Closed Bug 264406 Opened 20 years ago Closed 20 years ago

i18n custom keywords not correctly encoded

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

Product:
SeaMonkey
Component:
Bookmarks & History
Platform:
x86
Windows XP
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 258223

People

(Reporter: bugzilla, Assigned: p_ch)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; da-DK; rv:1.8a5) Gecko/20041014
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; da-DK; rv:1.8a5) Gecko/20041014

I made a bookmark: http://www.google.dk/search?q=%s and gave it the keyword ?,
as descriped on http://www.mozilla.org/docs/end-user/keywords.html

then. When i whant to search for e.g. "æblegrød" i type "? æblegrød" in the
location bar. Then the browser performs a google search for "?blegr?d", not the
word i typed.

this makes custom keyword unusable

Reproducible: Always
Steps to Reproduce:
1. Add the google search bookmark as described in
http://www.mozilla.org/docs/end-user/keywords.html
2. type e.g. "? øl" in the location bar (=beer)

Actual Results:  
the parameter was read as "?l"

Expected Results:  
the keyword should have been used as it was, maybe url-incoded

used a new just installed build and the 1.7.2 build for windows
Summary: in bookmarks, when using custom keywords some characters (maybe mon-american) are converted into questionmarks → in bookmarks, when using custom keywords some characters (maybe non-american) are converted into questionmarks
Some likely error in bugzilla (/UTF8).

Ill try to write it the HTML way: "? æblegrød"

or the url way: %3F%20%E6%62%6C%65%67%72%F8%64
When using the bookmark, url is correctly constructed and url-encoded, but in
ISO-8859-1 whereas Google expects than the url will be sent UTF-8 encoded.

When making a search by loading the google page, the page is displayed as UTF-8,
and after that in the search URL the parameters are encoded in UTF-8 as google
expects.

This is similar to bug 181243, but for Mozilla/Firefox.

I see one method to always get the charset right when constructing the request
URL would be to use the LAST_CHARSET info of the bookmark entry to select the
charset.

Currently the encoding used by mozilla is platform dependant (windows-1252 on
windows, UTF-8 on Mac OS X, probably the locale charset on *nix).

The fix for 123006 that was checked in firefox encodes i18n data as UTF-8, so it
wil probably solve the problem at least for Google when checked in Mozilla.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Depends on: 123006
Ever confirmed: true
Summary: in bookmarks, when using custom keywords some characters (maybe non-american) are converted into questionmarks → i18n custom keywords not correctly encoded
bug 258223 has a patch so that I'm marking this as dupe of that.


*** This bug has been marked as a duplicate of 258223 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.