276663 - Chinese Characters turned to ??????? signs when import emails from Outlook

Status: RESOLVED DUPLICATE of bug 207156

(Thunderbird :: General, defect)

Description

[sureland]

I have installed Thunderbird 1.0 on both my Dell D600 and IBM ThinkPad R30 at
the way,  However, it happened to my Dell D600 that the emails imported from
Outlook lost all Chinese characters in all message bodies, while the Chinese
characters in Subjects can be read. 

I don't have any problems on my IBM ThinkPad R30.

Comment 1

[David Boettger]

(In reply to comment #0)
> I have installed Thunderbird 1.0 on both my Dell D600 and IBM ThinkPad R30 at
> the way,  However, it happened to my Dell D600 that the emails imported from
> Outlook lost all Chinese characters in all message bodies, while the Chinese
> characters in Subjects can be read. 
> 
> I don't have any problems on my IBM ThinkPad R30.

CONFIRMED on a Dell X300 (WinXP Pro SP2, TB v1.0.2 build 20050317, Outlook 2002
SP3 build 10.6515.6735). The character encoding which is causing the problem on
my machine is GB2312 (simplified Chinese). Please note that the problem is NOT a
failure to migrate the user's character encoding selection, but actual
corruption of the characters themselves during import. Composing and receiving
emails using the GB2312 character set works fine.

Resolution of this bug is critical for users who require Chinese language
support; TB is unusable otherwise.

Comment 2

[Ben Wing]

(In reply to comment #1)
> (In reply to comment #0)
> > I have installed Thunderbird 1.0 on both my Dell D600 and IBM ThinkPad R30 
at
> > the way,  However, it happened to my Dell D600 that the emails imported from
> > Outlook lost all Chinese characters in all message bodies, while the Chinese
> > characters in Subjects can be read. 
> > 
> > I don't have any problems on my IBM ThinkPad R30.
> CONFIRMED on a Dell X300 (WinXP Pro SP2, TB v1.0.2 build 20050317, Outlook 
2002
> SP3 build 10.6515.6735). The character encoding which is causing the problem 
on
> my machine is GB2312 (simplified Chinese). Please note that the problem is 
NOT a
> failure to migrate the user's character encoding selection, but actual
> corruption of the characters themselves during import. Composing and receiving
> emails using the GB2312 character set works fine.
> Resolution of this bug is critical for users who require Chinese language
> support; TB is unusable otherwise.

I see this too.  It doesn't happen only with Chinese but with Arabic, 
Russian, ...  sometimes Latin-2, also.  Even when the characters themselves 
aren't corrupted, the charset in Content-Type: is often typically wrong.  Both 
problems are worse in mail received directly from Outlook than mail imported 
into Outlook from Netscape Mail; I suspect Outlook is deleting or not inserting 
a Content-Type: header and TB is being stupid and not fixing it.

Comment 3

[Pierre]

*** This bug has been confirmed by popular vote. ***

Comment 4

[Igor Velkov]

I can confirm this bug for UTF-8 encoded russian and latvian letters. I look into mailbox with FAR file manager - it is not viewer problem, '?' character in place of letters.
Nightly build of Thunderbitd was used.

Comment 5

[Igor Velkov]

Looks like duplicate of bug #207156.

Comment 6

[ovidiu]

bug 359785 seams same