Open
Bug 179878
Opened 22 years ago
Updated 2 years ago
Save JA mail with attachment as html - content looks garbled
Categories
(MailNews Core :: Internationalization, defect)
MailNews Core
Internationalization
Tracking
(Not tracked)
NEW
People
(Reporter: jeesun, Assigned: jshin1987)
Details
(Keywords: intl)
Attachments
(2 files)
Save JA mail with attachment as html - content looks garbled Build: 1112 branch Platform: MacOSX and Linux 7.3 Steps: 1. Send yourself a JA mail with JA html file attachment. In my case, I attached a JA html file encoded with EUC-JP 2. Receive the mail 3. Go to File|Save as File 4. Save it as a html file (with either JA name or EN name) 5. Open it in the browser and turn on auto detect in View|Character Coding 6. The content looks garbled and the window title looks weird too. Note: If saved as eml or txt file, it looks OK
Jeesun, what Autodetect is on: universal or japanese? If autodetect is off does it show correctly? I send myself a page from yahoo.jp (a euc-jp encoded page), got the mail and saved it as .html file twice : with english and japanese name. I opened the saved file in the browser and in both cases it looked correct. Turning autodetect on/off didn't change anything.
Keywords: intl
Reporter | ||
Comment 3•22 years ago
|
||
I just turn auto-detect on with Universal. I saw this on all platforms. When we save shift_jis or iso-2022-jp email with NO attachment, saved html file looks fine. If you turn on auto-detect, the browser will find the right encoding to display the mail body and header(subject, from, to etc.). In other words, body and the header were encoded using the same encoding. But when I attach euc-jp or shift_jis html file in the mail (or any other encoding I guess) and save the received mail as a html file, the display in the browser doesn't look right. You'll see different encoding in each area: For headers: You need to select UTF-8 encoding specifically to see the chars correctly For mail body: Need to select iso-2022-jp encoding For attachment: Need to select shift-jis or euc-jp depending on the encoding of attached file The bottom line is the entire content can not be displayed correctly in any case above.
Jeesun, just to be sure: you are saving the attachment from the envelope? and we are talking about the multi-part message with different encodings?
as i understand it the .eml files are saved as the original RFC 822 data and the html files are saved in system encoding. The autodetect usually check for UTF-8 sequences. What's your system encoding, Jeesun?
To clarify, the spec for Save as is as below . txt format -- saves in system encoding, stripping off unnecessary RFC822 lines. . HTML -- saves in HTML format using the original encoding. (e.g. ISO-2022-JP) . eml format -- saves as RC822 data, i.e. same data as off the wire. Please refer Kat's comments at http://bugzilla.mozilla.org/show_bug.cgi?id=33049#c17
I think, when saving the mail as html, we need to convert the attachment from the its original charset (either from charset label or the charset value sniffed by the auto detector) to the mail charset. With the current implementation, the charset conversion is missing for the attachment. Naoki, what do you think? I don't think the problem reported in this bug is related to auto detector since the html file already has charset meta tag.
Reporter | ||
Comment 9•22 years ago
|
||
>Jeesun, just to be sure: you are saving the attachment from the >envelope? and we are talking about the multi-part message with different >encodings? I'm not saving just the attachment. I'm saving the whole mail (a mail with attachment) by going to File|Save As and select File. >What's your system encoding, Jeesun? Shift_JIS
Reporter | ||
Comment 10•22 years ago
|
||
>I don't think the problem reported in this bug is related to auto detector since >the html file already has charset meta tag. I don't see the charset meta tag in the saved html file. Please see the attached html file. (This html file was created by: 1. I first sent a mail with euc-jp htm file attached. 2. When I received the mail, I saved it as a html file.)
Comment 11•22 years ago
|
||
I see the charset meta tag in the saved html file in my case. Jeesun, could you attach the testing mail to the report? Thanks.
Reporter | ||
Comment 12•22 years ago
|
||
I saved the mail in eml format and attached it here
Comment 13•22 years ago
|
||
I can reproduce the charset meta tag problem with Jeesun's testing mail. Jeesun, you may need to file a seperate bug for this.
Comment 15•22 years ago
|
||
This should be a problem in mail save as instead of charset handling. Let me assign to naoki and see what he thinks.
Assignee: shanjian → nhotta
Reporter | ||
Comment 16•22 years ago
|
||
I saw this on Mac OSX too. nominate this bug. Without fixing the problem, when mail gets saved, attachments with JA encoding can't be seen properly.
Keywords: nsbeta1
Reporter | ||
Comment 17•22 years ago
|
||
>I can reproduce the charset meta tag problem with Jeesun's testing mail. Jeesun, >you may need to file a seperate bug for this. For meta tag missing problem see the bug 180032
Updated•20 years ago
|
Product: MailNews → Core
Comment 20•20 years ago
|
||
both naoki and I are off mozilla for about 20 monthes. If these bugs are still here, the real status is 'wont fix'. If you want to reopen it, please find a better owner who really looking at the bug database now.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Comment 22•20 years ago
|
||
Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all the spam is his fault feel free to tar and feather him
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 23•20 years ago
|
||
Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam
Assignee: nobody → jshin1987
Status: REOPENED → NEW
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: marina → i18n
Comment 24•7 years ago
|
||
Still repro with example file. Thunderbird 52.1.1 (32-bit) Windows 7 64-bit
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•