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.
Assigning myself QA contact initially.
QA Contact: lchiang → momoi
Can you try this out with the latest builds. I checked in some fixes for this a few weeks ago.
Status: NEW → ASSIGNED
bulk move to M16.
Target Milestone: --- → M16
I believe this is fixed but I don't have the ability to test it. Give it a shot and let me know!
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
** 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.
Verified with linux 2000060108 comm build. Can import .txt, .tab, .csv abook files which contain non-ASCII data.
Verified with Win32 2000-08-01-05-M17 build.
You need to log in before you can comment on or make changes to this bug.