Closed
Bug 182976
Opened 22 years ago
Closed 20 years ago
bad character set detection for '<emdash>t' (Windows 1252)
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 168526
People
(Reporter: timeless, Assigned: smontagu)
References
Details
Attachments
(1 file)
1.84 KB,
text/plain
|
Details |
I got bugmail for bug 181711 comment 3, mozmail (imap connection) - cvs build from about two weeks ago rendered "output葉hat", displaying the source/message as Western (ISO-8859-1) triggers results in "output—that". Oddly the character coding is listed as Western (ISO-8859-1) even while universal autodetect is triggering 葉.
When loaded from a file in navigator, i get Western (Windows-1252): output葉hat
Assignee | ||
Comment 2•22 years ago
|
||
Can anyone reproduce this in an up-to-date build? It might be a similar issue to bug 180988
Assignee | ||
Comment 3•21 years ago
|
||
In fact it's much more similar to bug 168526
Comment 4•20 years ago
|
||
Duping to the browser autodetect bug. Bug 253849 opened for the failure of the Mail/News View|Encoding menu to update, which is a common symptom to some otherwise distinct Mail/News charset bugs. *** This bug has been marked as a duplicate of 168526 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Summary: bad character set detection for '—t' → bad character set detection for '<emdash>t' (Windows 1252)
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•