Closed Bug 492692 Opened 15 years ago Closed 15 years ago

Cannot display Chinese email in UTF-8 by default

Categories

(Thunderbird :: Message Reader UI, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: armsoo, Unassigned)

Details

(Whiteboard: [DUPEME])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Thuderbird/2.0.0.21 (20090302)

Thunderbird can only display most Chinese-encoded email properly when asked to use UTF-8 encoding (View -> Character Encoding -> UTF-8).

As such, I tried but failed to make Thunderbird to apply UTF-8 encoding on all incoming and outgoing email (Tools > Options > Display > Formatting > Fonts > Character Encoding). Even I chose UTF-8, Thunderbird still displays incoming Chinese email in format other than UTF-8.

Reproducible: Always

Steps to Reproduce:
1. Use Yahoo to type a Chinese email
2. Email to an account with Thunderbird
Actual Results:  
Thunderbird does not display character in UTF-8 by default

Expected Results:  
Thunderbird should have applied UTF-8 as default encoding (assuming you have already set to UTF-8 under Tools > Options > Display > Formatting > Fonts > Character Encoding)
I'm sure this is fixed in Thunderbird 3 Beta 2. You can get it at http://www.mozillamessaging.com/en-US/thunderbird/3.0b2/ Please test and report back your results.

xref bug 498156
Whiteboard: DUPEME
Reporter could answer to comment #1, please?
Whiteboard: DUPEME → [DUPEME][closeme 2009-09-09]
Sorry that it took me so long. I downloaded the beta from the link above but the problem persists. However, the subject displays the Chinese character correctly. The content is still scrambled until I manually chose UTF-8.
What charset is specified in mail header?
> Content-Type: text/...; charset=????
> (check all parts in mail if multipart/xxx mail)
What is your choice of auto-detect setting?
>  View/Character Encoding/Auto Detect : ?
What do you specify/select/check(or uncheck) in per folder setting? 
>  Folder Properties/General Information/Default Character Encoding : ?
>  [ ? ] Apply default ... : Checked? Uncheced?
Whiteboard: [DUPEME][closeme 2009-09-09] → [DUPEME]
I used NJStar (Big 5 Traditional Chinese) to encode the original message in Yahoo Mail. I want to point out that the subject line display is fine and the preview of the content is also fine. Only when I double-click and open the message is the content garbled.

View/ Character Encoding/ Auto Detect > Chinese
Folder Properties > General Information > Default Character Encoding is Simplified Chinese HZ. Applied Defaut is checked.

-------------

From - Sat Sep 05 14:08:41 2009
X-Account-Key: account2
X-UIDL: UID2052-1161022945
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Return-path: <armstrongsoo@yahoo.com>
Envelope-to: teyung@teyung.com
Delivery-date: Sat, 05 Sep 2009 16:01:58 -0500
Received: from web81608.mail.mud.yahoo.com ([68.142.199.160])
	by server590.dvservers.com with smtp (Exim 4.69)
	(envelope-from <armstrongsoo@yahoo.com>)
	id 1Mk2OS-0004H7-0z
	for teyung@teyung.com; Sat, 05 Sep 2009 16:01:56 -0500
Received: (qmail 77073 invoked by uid 60001); 5 Sep 2009 21:01:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1252184518; bh=HViOPT1uaHJj/a7oAy3mUuzxmINsz1GuAvz0bOumSKk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=ioH5bm3eo5WRkAz9IbP6zNKzVcQfGLdabNzB3orVwBWjpp6R0vdGYAzAEzXO8pLAs/fWXiK511hbbSk9Wv8kp79bfIcyyGlsb+wDC+yPNzv2WS6uW/+kJgnpDpli8vVmjgyrpid7uA/WWQZ2119MSw18firvYOvY66AFUy/U3wM=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
  b=rsUGHduE1/p6+WAyo6SnRtAd/S07TXxKhiWeDN1dAdzRVWe2h6Bd1O7K8tdOQUoSXf3n7RTndFjbTj3IzshbAfqbR9zC0umX061WJd7ykw1A4qFPLpiy9kugxZNF6FmHR0itZt4QkHRGhnMyVm/2Vh12vGo5U37GDrfKef7ex9I=;
