297159 - certain Chinese chars in subject of an email garbled if the email was encoded in GB2312

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[liuhui913]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Maxthon)
Build Identifier: 

send an email which has subject "谢谢" to user itself. Choose the encoding as 
GB2312. The received email will have a garbled subject. This doesn't happen in 
Netscape Mail.

Reproducible: Always

Steps to Reproduce:
1.send an email which has subject "谢谢" to user itself. 
2.Choose the encoding as GB2312.
3.Send the email.

Actual Results:  
лл

Expected Results:  
谢谢

Comment 1

[liuhui913]

(In reply to comment #0)
> User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Maxthon)
> Build Identifier: 
> send an email which has subject "谢谢" to user itself. Choose the encoding 
as 
> GB2312. The received email will have a garbled subject. This doesn't happen 
in 
> Netscape Mail.
> Reproducible: Always
> Steps to Reproduce:
> 1.send an email which has subject "谢谢" to user itself. 
> 2.Choose the encoding as GB2312.
> 3.Send the email.
> Actual Results:  
> лл
> Expected Results:  
> 谢谢

Sorry, since there is some encoding error. The subject chars should be like the 
words in Actual Results(лл). And the actual results is garbled.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[Rod Whiteley]

This problem still exists in Thunderbird 2 (Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0).

Example message source for a message that fails (subject and body should look the same):

MIME-Version: 1.0
Subject: =?gb2312?Q?=D3=A6=C6=B8?= fails
Content-Type: text/plain; charset=gb18030; format=flowed
Content-Transfer-Encoding: quoted-printable

=D3=A6=C6=B8

Example message source for a message that works:

MIME-Version: 1.0
Subject: =?gb2312?Q?=E3=A6=E6=B8?= works
Content-Type: text/plain; charset=gb18030; format=flowed
Content-Transfer-Encoding: quoted-printable

=E3=A6=E6=B8

Comment 5

[Wayne Mery (:wsmwk)]

Rod, do you still see a problem if using version 3?

Comment 6

[Rod Whiteley]

Yes, I still see a problem using Thunderbird 3.0.4 or Lanikai/3.1b2pre. The failing Subject appears to be decoded as if it were UTF-8.