Open
Bug 123608
Opened 23 years ago
Updated 2 years ago
Save as | File on mail compose window is not working properly when charset is not consistent with system charset.
Categories
(MailNews Core :: Internationalization, defect)
MailNews Core
Internationalization
Tracking
(Not tracked)
NEW
People
(Reporter: ji, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intl)
On Mail compose window, menu File | Save as | File is not working properly for non-ASCII mails. Steps to reproduce: 1. Open a mail compose window. 2. Enter some non-ASCII chars, like Japanese, in subject and mail body. With current implementation, it only saves mail body part in text format, and if mail body is empty, it generates a empty text file. 3. Select File | Save as | File, a file dialog window comes up. (I think here we need some charset check for mail body. And we need this check for both HTML and plain text mails for this function, I'll file a seperate bug later) 4. On file dialog window, enter a filename and click on Save. 5. Open the text file that is generated, the Ja chars are displayed in question marks. It should be saved in system charset.
Please note that at step 3, I select iso-2022-jp charset before saving the compose message, and I got incorrect result. If I select Japanese Shift-JIS before saving, I got a file saved in SJIS. It seems a conversion is missing here.
Keywords: intl
It only works when the charset of the mail compose window is consistent with system charset.
Summary: Save as | File on mail compose window is not working properly for non-ASCII mails → Save as | File on mail compose window is not working properly when charset is not consistent with system charset.
Comment 3•23 years ago
|
||
What is the desirable behavior? Always save as the mail charset?
Status: NEW → ASSIGNED
I think the purpose of the function is to allow users to save the message into a text file which is readable and can be copy/pasted to compose window later. So it should be saved in system charset so users can read it with a text edit application, like notepad. When the mail compose charset is not the same as system charset, it should do the conversion.
Nominating for nsbeta1 since Japanese users usually compose mails with charset set to ISO-2022-JP, which is not same as system charset.
Keywords: nsbeta1
Updated•23 years ago
|
Target Milestone: --- → mozilla1.2
Updated•22 years ago
|
Target Milestone: mozilla1.2alpha → ---
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: ji → i18n
Comment 7•15 years ago
|
||
similar to bug 123612.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•