[Xapian-tickets] [Xapian] #644: Wrong URLs in db and omega cgi

[Xapian]

#644: Wrong URLs in db and omega cgi
---------------------+---------------------------
 Reporter:  terencz  |             Owner:  olly
     Type:  defect   |            Status:  new
 Priority:  normal   |         Milestone:
Component:  Omega    |           Version:  1.2.12
 Severity:  normal   |        Resolution:
 Keywords:           |        Blocked By:
 Blocking:           |  Operating System:  Linux
---------------------+---------------------------
\
\
\
\
Changes (by olly):

 * component:  Other => Omega

\
\
\

Comment:

 Are you saying these URLs don't work, or just that they look ugly?

 If the former, please can you provide us with some example documents
 filenames which when indexed reproduce the problem.

 If the latter, I think what you're seeing is the result of fixing a bug in
 that older version - we weren't encoding characters in URLs which should
 be encoded according to the relevant RFCs, which was causing problems in
 some cases.

 There's now a $prettyurl omegascript command which undoes some of this
 encoding in cases where it doesn't actually seem to be required in
 practice with the commonly used webbrowsers - the aim is to produce a more
 human readable version of the URL which is still likely to work if cut and
 pasted (since some users will try that).  Unfortunately, top-bit-set
 characters are a bit problematic, as we don't know necessarily know what
 encoding filenames have on the system, and inside $prettyurl we don't know
 what character set the page we're generating has.  There's certainly scope
 for improvement here, and there's already ticket #550 open for this issue.
\
\
\

--
Ticket URL: <http://trac.xapian.org/ticket/644#comment:1>
Xapian <http://xapian.org/>
Xapian