Import of Japanese emails from outlook does not work correctly.

RESOLVED INCOMPLETE

Status

Thunderbird
Migration
--
critical
RESOLVED INCOMPLETE
12 years ago
10 years ago

People

(Reporter: Atlanx, Assigned: Scott MacGregor)

Tracking

({dataloss, intl})

x86
Windows XP
dataloss, intl

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 2008-05-07)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.12) Gecko/20050915
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.12) Gecko/20050915


Used System: WinXP SP2 eng, Outlook, Thunderbird 1.5
Second Testsystem: WinXP SP2 ger, Thunderbird 1.0.x, Mozilla 1.7.12

I have imported emails from Outlook(not Express) to Thunderbird 1.5.
All worked good but all my Emails from japanese friends have lost the kanjis and are only displaying ??????????(Questionmarks) instead of kanjis.

I have looked in the source code of the emails and there are no kanjis
any more as they should be.

I have rechecked it with importing jap. Emails from Mozilla 1.7.12 to Thunderbird 1.0.2 and there where the jap. Kanjis still in the source code.

This means it is NOT a problem of not installed fonts or wrong set content-type.
Thunderbird 1.5(probably Thunderbird 1.0.x and Mozilla/Seamonkey, too) is loosing the kanjis by importing from Outlook.


I have written this in the mozilla.support.thunderbird newsgroup:
----
Ah, I think this is a big bug in the import program of Thunderbird!!!
I have now checked the message source and the text there is
??????????????????? instead of the kanjis.

And the content type is set right:

Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Antispam: 0 (Mail was not recognized as spam)
X-GMX-UID: kkFjZBlWeSEkcTM9e3QhaXN1IGRvb0DO

????????

I have made a new mail and send this for test to me and there is
the Kanji visible in the source code.

Subject: test
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

&#29483; <- this kanji is displayed correct in the message source on my system and in mozilla, too.

So, the problem is the import filter program of thunderbird.
It looks like it is not working by importing from outlook to thunderbird.
I have tested an import from mozilla 1.7.12 to thunderbird 1.0.2 which worked fine.

----



Reproducible: Always

Steps to Reproduce:
1.Have (working) japaneses Emails in Outlook
2.Install Thunderbird1.5(or probably Mozilla) and import the emails from outlook
3.Try to read the jap. Emails in Thunderbird.

Actual Results:  
All japanese Emails aren't readable any more because of loosing coding.

Expected Results:  
The jap. Characters(kanjis) should still be readable.
(Reporter)

Updated

12 years ago
Keywords: dataloss, jp-critical
Version: unspecified → 1.5

Comment 1

12 years ago
Maybe related to Core bug 207156?
(Reporter)

Comment 2

12 years ago
Looks like. Then the core bug should get reopend because what I have read in the core bug was only that they have found a strange solution over an imap server instead of using mozilla. And the bug was closed automatically without fixing the bug.

And there is no warning at least in mozilla/thunderbird that data get lost.
(Reporter)

Comment 3

12 years ago
With Outlook was meant the Outlook which is delivered with Office XP.
So, I think Outlook XP.

Updated

12 years ago
Depends on: 207156
- jp-critical

Because this is not a problem for Japanese *people*. But this nominate tells me the intl problem, thanks.
Severity: major → critical
Keywords: jp-critical → intl
(Reporter)

Updated

12 years ago
Summary: Import of Japanese emails from outlook does not work correct. → Import of Japanese emails from outlook does not work correctly.
1.5.0.x is no longer supported.

Atlanx, does this still occur with the latest Thunderbird 2.0.0.x?
Whiteboard: CLOSEME 2008-05-07
No additional useful information since last comment -> resolving incomplete.

Please comment if the issue still occurs in the latest supported 2.0.0.14 / trunk nightlies.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.