Closed Bug 370894 Opened 18 years ago Closed 16 years ago

bad encoding of hebrew (non latin?) substitute for custom keywords

Categories

(SeaMonkey :: Bookmarks & History, defect)

SeaMonkey 1.1 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: tsahi_75, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 i have this custom keyword bookmark for the hebrew wikipedia: http://he.wikipedia.org/wiki/%s with the keyword "wp". on mozilla 1.7.13 this worked fine, and it works in firefox, but since seamonkey 1.0 it doesn't. the word גז is encoded %3F%3F%3F instead of %D7%92%D7%90%D7%96 (as it is in firefox). in fact, all hebrew strings are encoded as sequences of %3F's. Reproducible: Always Steps to Reproduce: 1. create a custom keyword bookmark 2. call this keyword with a hebrew word (may be true for other non-latin, i didn't check) 3. Actual Results: the %s in the url is replaced with a sequence of %3F's Expected Results: the %s should be replaced with properly encoded string
Flags: blocking-seamonkey1.5a?
I seem to get %D7%92%D7%96 when I paste גז into the URL bar... is this still a problem? Or is there something I'm missing?
(In reply to comment #1) > I seem to get %D7%92%D7%96 when I paste גז into the URL bar... is this still > a problem? Or is there something I'm missing? > Tsahi have noted that "%D7%92%D7%90%D7%96" should decode to "גז" rather than "גאז" as it should. So you get the expected result for "גז".
this seems to be some kind of profile corruption, because on a new profile it doesn't happen. and i also started to get this in a firefox installation i have on a different computer (at work). i'll have to verify the firefox case when i get to work tomorrow. (In reply to comment #2) > (In reply to comment #1) > > I seem to get %D7%92%D7%96 when I paste גז into the URL bar... is this still > > a problem? Or is there something I'm missing? > > Tsahi have noted that "%D7%92%D7%90%D7%96" should decode to "גז" rather than > "גאז" as it should. So you get the expected result for "גז". > i think Andrew is getting the correct encoding here. on my machine and profile, i would get a sequence of %3F's, as i wrote.
This is probably connected to the prefs network.standard-url.encode-utf8 and/or network.standard-url.escape-utf8.
(In reply to comment #4) > This is probably connected to the prefs network.standard-url.encode-utf8 and/or > network.standard-url.escape-utf8. > both of these prefs are at their default values in the SeaMonkey installation - false and true respectively.
The default of network.standard-url.encode-utf8 has gone to and fro: it was changed to true in bug 261929 at 2005-01-12, reverted to false in bug 284474 at 2005-10-10, and rereverted to true in bug 261929 at 2006-04-13. FWIW, I can't reproduce the bug with either pref setting in trunk builds of either firefox or seamonkey.
re. comment 3, i also get this on a firefox 2.0 installation have.
Version: unspecified → SeaMonkey 1.1 Branch
Does this happen on SM trunk nightlies?
Denying SM2.0a1 as no response. You can nominate for 2.0 if there is more information posted.
Flags: blocking-seamonkey2.0a1? → blocking-seamonkey2.0a1-
(1+ year later) No reply from reporter R.Incomplete Reopen if you can reproduce with using an recent Build, and submit actual information.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.