33292 - Make TEXT import utility work for non-ASCII data

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[Katsuhiko Momoi]

I thought there is another bug filed for this, but I can't
find it. So I'll file it to see. 

In Beta 1, we removed TEXT and Eudora modules from the utility
for the Japanese version because they were not ready for Japanese
data, possibly for non-ASCII data. 
This bug is filed to request that the Text import works for this
kind of multi-byte data.

Text data should be stored in the system charset most probably.
This means that there need to be proper conversion from the system
charset to whatever charset is expected by Mozilla -- UTTF-8,
most probably.

Comment 1

[Katsuhiko Momoi]

Assigning myself QA contact initially.

Comment 2

[tonyr]

Can you try this out with the latest builds.  I checked in some fixes for this a 
few weeks ago.

Comment 3

[lchiang]

bulk move to M16.  

Comment 4

[tonyr]

I believe this is fixed but I don't have the ability to test it.  Give it a shot 
and let me know!

Comment 5

[Katsuhiko Momoi]

** Checked with 5/30/2000 Win32 build under Japanese Windows **

Yes, .txt, .csv, and .tab format TEXt importing 
seems to work OK from 4.x into Mozilla now on
Japanese Windows.

I would like to ask my coleagues to try 
importing 4.x exported TEXT files in the above
format under Mac and Linux also. Try this under
Japanese OS or locale, and if possible under one
extra locale whose system charset is not ISO-8859-1,
e.g. Russian. marina might try this under Russian windows
to see if the basic idea of the fix is OK.

Comment 6

[ji]

Verified with linux 2000060108 comm build.
Can import .txt, .tab, .csv abook files which contain non-ASCII data.

Comment 7

[ji]

Verified with Win32 2000-08-01-05-M17 build.