User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 I've been having some problems getting mozilla to display japanese emails correctly. I've tried getting new emails with japanese in them and that works after manually setting the character coding to Japanese(Shift-JIS) but it seems that mail that has been imported from outlook has completely lost the japanese text and been replaced wih question marks. Reproducible: Always Steps to Reproduce: 1. Set up MS Outlook so that it contains mail that has used the MS Windwos Japanese IME to write Japanese text using the standard settings. 2. Use mozilla's import feature in it's mail sub program to import mail from MS Outlook. 3. Attempt to read one of the importat Japanese email messages. Actual Results: All characters which were in Japanese in MS Outlook are now all question marks once imported into Mozilla. Expected Results: Mozilla should have autodetected that Japanese characters are being used in the mail in Outlook and then imported the data correctly without loosing the Japanese text. This problem goes along with the same problem that I have where in order to view newly recieved Japanese mail in Mozilla I need to manually change the character coding setting each time I view the mail. It seems that automatic lanague detection throughout the software could be improved so that importing and viewing japanese mail work without tweaking.

I have similar problems. I want to use mozzilla, but can't convert previous emails to the Japanese system. Is there any way to import files as Japanese shift_jis or something explicitly[sp]? OS: XP Mozilla 1.4 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Importing from MS Outlook.

The specific behavior is that I see is as follows: the header (subject, sender, etc) comes through correctly but the message text consists of question marks in place of Japanese (i.e. double byte) characters. Outlook has a kind on inverse behavior where the message body displays correctly, but the double bytes in the header show up as question marks UNLESS the OS character set is set to Japanese. I'm an amateur, so take this for what its worth, but I wonder if the fact that the message body is being stored by the OS and the OS is not set to default to a double byte character set might be related to this. Also note that I copied the Thunderbird "folders" from the windows PC to an iMac (OS 10.3) and opened up the messages and they look identical to the windows ones. Again, my guess is the error is happening at the time the message is saved in Thunderbird format.

I think I have a workaround for this. It has two parts: 1) make sure you are using Outlook 2003 and the folder containing the Japanese e-mail is in 2003 (i.e. Unicode) format. You may have to create a new personal folder of type 2003 (NOT the 97-2002 option) and then copy the japanese e-mail over to the new (unicode) personal folder. 2) Open Control Panel -> Regional and Language Options and select the Advanced tab. The top option should be something like, "This system setting enables non- Unicode ... Select a language to match the language version of the non-unicode programs you want to use:" Change this to Japanese. You may need your original Windows CD, so have it handy. Reboot. After the import you can reverse step 2) (switch back to English) and the imported e-mail will still show up correctly. I repeated these steps twice and both times ALL of the japanese e-mail came over correctly. I was even able to copy the files over to my Mac and open them with the OS X version of Thunderbird and everything worked flawlessly. Hope this helps to fix any potential flaws in the importer, and if not to at least help anyone else that runs into the same thing. P.S. I'm new to this whole Open Source support thing, so if I should post this to a newsgroup or FAQ to make it easier for the next person to find, please let me know. Thanks

The above workaround might suffice for Outlook 2003 users, but it doesn't seem to work for those of us who have non-Unicode versions of Outlook (i.e., 2002 or earlier). Any ideas?

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.