Closed
Bug 23268
Opened 26 years ago
Closed 26 years ago
int. chars in fx. "Your name" get written funny
Categories
(SeaMonkey :: MailNews: Account Configuration, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: bugzilla, Assigned: alecf)
Details
If I enter "Hænrik Gømal" in "Your Name" in the account setting dialog the data
that actually gets written to the prefs.js file is different. My data in the
pref becomes:
user_pref("mail.identity.id2.fullName", "Hænrik Gømal");
The data you enter should also be the data in the prefs!
Build 20000105
Comment 1•26 years ago
|
||
This is as it should be. All non-ASCII data in prefs.js msut be
stored in UTF-8. What you are seeing is the UTF-8 encoding of
the name you put in.
We need to provide a handy UTF-8 editor to use for prefs.js -- hopefully
we can come up with one soon.
This bug should be resolved as Worksforme or Invalid.
| Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 2•26 years ago
|
||
yes, I was going to write the same thing but momoi beat me to it.
beppe or buster,
Eons ago, we had discused that composer would be able to open *.js files
and treat them like *.txt files? I haven't tried this recently. Is this
in the plans? Because composer should be able to handle UTF-8 text files.
Comment 5•26 years ago
|
||
I don't know what code handles figuring out which type of editor to use
depending on the file suffix. Simon might know more -- cc'ing. It certainly
sounds very reasonable that we should treat .js files as plain text, and if
we're not doing that already, I'd encourage filing a new bug on that issue (I
would assume that the fix for that would be straightforward for anyone on the
editor team).
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•26 years ago
|
||
** Checked with 1/13/00 Win32 build **
Verified as invalid.
A request to treat .js extension has been filed as a new Bug 23943.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•