Bug #2067

character translation in search

Added by Bob Gobeille 12 months ago. Updated 9 months ago.

Status:Closed Start date:05/30/2012
Priority:High Due date:
Assignee:Dong Ma % Done:

0%
Category:UI
Target version:2.1.0 Estimated time:16.00 hours
Rank: Tester:

Description

Entering some search filenames requires you to enter character sequences that are translated. For example, search for the file name daemon and the leading %da will get translated to:

<INPUT type='text' name='filename' size='40' value='&Uacute;emon%'>

(see attached file).

The webpage charset is UTF-8, changing it to us-ascii would not be desirable nor did it fix the problem. If we can't come up with an elegant solution, I recommend changing the wildcard from % to *. The code would have to do the reverse when generating the sql since postgres expects %.

charset.gif (37.3 kB) Bob Gobeille, 05/30/2012 07:50 pm

History

#1
Updated by Paul Holland 12 months ago

  • Assignee set to Dong Ma
  • IterNum set to 2

#2
Updated by Dong Ma 12 months ago

  • Estimated time set to 16.00

#3
Updated by Dong Ma 12 months ago

  • Status changed from New to Resolved

Fixed in revision5930.

Caused by $Filename = GetParm("filename",PARM_STRING); PARM_STRING use urldecode() function to decode any %## encoding in the given string.

#4
Updated by Bob Gobeille 11 months ago

  • Status changed from Resolved to Closed

verified on svn 5931

#5
Updated by Mary Laser 9 months ago

  • Target version changed from 2.0.1 to 2.1.0

Also available in: Atom PDF