Closed
Bug 231524
Opened 21 years ago
Closed 21 years ago
8-bit (8859-1) source for RFC822 body converted to UTF-8, then rendered as 8-bit
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 129443
People
(Reporter: mcow, Assigned: smontagu)
Details
I first noticed this back in June, testing bug 144793. Reporter included source
for an email which had ISO-8859-1 characters (Spanish diacriticals) in the
subject and in the body. His problem seems to have been fixed within the mail
program.
However, I noticed that downloading his attachment 83738 [details] into the browser
rendered somewhat peculiarly -- when the message is displayed per the browser's
'mail message' styling, with ISO-8859-1 encoding, the characters in the body
appear to have been converted from 8859 to Unicode, then are being displayed as
the 8-bit bytes of the UTF-8 representation. The subject displays correctly.
Changing the browser's encoding setting to UTF-8 renders the body correctly but
now the subject is misrendered, as you would expect.
If this attachment -- which has a type of text/plain -- is reloaded, it loses
its 'message' styling, displays just as a string of characters, and all are
rendered correctly (with 8859-1 encoding).
The source of this file is definitely 8-bit/8859, in its entirety -- I've
checked it with a hex editor.
See also attachment 139450 [details], which is the same source file but with a MIME type
of message/rfc822 -- this one will continue to have the 'message' styling on
reload.
Assignee | ||
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 129443 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•