122569 - Saving as draft with едц in subject changes to diamond characters

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[magnus.malmsten]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+)
Gecko/20020120
BuildID:    20020120

Saving as draft with scandinavian characters åäöÅÄÖ gives user a warning about
changing message character coding. When saving anyway scandinavian characters
converts to different diamond characters in subject.

Reproducible: Didn't try
Steps to Reproduce:
1. Create a new mail with scandinavian characters in subject
2. save as draft
3.

Actual Results:  subject with scandinavian characters converts to different
diamond instead of scandinavian characters.


Expected Results:  save subject with scandinavian characters without warning to user

Comment 1

[Karl Johan Kleist]

Reporter: Maybe a summary in English would be better?

Comment 2

[R.K.Aa.]

On linux, I have checked the pref / mail & newsgroups / Message Composition 
to use "For messages that contain 8-bit characters, user "quoted printable" MIME
encoding...."

Drafts here save with correct characters (using norwegian characters as well as
those pasted from this bug). No alert appeared.

Comment 3

[magnus.malmsten]

Enabling the setting for "For messages that contain 8-bit characters, user
"quoted printable" MIME encoding...." had no effect on this one.
The mail draft saving works perfectly with Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:0.9.4) Gecko/20010914 but not with this build. Preferences could be
different.

Comment 4

[nhottanscp]

Reassign to nhotta.
I copy/paste 'едц' to the subject field but did not see the warning, I used my
debug build updated this morning, the charset of the message was ISO-8859-1 (set
in the "Message Compose" preference).
Cc to IQA.

Comment 5

[marina]

i am mot able to reproduce it on my Win2K machine. Those chars are displaying
correctly in Drafts and i don't get any warning while saving. Magnus, what's
your system charset?

Comment 6

[magnus.malmsten]

System Charset is ISO-8859-1 on display and compose

Comment 7

[marina]

magnus, would you please attach the saved mail since we are not able to
reproduce it in house. Thanks.

Comment 8

[magnus.malmsten]

Attachment: Draft message attached

Sending the mail converted the å characters to a* ä chars to a¨ 
Had to correct them manually to get it right.

Comment 9

[nhottanscp]

Subject: Linux =?us-ascii?Q?ty=F6ryhm=E4n?= kokous

It should be "ISO-8859-1" instead of "us-ascii". That might be something to do
with the problem.

Comment 10

[marina]

yes, i wanted to ask you the same question as Naoki did:
the header in the source is not correct, looking at your environement  sv,en-en
the header should say Western 8859-1 and you can not get any warning of the
mismatch charset in that case. In your case you get us-ascii in header and that
would explain the poping -up alert. Magnus, could you please try to compose a
new message with the latest build and attach it ( without altering chars) so
that we could be able to see why you're getting a wrong header. Then you're
saving to Draft, are you Editing Drafts?? 

Comment 11

[ji]

I checked linux 0.9.7 build (and also the latest build), with the same subject
copied over from the attached mail, I got the right MIME header specifying the
charset as ISO-8859-1, not us-ascii. And I have the same preferences: with
quoted printable enabled, composition and display charset set to iso-8859-1. And
I started the browser in sv locale. 

Comment 12

[magnus.malmsten]

Attachment: mail composed with new build

Installed Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8+)
Gecko/20020131 and composed a new mail, saved as draft and saved on local drive
and attached the file. Looks like the header is still us-ascii

Comment 13

[marina]

Attachment: Magnus, here is a screen shot of the display of the message you attached, it looks correct

Comment 14

[magnus.malmsten]

I wonder how the previous message did get the us-ascii in the subject line.
Could a previous version or another mail program change it when it was edited in
draft?

Comment 15

[magnus.malmsten]

Sorry to say that i got this bug again today. With User-Agent: Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:0.9.8+) Gecko/20020204
in
Subject: =?us-ascii?Q?Offertbeg=E4ran?=

Comment 16

[marina]

Magnus, thanks for keeping eye on this bug. Now i am wondering whether it is the
same problem that was reported in bug #57731.Looking as the source of the header
that Bob Jung provided the charset was treated as us-ascii in his case as
well.The display at that time of the едц was a square and not diamond chars, it
wasn't a saving problem either. Though it does look like there are similarities
in those two cases ( besides those that we were not able to reproduce it either :-) 
Naoki, could you take a look at this problem?

Comment 17

[magnus.malmsten]

Attachment: Saving a edited draft with едц picture

Have been able to reproduce bug with Mozilla/5.0 (Windows; U; Windows NT 5.0;
en-US; rv:0.9.8+) Gecko/20020218
1. Compose a mail with едц in subject and едц in contents
2. save as draft
3. open draft and edit text
4. save draft
result saving_edited_draft.gif
when saved (ok clicked) savedasdraft.gif

Comment 18

[magnus.malmsten]

Attachment: Edited draft is saved

Comment 19

[magnus.malmsten]

Attachment: Subject line in draft does not show totally

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914
shows right of едц in subject line in draft folder empty

Comment 20

[marina]

magnus, thank you for detailed steps , the key to reproduce your problem was
saving to Drafts TWICE. When you do so you do get a charset warning and if you
save it anyway then you have (i've got) ????? . I can confirm this bug.

Comment 21

[nhottanscp]

I check in some changes for forward inline and draft recently. 
Does this still happen?

Comment 22

[magnus.malmsten]

Yes now it works for me. the second time you save to draft it gives a charset
warning but it does not mess up scandinavian characters now. Nice work, thank you !!

Comment 23

[marina]

verifying