123612 - Mail compose window: need charset check when selecting File | Save as | File

Status: NEW

(MailNews Core :: Internationalization, defect)

Description

[ji]

With the current build, on mail compose window, we do charset check when sending
out messages or saving messages as draft or template. We also need this check
for saving as file, otherwise the composing message can't be saved correctly.
And we need this for both HTML and plain text mail.

Comment 1

[ji]

Steps to reproduce:
1. Open a mail compose window, make sure the charset is pointing to iso-8859-1.
2. Enter some chars not in ISO-8859-1, like Japanese, in mail body. (Save as
file only saves mail body for now)
3. Select File | Save as | File, no charset warning dialog comes up. 

Comment 2

[nhottanscp]

For HTML, it can be saved as NCR, so no alert is necessary.

Comment 3

[ji]

But can users read it if it is saved in NCR?

Comment 4

[nhottanscp]

That's for HTML only. I think it's better to save as NCR instead of a question mark.

Comment 5

[ji]

Can we convert it to plain text before saving it to file? Not like save as
draft/template, this function is going to save the mail body into a text file.
If we save it in NCR, the user won't be able to read it from a  text editor.

Comment 6

[nhottanscp]

I misunderstood the feature, if the only option is text/plain then we should not
save as NCR.

Comment 7

[marina]

why are we talking only about one option : saving as text file ( this is the
first choice, but then there are all formats)..?

Comment 8

[ji]

If I select All Files and give the extension as .html, it still saves as text.
It seems the current implementation only supports save as text.

Comment 9

[Makoto Kato [:m_kato]]

When I write JPN body with ISO-8859-1 charset (Options - Character Encoding), I save text file by File - Save As - File.  Then, text file is corrupt (it becomes '?').

This is still repro on 3.1