Closed
Bug 138293
Opened 23 years ago
Closed 23 years ago
Forward: non-ascii header in the message is displayed as single byte chars
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 110729
People
(Reporter: marina, Assigned: nhottanscp)
Details
(Keywords: intl, regression)
Attachments
(1 file)
(deleted),
image/jpeg
|
Details |
*** observed with 2002-04-18-03 trunk build ***
Steps to reproduce:
- compose a message with non-ascii chars ( i used Latin-1) in the Subject header;
- forward message as an attachment;
- get message and note that the display of the non-ascii header in the message
body is incorrect. Source of the message points to 1252 encoding instead of
8859-1. At the same time if you forward inline you get a warning for the charset
mismatch, sending as is( without manually setting to Latin-1)is not reflected on
the header display. The display is still fine in the message body. Regression.
Keywords: intl,
regression
Assignee | ||
Comment 4•23 years ago
|
||
cc to putterman, ducarroz, do you know trunk only fix which might cause this?
We need to make sure the problem does not copied to the branch.
Assignee | ||
Comment 5•23 years ago
|
||
I looked at check in to libmime within one week.
There was check in for bug 30888 on 3/16 affected many files.
Marina, could you test 3/16 morning trunk and 3/17 trunk to see if the problem
exist in those builds?
Naoki, i re-installed the build and i don't see the problem now, neither do i
see it in 4/16 and 4/17 builds. However there might be some conditions that were
present yesterday and triggered the problem ( i was testing plaintext
conversion). Let me do some more testing before we solve this as invalid.
I know now what happened: prior to viewing this message i opened a .pdf file(
btw: this pdf attachment didn't get open in Acrobat application but got
displayed inside the message). The problem with non-ascii chars and viewing pdf
file is an old one but i thought it was fixed already, let me find the bug
number. In any event only forward as attachment gets effected.
*** This bug has been marked as a duplicate of 110729 ***
Status: ASSIGNED → RESOLVED
Closed: 23 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
•