Open
Bug 92183
Opened 23 years ago
Updated 2 years ago
Save as File is not working properly for the message headers with wrong or no MIME charset
Categories
(MailNews Core :: Internationalization, defect, P4)
Tracking
(Not tracked)
NEW
Future
People
(Reporter: ji, Unassigned)
Details
(Keywords: intl, Whiteboard: intl)
Build: 07/24 branch build Save as File is working properly for the mail body of the messages which have wrong or no MIME charset info, but not for the header. When saved as .txt file, the header is not saved in system encoding. When saved as .eml file, it seems that the header is saved in RFC 822 style data, but when I open this .eml file in browser window, it's not displayed correctly in uTF-8 charset menu selection. Our discussion about save as file spec for i18n is described in bug 33049.
Updated•23 years ago
|
Status: NEW → ASSIGNED
dup of bug# 88121?
Updated•23 years ago
|
Priority: -- → P4
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•15 years ago
|
QA Contact: ji → i18n
Updated•11 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
•