Open
Bug 82016
Opened 24 years ago
Updated 2 years ago
Non-ascii file name and Subject in the body of NoMime messages are not displaying correctly when Forward as attachment
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
NEW
Future
People
(Reporter: marina, Unassigned)
References
Details
(Keywords: intl, Whiteboard: intl)
Attachments
(2 files)
*** observed with 2001-05-21 build *** -Forward a message in KOI8-R as an attchment; -get the message; - select KOI8-R encoding; //note: file name and subject in the body look like garbage; now: reload the message and you'll see the file name displayed correctly but the Subject in the body is still garbled, to correct the display you have to scroll
Summary: Non-ascii file name and Subject in the body need to be reloaded to see the proper encoding → Non-ascii file name and Subject in the body of NoMime messages are not displaying correctly when Forward as attachment
Comment 3•24 years ago
|
||
>//note: file name and subject in the body look like garbage;
What does that mean? Could you attach a screen shot?
Updated•24 years ago
|
in today's build scrolling doesn't help, you have to reload the message
Updated•24 years ago
|
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Comment 7•24 years ago
|
||
Non-ASCII does not display correctly in Message pan. It display correctly in email list (upper part)
Comment 9•23 years ago
|
||
WORKSFORME on today's build (with fix for bug 91899) : I took koi8 message from testcase, forwarded it as attachment (set charset to koi8-r). Subject of message and attachment name are displayed correctly (they were encoded in koi8-r while forwarding message) After setting view charset to koi8-r original message body and subject are displayed correctly as well.
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: marina → i18n
Updated•12 years ago
|
Assignee: nhottanscp → nobody
Status: ASSIGNED → NEW
Whiteboard: intl
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•