** Observed with 4/13/99 Win32 build ** When I tried to input Japanese into the mail header field using Japanese IME on Windows, there is no connection between the IME and the input field and nothing shows up there. (We cannot input via copy/paste and this has to be also filed as a new bug.)
Naoki, please set the TM.
See also Bug 5063 -- copy/paste does not work well for Japanese strings.
This is needed for M5 (to support MIME encode for Japanese). Bob, who should I assgin this, xpfe?
This may related to dom, I added a comment in 5063.
Reassigning to Eric based upon Vidur's comment in bug 5063. This is blocking the M5 deliverable for sending Japanese email.
This smells like a widget issue to me, and a platform-specific one at that. Passing to Rod (looks like you did a large amount of the textarea widget work for windows?). CC'ing XP Widgets and Linux Widget folks, as this issue probably needs to be addressed by them as well.
This is possibly a Windows toolkit bug. Currently, we are using the MS-Windows standard text and textarea controls within the widget toolkit. I am not sure why copy/paste of Japanese strings do not work, because that should all be native windows clipboard stuff. I can help take a look at this, but I am going to need some help. I don't have a clue about IME or what is even potentially wrong here.
The forms text widgets are planned to be Ender-based. Is that correct? I think we should focus on switching to Ender and not worry about the intermediate native widget implementation.
Updated Summary by prepending "[I18N/ENDER]" as was done for 5063.
Adding to QA Blocker radar.
I agree with bob, I don't think we should put a lot of effort into this since we will be moving to Ender text widgets.
Rod, Can we make the switch by M6? Isn't this already working in viewer, so what does it take to get it working in apprunner? We need this because the text widget for the mail headers are using forms -- one of the remaining I18N mail composition problems left. Also we want to start testing forms ASAP. Thanks.
I am not sure where the editor folks are in getting ender to be the text widget/control? Greg, do you know?
Moving to M6 and marking as later
Rod, Shouldn't this be ASSIGNED and not RESOLVED/LATER for M6?
*** Bug 5930 has been marked as a duplicate of this bug. ***
When this is resolved, testing should include the problem mentioned in Bug 5930.
resolving as remind, since we have no plans to test or ship native text widgets. Why is this marked as a QA Blocker? Also, if someone needs to test 5930 when testing this, then 5930 is not a duplicate of this, and should not have been closed.
Should be fixed by Ender-based text widget. See bug #6262.
*** This bug has been marked as a duplicate of 6262 ***
I'm verifying the dyplicate status of this bug.