Closed
Bug 60496
Opened 25 years ago
Closed 25 years ago
Add HTTP header Accept-Charset like Nav 4, and reflect charset pref setting
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
People
(Reporter: havill, Assigned: gagan)
Details
Attachments
(1 file)
Navigator 4 adds a static Accept-Charset to HTTP request headers. Add this
header to Mozilla as well, and also reflect the user's desired character
set/encoding set via Edit... Preferences... Languages which is saved in the
intl.charset.default preferences... giving end users a way to hint to the server
what charset they'd prefer to receive documents in (to aid in receiving a
document that is displayable immediately on their host system). For example,
Windows and Macintosh Japanese users would want Japanese documents in Shift_JIS,
but Unix users may want euc-jp. You can always post-convert, and Mozilla can
handle any charset, but when saving the HTML to the client system, it makes it
easier for newbies doing HTML editing to edit the document immediately with
standard editors, without needing conversion.
| Reporter | ||
Comment 1•25 years ago
|
||
Comment 2•25 years ago
|
||
This is a duplicate. You probably want to attach the patch to the original bug...
*** This bug has been marked as a duplicate of 13393 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•