Closed Bug 38109 Opened 25 years ago Closed 20 years ago

Eml attachment with non-ascii in the header shows them as garbage in the browser

Categories

(MailNews Core :: Internationalization, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 129443
mozilla1.0.1

People

(Reporter: marina, Assigned: bugzilla)

References

Details

(Keywords: intl)

Attachments

(2 files)

***** observed with 2000-05-03 build ***** Steps to reproduce: -select a message with non-ascii in the Subject field(or having a recipient name with non-ascii chars); -save this message in .eml format; -invoke a new composition window; -attach the .eml file, send and get it; //note: all non-ascii in the attachment in header look like garbage
Are headers correctly saved? Marina, please attach the .eml file used for the test.
Reassing to rhp. A problem in save as .eml or attachment send. Marina, please attach the .eml file used for the test.
Assignee: nhotta → rhp
Target M17.
Target Milestone: --- → M17
*** Bug 39352 has been marked as a duplicate of this bug. ***
Keywords: nsbeta2
Status: NEW → ASSIGNED
Target Milestone: M17 → M18
Need retest on fwding and let us know if still occurs.
Whiteboard: [NEED INFO]
marina, please check this.
QA Contact: momoi → marina
Tested with 2000-05-25-08 build : the scenario described in the bug report (message with non-ascii in the Subject saved as .eml file displays 8-bit chars as two single-byte chars if attached to the mail body) is not happening anymore. When you attach an eml file non-ascii in the attachment are showing up correctly but if you just view the saved file through the Browser (File|Open page...) it is showing 8bit chars as two single-byte, please advise.
If .eml file is supposed to be the same as the original message data, then this result is wrong. It is message body is saved as UTF-8 right now. I think this is a bug.
Putting on nsbeta2- radar.
Whiteboard: [NEED INFO] → [nsbeta2-]
still reproducable with 2000-07-07 M17 build
Keywords: nsbeta2correctness, nsbeta3
Whiteboard: [nsbeta2-]
Ok, I've retested this and like the other .EML message, this is displaying correctly when displayed inline. - rhp
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
the second scenario: view eml file with non-ascii in the Subject header from Browser shows single byte as two-bytes is still happening in 2000-09-19 build, reopening and attaching screen shot
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Well, this is gonna have to wait for 6.1
Status: REOPENED → ASSIGNED
Target Milestone: M18 → Future
What argument would support a P1 or P2 for this?
Whiteboard: [b3 need info]
Seeing the type of stuff we are "Future-ing" at this point, there's no way this would come close to being criticial enough to fix. - rhp
nsbeta3-
Whiteboard: [b3 need info] → [nsbeta3-]
Keywords: intl
just want to add some comments: JA chars in this case ( mail saved as eml file) are displaying in the message header and body as question marks (???) and i am not able to view them in 4.72 at all.
reassigning to ducarroz
Assignee: rhp → ducarroz
Status: ASSIGNED → NEW
Target Milestone: Future → mozilla0.9.7
Keywords: nsbeta3
Whiteboard: [nsbeta3-]
Target Milestone: mozilla0.9.7 → mozilla1.0.1
Status: NEW → ASSIGNED
Note, that non-ascii headers in .eml file are correctly encoded (QP for message headers and B64 for attachment headers), so maybe this is browser problem?
Summary: Eml attachment with non-ascii in the header shows them as garbage → Eml attachment with non-ascii in the header shows them as garbage in the browser
*** Bug 206898 has been marked as a duplicate of this bug. ***
Ray and Ying, please see comments in 206898 concerning l10n
Attachment #8299 - Attachment mime type: text/plain → message/rfc822
Attachment #8299 - Attachment filename: Inbox.txt → 38109.eml
*** This bug has been marked as a duplicate of 129443 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago20 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: