507875 - When forwarding Hebrew text is corrupted, when replying text is OK

Status: NEW

(Thunderbird :: Message Compose Window, defect)

Description

[Eran Gal]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.37 Safari/530.5
Build Identifier: 5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3

When I receive an email with Hebrew text, I am able to reply to it and have the text copy fine to the new email, however, when I forward emails, the text becomes corrupted.  For example, when I forward:
"איל שלום,"
I get:
"àéì ùìåí,"





Reproducible: Always

Steps to Reproduce:
1. Get an email with Hebrew body text
2. Forward it (no need to send, you will see the issue right away)

Comment 1

[Simon Montagu :smontagu]

Dupe of bug 287675?

Comment 2

[[:Aureliano Buendía]]

If I understand your issue is WFM here on

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3pre) Gecko/20090815 Lightning/1.0pre Shredder/3.0b4pre ID:20090815035456

Have you enabled charset auto-detection on your folder?

Comment 3

[Eran Gal]

No.  How do you do that?

Comment 4

[Eran Gal]

(In reply to comment #2)
> If I understand your issue is WFM here on
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3pre) Gecko/20090815
> Lightning/1.0pre Shredder/3.0b4pre ID:20090815035456
> 
> Have you enabled charset auto-detection on your folder?

No. How do you do that?

Comment 5

[[:Aureliano Buendía]]

Go to folder that contains the message that you should "forward".

Click on it with mouse rx and select on context menu item "properties...": this
open a window: flag OFF the property "Apply default to all messages in the
folder (individual message character encoding settings and auto-detection will
be ignored)".

This resolve your issue?

Comment 7

[[:Aureliano Buendía]]

Gérard Vahée can attach here your email that show the issue (not *.pdf but *.eml)

Can also try with workaround in comment #5?

Comment 8

[Gérard Vahée]

(In reply to comment #7)
> Gérard Vahée can attach here your email that show the issue (not *.pdf but
> *.eml)
> Can also try with workaround in comment #5?

1- I do not know how to edit a mail that I have received into an .eml format. Can you tell me ?

2-The workaround in #5 is not appropiate : I had read this 507875 before sending my bug description, and I had tried to turn ON and OFF to see what would happen. Nothing better, worste when ON. That is why I wrote in my description that in the "properties" of the folder where I receive mails, the encoding is "occidental (ISO-8859-1)" and the box "apply default etc." is OFF.

3- Back to the bug, it seems to me that when I receive a mail which contains, among others, a text that has been written with a set of characters which are not recognized by the message compose window, this component looses its right mind and corrupts all the texts, even those with a normal set of characters.

Comment 9

[[:Aureliano Buendía]]

(In reply to comment #8)
> (In reply to comment #7)
> > Gérard Vahée can attach here your email that show the issue (not *.pdf but
> > *.eml)
> > Can also try with workaround in comment #5?
> 
> 1- I do not know how to edit a mail that I have received into an .eml format.
> Can you tell me ?

Select the mail, go to menu-->File-->Save As-->File and save as "Mail Files"  (with extension *.eml)

Comment 10

[Gérard Vahée]

(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Gérard Vahée can attach here your email that show the issue (not *.pdf but
> > > *.eml)
> > > Can also try with workaround in comment #5?
> > 
> > 1- I do not know how to edit a mail that I have received into an .eml format.
> > Can you tell me ?
> Select the mail, go to menu-->File-->Save As-->File and save as "Mail Files" 
> (with extension *.eml)

Re 1- OK, thank you. I attach an .eml example. 
Re 3- I also attach an abstract from the error desk, which shows that the message compose window has problems with that kind of mail

Comment 11

[Gérard Vahée]

Attachment: Example of how the text becomes corrupted when I click on forward

Comment 12

[Gérard Vahée]

Attachment: Errors listed in the error desk

Comment 13

[[:Aureliano Buendía]]

Confirmed also here

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091019 Lightning/1.0pre Shredder/3.0pre ID:20091019031614

with this STR:

1. create a new message with this body
איל שלום,

(as reported in comment #0)
2. send the mail to yourself;
3. when the auto-mail arrive: 
 3.1 open compose window with reply: all is fine;
 3.2 open compose window with forward: body of message not is decoded.

Comment 15

[[:Aureliano Buendía]]

As verified with Nothing user on bug #475933, the issue not is related to Hebrew font but in general to Est European charset (as KOI8-R in bug #475933).
In meantime I dont find any better title. :-D

ps: @Nothing.
Could attach here one of your mail (that is privacy safe for you) using above "Add an attachment" link? (You first shuold save her using menu-->File--Save As-->File)

Comment 16

[Magnus Melin [:mkmelin]]

Steps from comment 13 seems to WFM on linux latest branch nightly.

Comment 17

[[:Aureliano Buendía]]

(In reply to comment #16)
> Steps from comment 13 seems to WFM on linux latest branch nightly.

Here too... I'm very happy for this :-D

Waiting for Eran and [e-mail] confirm?

I'm curious: what bug landes could be fixed this?

Comment 18

[nothing]

Attachment: forward message encodings

test1 - the characters are messed
test2 - everything is fine

Comment 19

[[:Aureliano Buendía]]

Confirm test2 result.

Forward test1 TB here open a compose window empty


Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091028 Lightning/1.0pre Shredder/3.0pre ID:20091028031844

Comment 20

[Magnus Melin [:mkmelin]]

Comment on attachment 396150 [details]
Errors listed in the error desk

The error console css warnings aren't relevant.

Comment 21

[Magnus Melin [:mkmelin]]

Yup. test1.eml from that rar file doesn't work when trying to forward

Comment 22

[Rune Kock]

The problem occurs when the message to be forwarded is in a different charset than Thunderbird's default -- which seems to be ISO-8859-15 (I don't seem to be able to change that.  Some other bug perhaps).

So if I try to forward an UTF-8 message, every non-ascii char gets garbled.  Thunderbird just copies the message byte-by-byte without any regard to charset.

I have tried looking at the source, more specifically at nsMsgComposeService.cpp.  Back in november 1999, Jean-Francois Ducarroz wrote a comment in the function OpenComposeWindow:

/* Actually, the only way to implement forward inline is to simulate a template message. Maybe one day when we will have more time we can change that */

This seems to be the heart of the matter.  There isn't much reason to bother with charsets for templates, but they are essential for forwarding.

I strongly fear that fixing this is beyond me, and can only hope that a wizard actually does get some more time one day.