Closed Bug 356778 Opened 18 years ago Closed 18 years ago

Shift_JIS Subject seems to be wrongly encoded in UTF-8

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 90584

People

(Reporter: haijin.ash, Assigned: mscott)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 The Shift_JIS mail subject on every windows is remplaced by question marks. I checked the character encoding and it is correctly set on Shift_JIS. The subject is also displayed correctly in the source of the mail. The trouble doesn't seem to occur if the mail is encoded in ISO-2022-JP Reproducible: Always
Can you provide a sample message, please? Save it as a .EML file and attach to this bug using the Create New Attachment link, above.
The subject should be テスト, but instead it's ?????? Anyway the mail body display correctly 日本語
The problem with this message is that the subject, while it may be in the Shift_JIS charset, is illegal: it's constructed of the raw bytes. Only ASCII is allowed in mail headers. Non-ASCII values are supposed to be encoded per RFC 2047 ("MIME-encoded"). A couple of workarounds: First, when you view the message, use View | Character Encoding | <set encoding> You need to do this every time you view the message, and it only fixes the header display in the message envelope, not in the thread pane. (You can set this up to always have Shift_JIS and ISO-2022-JP in the list by selecting the Customize List item in that menu.) Second, you can set the folder's default encoding -- right click on the folder, select Properties from the menu. Then the subject will always appear correctly in the thread pane, when the incorrectly-encoded message is placed in the folder with the corresponding charset. The duplicate bug request the feature to use the message body's charset to decode headers.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: