Closed Bug 299000 Opened 19 years ago Closed 19 years ago

Support escaping for UTF-8 for all strings in prefs.js

Categories

(Core :: Preferences: Backend, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 307438

People

(Reporter: daniel.brucker, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Win98; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

(English follows)
 
Impossible d'afficher les caractères accentués dans les en-têtes de réponse. La
formule \x(nnn) dans "user.js" ne fonctionne pas.

Unable to display accentuated characters in reply headers. Using \x(nnn) formula
in "user.js" doesn't work. 

Reproducible: Always

Actual Results:  
(English follows)
toute la phrase est perdue

all the sentence is lost

Expected Results:  
a good job !
You mean when reading a mail? I don't see what this bug has to do with the
preferences (window)?
(In reply to comment #1)
> You mean when reading a mail? I don't see what this bug has to do with the
> preferences (window)?

I mean this header shoud be writen as 
"le 28/06/05 14:17 bugzilla-daemon@mozilla.org a _écrit_ ceci:"
instead of
"le 28/06/05 14:17 bugzilla-daemon@mozilla.org a ecrit ceci:"
See bug 297572 -- prefs.js is assumed to be encoded in UTF-8.

However, it's true that there is no way to "escape" the strings -- é could be 
entered in the file as %C3%A9 or \xC3\xA9.  (URL strings can be entered in 
prefs.js using %xx escaping, only because the URL parser unescapes.)

The workaround is to edit the preferences using about:config (or a UTF-8-
compatible editor).  In Thunderbird, pre-1.1 builds have an "about:config" page, 
at:  Tools | Options | Advanced | General:  "Config Editor"
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: Preferences → Preferences: Backend
Ever confirmed: true
OS: Windows 98 → All
Product: Thunderbird → Core
Hardware: PC → All
Summary: Unable to display accentuated characters in reply headers → Support escaping for UTF-8 for all strings in prefs.js
Version: unspecified → Trunk
Er... Did this break when we stopped using JS for the prefs parsing?
I believe it is a regression from that particular change, yes.
fixed in bug 307438...

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