Message-ID: <316467.76647.qm@web81608.mail.mud.yahoo.com>
X-YMail-OSG: KFV7yJAVM1mljZsYAlr1vN2.1Va8qMtyMquj6snC27Jzmm3ArrV4aNTPL.2h98gq3wBi6DmX6v4NVH_nrIepl0IeZHLAs6Z2TsqCncoXruNJ4eAUVrP8PLJmuNXv1G_DGm3Odad8qk0fHTIaq71LXkjIW61oo4kwvRl.g1ezQJNoIIWu6tOmK2Wkyy3ld48g9961N.pFMuSQ9W1rVJW6Ha3e5a4Uo3LRE2CiV77JodhXNfWCG.bwt48r_rrfXA1fKm2Ay7Cr_1XzcCC.vKRROiB0wp.vaUTOssLS2vS.UgjjiohEqiY2nzSNWJ_szee05ioJ0dLe1xk8tET2Sqz30oXpje7_
Received: from [99.187.227.237] by web81608.mail.mud.yahoo.com via HTTP; Sat, 05 Sep 2009 14:01:58 PDT
X-Mailer: YahooMailRC/1358.27 YahooMailWebService/0.7.338.2
Date: Sat, 5 Sep 2009 14:01:58 -0700 (PDT)
From: Armstrong Soo <armstrongsoo@yahoo.com>
Subject: =?utf-8?B?6Kmm5qmf?=
To: teyung@teyung.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-825569436-1252184518=:76647"
X-Antivirus: avast! (VPS 090905-0, 09/05/2009), Inbound message
X-Antivirus-Status: Clean

--0-825569436-1252184518=:76647
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

=E7=B9=81=E9=AB=94=E4=B8=AD=E6=96=87
--0-825569436-1252184518=:76647
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV>=E7=B9=81=E9=AB=94=E4=B8=AD=E6=96=87</DIV></div></body=
></html>
--0-825569436-1252184518=:76647--
(In reply to comment #5)
> Folder Properties > General Information > Default Character Encoding is
> Simplified Chinese HZ. Applied Defaut is checked.

Have you read description of "Apply default ..." of "Folder Properties>General Information"?
Your setting means "Ignore utf-8 in Content-Type: etc. of message headers, and always decode/interpret in Simplified Chinese HZ".
So, phenomenon is that "Apply default ..." doesn't work at preview pane in your environment...

Anyway, if bug summary correctly represents problem of this bug, INVALID.
INVALID per commet 6. Reporter feel free to reopen and explain why this is not invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
There are other emails that are not encoded un UTF-8 (such as base64, gb2312). When I checked View > Character Encoding > Auto Detect > Chinese, I expect Thunderbird will, indeed, auto-detect.

Now I changed the default as UTF-8, I still cannot read email encoded with base64 and gb2312.
Have you read description of "Apply default ..." of "Folder Properties>General Information"?
Have you unchecked "Apply default ..." of "Folder Properties>General Information"?

Please note that "auto-detect" is for mail of no charset in Content-Type:.
Mail data is really binary code of GB2312 which is specified in Content-Type:?
Yes. So now I unchecked the "Apply Default". But there are still messages it can decode unless I have to manually try out each type of encoding.

Just tell me please, what can I do so that Thunderbird can automatically select the correct encoding?
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Your problem of this bug was "Cannot display Chinese email in UTF-8 by default", wan't it? It was already resolved by uncheck of "Apply Default", which you wrongly checked, wasn't it?

If you properly set "Apply Default"=Unchecked, problem on other than UTF-8 mail is different problem.
> other emails that are not encoded un UTF-8 (such as base64, gb2312)
"One problem per a bug" is rule at B.M.O.
Open separate bug for such mail, with clear description about you setting, with detailed description about your operation and phenomenon by the operation, with attaching(never paste, please) mail data, after view/check mail source and mail data(a. what is set in charset, b. really used character encoding as mail data, ...).
Wrong charset is suspected. For (a) : View mail source, and check charset in Content-Type:, <meta> tag in HTML etc. For (b) : Change View/Character Encoding. If mail is displayed as expected, it's really used charset.

Anyway, closing as INVALID again.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.