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)
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
Comment 1•25 years ago
|
||
Are headers correctly saved? Marina, please attach the .eml file used for the
test.
Comment 2•25 years ago
|
||
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
*** Bug 39352 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17 → M18
Need retest on fwding and let us know if still occurs.
Whiteboard: [NEED INFO]
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.
Comment 9•25 years ago
|
||
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.
Reporter | ||
Comment 11•25 years ago
|
||
still reproducable with 2000-07-07 M17 build
Updated•25 years ago
|
Whiteboard: [nsbeta2-]
Comment 12•24 years ago
|
||
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
Reporter | ||
Comment 13•24 years ago
|
||
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 → ---
Reporter | ||
Comment 14•24 years ago
|
||
Comment 15•24 years ago
|
||
Well, this is gonna have to wait for 6.1
Status: REOPENED → ASSIGNED
Target Milestone: M18 → Future
Comment 16•24 years ago
|
||
What argument would support a P1 or P2 for this?
Whiteboard: [b3 need info]
Comment 17•24 years ago
|
||
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
Reporter | ||
Comment 19•24 years ago
|
||
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.
Assignee | ||
Updated•23 years ago
|
Target Milestone: Future → mozilla0.9.7
Updated•23 years ago
|
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 21•23 years ago
|
||
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
Reporter | ||
Comment 22•22 years ago
|
||
*** Bug 206898 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 23•22 years ago
|
||
Ray and Ying, please see comments in 206898 concerning l10n
Updated•20 years ago
|
Attachment #8299 -
Attachment mime type: text/plain → message/rfc822
Updated•20 years ago
|
Attachment #8299 -
Attachment filename: Inbox.txt → 38109.eml
Comment 24•20 years ago
|
||
*** This bug has been marked as a duplicate of 129443 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•