Closed Bug 89043 Opened 24 years ago Closed 24 years ago

ISO-2022-JP encoded messages are incorrectly converted to ISO-8859-1 on reply

Categories

(MailNews Core :: Composition, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: blizzard, Assigned: bugzilla)

Details

(Keywords: intl, regression)

This is from Adrian. It's present in the Moz 0.9.2 release and I would assume that it's in the tip and the current branch builds as well. If you reply to a message that is sent with ISO-2022-JP encoding and you reply it is assumed to be Western ISO-8859-1 and the quoted Japanese message is turned into ASCII jibberish. This worked in 0.9.1.
This is a pretty serious regression. You guys probably want to fix this for RTM if you want your JP users to be able to use email.
Keywords: regression
add nhotta to the cc
cc to iqamail
Keywords: intl
Adrian, i am using the 07-03-03 branch ( 0.9.2) build and i can not reproduce your problem. Question: are you using branch or trunk build? Can you clarify what you mean when you say <"you reply it is assumed to be Western ISO-8859-1"< ? Thanks.
( I suspect that adrian is using the mozilla 0.9.2 release build. ) More notes from Adrian in private email: "It *IS* apparently possible to get the reply to ISO-2022-JP, but it looks like you must first compose a new message, setting the encoding to ISO-2022-JP, AND successfully send before the initial encoding "sticks". When the fonts were messed with for 0.9.2 it looks like it through my initial encoding back to ISO-8859-1 when upgrading from 0.9.1."
i noticed that the platform is Linux , i actually tried Windows, Adrian is that Linux specific? I'll try Linux now and report here..
I'm using Linux... haven't tried Windows.
I am embarrassed to admit that I'm probably going to have to close this bug-- I myself can no longer reproduce it for one reason or another.
i tried yesterday's 07-02-03- Linux build ( on Linux redhat 7.0 JA) and i can not reproduce it. Adrian, would you help us to reproduce it in house? We need to know what build you are using ( branch/trunk)? Thanks.
based on Adrian comments and on our inability to reproduce it i am marking it as wfm. Adrian , in case you'll see it again,please reopen.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
QA Contact: sheelar → marina
verifying as such
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.