176839 - Japanese text in applet text field is displayed as garbage

Status: VERIFIED FIXED

(Core Graveyard :: Java: OJI, defect)

Description

[Koike Kazuhiko]

Japanese text in applet text field is displayed as garbage.

http://www.moonstone.jp/chat.htm

Reproduced with 2002102508-trunk/WinXP + Java 1.4.1_01
Not reproduced with 2002102508-trunk/Win98 + Java 1.4.1_01


Original report in Bugzilla-jp:
http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=2745

Comment 1

[Hidehiro Kozawa]

Not reproduced with phoenix 0.2.
Reproduced with phoenix 0.3.
I think regression between 10-01 and 10-15.

Comment 2

[Hidehiro Kozawa]

mistaked...
Not reproduced with mozilla1.2a.
Reproduced with phoenix 0.1.
I think regression between 09-11 and 09-23.

Not reproduced with 1.2b/Win2K + Java 1.4.1_01.
I think that the problem is only in WinXP.

Comment 3

[Hidehiro Kozawa]

Not reproduced with build from cvs "09/22/2002 18:00".
reproduced with build from cvs "09/22/2002 19:00".
Not reproduced with build from cvs "09/22/2002 19:00" with back out Bug 170142.

Patch of Bug 170142 cause this bug.

Back out please.

Comment 4

[Hidehiro Kozawa]

In Japanese, This problem is 'major'.

Comment 5

[Joshua Xia]

reassign to me

Comment 6

[Joshua Xia]

This bug can't be reproduced on

Java(TM) Plug-in: バージョン 1.4.1_01
使用中の JRE のバージョン 1.4.1_01 Java HotSpot(TM) Client VM
+
Mozilla 1.2.1
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

close it.

Comment 7

[Hidehiro Kozawa]

This bug is still reproduced on

Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.2.1) Gecko/20021130
Java(TM) Plug-in: バージョン 1.4.1_01
使用中の JRE のバージョン 1.4.1_01 Java HotSpot(TM) Client VM

When convert Japanese IME, please input at least rather than two kanji letter.

Comment 8

[Hidehiro Kozawa]

Joshua Xia  
do you use Win2K?
this bug is WinXP only...

Comment 9

[Koike Kazuhiko]

Reopening.

Comment 10

[Joshua Xia]

I used Java(TM) Plug-in: Version 1.4.1_01 
Using JRE Version 1.4.1_01 Java HotSpot(TM) Client VM
+
Mozilla 1.2.1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
on Windows XP
and input "ログオンネ" as nickname and login,
My nickname display correctly in name list.

but if I copy some kanji from webpage, it display incorrectly.
It should be problem of code-set.

Comment 11

[Joshua Xia]

Hi, reporter:

Can you provide simple testcase?
or modify the html <object> tag to be <applet> so that we can view the applet by
using appletviewer.

I think this should be OJI/JPI 's bug, check the applet's code-set please.
Thanks!

Comment 12

[Joshua Xia]

Sorry!

I think this should NOT be OJI/JPI 's bug, check the applet's code-set please.

Thanks!

Comment 13

[Hidehiro Kozawa]

one page of reproduce...
http://www.moonstone.jp/chat.htm

I used Java(TM) Plug-in: Version 1.4.1_01 
Using JRE Version 1.4.1_01 Java HotSpot(TM) Client VM
+
Mozilla 1.3a

1.ログオンネ in Japanese Copy & Paste
 -> correct. not broken

2.ログオンネ in Japanese Input Japanese IME
(using Kana-Kanji exchanging mode, input those five candidate-letters 
which has various exchanged letters
and push enter key to determine the real letters all at a same time).
 -> broken.

3.ログオンネ in Japanese Input Japanese IME
(using Kana-Kanji exchanging mode, input only one letter and enter
key to determine the real one. repeat this five time, one by one).
 -> not broken.


Many Japanese reports this bug at many places in JavaApplet.
This is Win XP only.
This occurs after 09/22/2002 19:00 in trunk(only after the patch
Bug 170142).

Comment 14

[Joshua Xia]

->louie

Comment 15

[dsirnapalli]

Need some traction on this bug

Comment 16

[Teruko Kobayashi]

Changed QA contact to myself.

Comment 17

[Teruko Kobayashi]

The original reporter in Japan already verified that this was not reproduciable
in JRE 1.4.1_01 with 1.4b Mozilla.

I tested this with 5-12 trunk (1.4b) with JRE 1.4.1_01 and JRE 1.4.2 beta.  I
could not reproduce this.

Comment 18

[Teruko Kobayashi]

Verified.

Comment 19

[Hidehiro Kozawa]

JRE1.4.1_01 is "REPRODUCE".
JRE1.4.2 not reproduce.
I heared from Sun engeneer, that was JRE bug and fixed jre 1.4.2.

Status & Resolution is no problem.