** Observed with 5/23/99 Win32 build ** 1. Send yourself a msg from 4.6 in Japanese with the Subject and body in Japanese. With 4.6, you can copy paste this string wit the Character Set set to Japanese (Auto-Detect) on your browser. As long as the new Composer's Character set is set to Japanese (Auto-Detect) and your global default set to Japanese, this should work. http://kaze:8000/ldapstring.txt 2. Receive this msg with 5.0 Messenger 3. Confirm that the message header is displaying correctly on the thread pane header. 4. Now engage the "reply" button. 5. Note that the quoted subject is in raw MIME-encoded format rather than showing as Japanese. Reply/Quote in Japanese is part of the International requirements for M6. This then has to be working for M6. Naoki, if this is still true, please set the TFV to M6.
I think this is a widget problem, we need to switch to Ender. I checked in the debugger that messenger is passing correct Unicode String (for Japanese) to the widget (nsIDOMHTMLInputElement).
*** Bug 8460 has been marked as a duplicate of this bug. ***
There seems to be a problem in general with UTF-8 encoding. Currently, sending META tags to Ender doesn't let you edit the document. I've turned off UTF-8 output in quoting until we can get this fixed. Also, added akkana to the cc list. Shoot for M9 on this one. - rhp
I have a fix for this in my tree. Now that the Ender problem of reloading URL's has been fixed, I can checkin in my fix when the tree opens. This is a simple libmime change of stuff that I commented out (emitting META tags). - rhp
** Checked with 7/30/99 Win32 build ** This is now fixed. Currently because we are not using GFX widget in the subject field, we see dots instead of Japanese characters, but when the GFX widget.mode=2 is set, you actually see Japanese indicating that MIME headers are getting decoded properly. Rich, should the GFX widget thing be part of this bug? If not, I'll go ahead and mark it verified.
The GFX widget falls under Jean-Francios's area so I wouldn't mix the two. - rhp
Marking it verified as fixed based on the results of testing with 7/3099 Win32 build.