[Steps] 1. Pre-install CHT Phonetic IME on Win2K if not using CHT Win2K. 2. Launch a new email dialog, put cursor into Subject box. 3. Enable Phonetic IME. 4. Type 'u' and 'l', then press spacebar. The character selector box pops up. 5. Click on PageDown button, then click '6'. A character should be in Subject box. 6. Put cursor into body box, and observe title bar. [Actual] 'No Subject' is displayed in tital bar of the new email dialog. [Additional Information] Can reproduce it on WinNT4.0 and WinXP b2.

make a screen shot please.

ruixu - please add a screen shot showing the problem. Thanks.

same as 94011 except CHT char. Please see my comment in 94011. Marking as WONTFIX

This case is similar with 94011. Since not only native system charset can be supported on WinNT, Win2K and WinXP, I would like to make sure whether we need to fix or not if user use English NS6.1 on a Traditional Chinese Win2K and cause the same problem? Thank you.

I am using English NS6.1 on W2K-Ja and it works great with Ja char.

Yes, you are right. In this case, there are not any problem on Ja Win2K and Sc Win2K definitely. The reason is Ja IME and Sc IME exactly match and handle native charset in Win2K systems, so we cannot see any problem with them, like we used them in any Win9x systems. But, Tc IME and Ko IME have been advanced from their classical Win9x IME to cater for the special marketing request, they not only match the native charset but also handle some others like we known. So, it might be better to improve our code to fit for those advanced IMEs.

Are you saying we have the TITLE BAR problem using NS6.1-En in W2K-Tc? I thought we were discussing about the rendering problem in the TITLE BAR; not the specific IME handling.

What I want to say is some CHT and KOR characters cannot be displayed properly in the TITLE BAR. Those characters are generated by standrad Win2K IMEs. I would like to make sure whether it is only planned to display native charset on the TITLE BAR or not for the current Ns6.1 and later versions, so I can make a change for bug status. Thank you.

So the problem is reproducible on Tranditional Chinese system. Reopened the bug based on Rui's comments.

Rui, do you see the problem on navigator? For example, open a Big5 page with the same title you used for the mail subject.

Rui: according to your last screen shot the chinese char you entered into the Subject field is not showing up on the window caption, right? I believe this is only one char? Then i would ask you to try to enter another one and i guess you would see the first one appearing on the window title. Same is true for non-aascii ( accented chars). If i would enter Alt+0+224 the window title would say " no subject" , after i type a second char the first char appears.

i will log in a seperate problem for the non-ascii chars delayted appearance on the window title that i observed already for a while

Marina: Thank you for your input, and yes, I think that is also a bug. I tried a long CHT string on CHT Win2K with USRTM NS6.1, and got a different result. The CHT characters in subject cannot be picked up into the title bar, please see the attachment A. But if I use [Backspace] key to delete last one, the string can be picked up into the title bar. If the string has the problematic CHT characters, they will become '?' in the title bar. And also, I think it is not only one problematic CHT character here, I don't know how many, but a quite number, they belong to CHS native charset, please see the attachment B as well. Thank you.

Xianglan: this problem happened on the browser as well. I will open the bugs.

So it's a browser generic problem. Changed Product to Browser. Rui, you don't need to open another bug for navigator window.

== assigning to jbetak

accepting...

Reassign to nhotta. This seems to be a generic widget problem, not mail compose specific. Rui, did you use localized traditional Chinese system?

Same as 94011 - generic widget problem. *** This bug has been marked as a duplicate of 97671 ***

Same as Bug 94011, there are 2 solutions to fix 97671. Leave as RESOLVED DUPLICATE for now, and will verify after fixing 97671.

> Rui, did you use localized traditional Chinese system? I am using localized traditional Chinese system, it is a CHT Win2K+SP2. Actually, it is an unicode issue, I am sure it can be reproduced on any MS Windows unicode systems, eg. NT, 2K and XP.