Closed
Bug 24394
Opened 26 years ago
Closed 25 years ago
ACTIVE IME-Kana mode input after switch from korean IME to Japanese IME
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
M18
People
(Reporter: teruko, Assigned: shanjian)
Details
(Keywords: helpwanted)
I installed Grobal IME for Korean to Winnt 4.0J. Japanese IME input mode will change to kana mode after I switch
from Korean IME to Japanese IME.
Steps of reproduce
1. Install Grobal IME for Korean to Winnt 4.0J and reboot the system
2. Launch Seamonkey
3. Open Composer by selecting menu Tasks|Composer
4. Change IME to Korean IME and type some Korean characters
5. Change IME to Japanese IME (make sure you are using Zenkaku hiragana mode) and start typing Japanese characters
Notice that the Japanese input mode is changed to Kana-input mode instead of Romaji-input mode.
I looked at the MS-IME97 property dialog. It says that Romaji-input mode.
This happens in 2000011210 Win32 build under Winnt 4.0J with Korean IME.
This does not happen in 2000011308 Win32 build under Winnt 4.0J with Korean IME.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Comment 1•26 years ago
|
||
The "IME-Kana mode" is referred to the keyboard layout of Japanese character.
Romaji mode mean type key 'a' will get a Katakana A, kana mode you will get a
katakana SA.
It is very hard to reproduce. teruko have that magic finger to reproduce it 50%
of her try. I cannot reproduce > 30% of my try even in front of her.
I think it is a valid bug but very difficult to reproduce by people other than
teruko (again, she have this magic finger) . And I don't think that many people
will use Korean and Japanese at the same time.
Add momoi at the cc list.
Updated•26 years ago
|
Whiteboard: [need help]
Comment 3•26 years ago
|
||
Added m_kato to the CC list.
Comment 4•26 years ago
|
||
add m_kato@ga2.so-net.ne.jp to cc list
Comment 5•26 years ago
|
||
I see that the reverse problem is very easy to reproduce
and does not have to involve Korean IME. All you need is
another keyboard.
Here's a similar problem in reverse.
1. Open JPN IME pref panel and set the input mode default
to "Kana" rather than "Roma-ji". Apply this change
by pressing "Apply" button.
2. Now on Mozilla composer, try the Zenkaku input mode in Japanese.
You will see that you get "underlined" Roma-ji input.
3. Now change to any keyboard you have on your system.
I tried "ru" for Russian. Put in a few Cyrillic characters.
4. Now go back to Japanese. Confrim that it is still in
Zenkaku input mode. Start inputting Japanese.
5. You notice that the input is in "Roma-ji" mode and you see
Hiragana instead of Roma-ji with underline.
6. Check the IME properties dialog -- you find that the
input mode has been changed to "Roma-ji" mode.
I wonder if we are seeing something similar in reverse in Korean IME>
Comment 6•26 years ago
|
||
The above problem is reproducible just about every time
I tried it.
Keywords: helpwanted
Whiteboard: [need help]
Comment 7•26 years ago
|
||
I cannot repro on NT4.0SP6 JPN + WXG2. Probebry IME97's bug??
Let me know that this issue can reproduce on IME98/IME2000 (or Windows 98)
Comment 8•25 years ago
|
||
strange IME issue. Reassign to shanjian for now.
Assignee: ftang → shanjian
Status: ASSIGNED → NEW
| Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 9•25 years ago
|
||
I could not reproduce the problem either way. I guess the original problem might
be cause by bug in MS's implementation. If the bug is still reproducible, please
try to update your global IME module to 5.02. If that does not help, you can
reopen the bug.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 10•24 years ago
|
||
Shanjian, do you have global IME module 5.02? I tried to get it from Microsoft
page, but I was not be able to download it.
| Reporter | ||
Comment 11•24 years ago
|
||
I cannot reproduce this with 7-27-00-0.9.2 build anymore. I mark this as
verified.
Status: RESOLVED → VERIFIED
| Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•