Closed Bug 197728 Opened 21 years ago Closed 21 years ago

Incorrect translation of special characters when using Internet Keywords

Categories

(SeaMonkey :: Location Bar, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mozilla.org, Assigned: hewitt)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312

When using Internet Keywords, search terms that contain special characters are
not translated correctly.

Reproducible: Always

Steps to Reproduce:
1. Enable Internet Keywords in Preferences -> Navigator -> Smart Browsing
2. Enter a word containing special characters in the URL bar and hit return

Actual Results:  
entering 'würstchen' (german u umlaut) returns
http://www.google.com/search?q=w%C3%BCrstchen

Expected Results:  
entering 'würstchen' should instead return
http://www.google.com/search?q=w%FCrstchen
Eh?  The former is a correct encoding of the UTF8 version of that character... I
assume the latter is an encoding in some ISO-8859-* charset?
I ~think~ so. My point is: The former encoding will be translated to 'würstchen'
(this is w--capital A with tilde--1/4--rstchen) by google (as well as by other
search engines, by any php-script you pass it to, etc), while only the latter
correctly returns 'würstchen'. Bottom line: UTF8 encoding is inappropriate for
Internet Keywords.
Google does handle UTF8 encoding, but only if told to:

http://www.google.com/search?q=w%C3%BCrstchen&ie=UTF-8

I'm not sure about the other search engines listed in
Preferences -> Navigator -> Internet Search though...
Reporter: Is this still a bug? Internet Keywords send UTF-8 encoding here,
entering something and clicking on "Search Google for "würstel"" also works
(sends the URL
http://www.google.com/search?q=w%C3%BCrstel&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8).
Everything on win2k with a cvs trunk build.
no response-->resolving worksforme
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.