Closed Bug 15642 Opened 25 years ago Closed 25 years ago

[PP][IME-X]Editor Plain Text-Needs to commit twice to display Japanese chars

Categories

(Core :: Internationalization, defect, P3)

Other
Linux
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: teruko, Assigned: tajima)

References

Details

When you type Japanese characters in the Editor Plain Text Window, you need to
hit the Enter twice to display Japanese characters.

Steps of reproduce
1. Open Plain text Editor
2. Turn on IME by Shift+Space
3. Type Japanese characters like "kannji" in hiragana mode
4. Hit space key to change to Kannji
5. Hit Enter to commit

At this time, Japanese characters is not displayed.
Then, hit Enter again.  Now Japanese characters is displayed.

When you type Japanese characters at the beginnig of the first line, this works
fine. However, if you contine to type Japanese characters, you will see this
problem.

Using Kinput2.  Tested 10-01-M10 Linux build.  This does not happen in HTML
editor.
Status: NEW → ASSIGNED
Accepted, and I'm trying to reproduced the problem, without any luck yet.
Trying to reproduce the problem, without a luck, so far. Any specific engine is
to
be used to reproduce? Wnn6, Canna, etc?
We are using Wnn4.2-9JRPM60.i386.rpm, kinput2-wnn4-v3-2JRPM60.i386.rpm, and
locale-ja-2.1.1.1-2.noarch.rpm.
Tajima-san, I will test again this after I change my linux environment from
your suggestion.
Blocks: 16127
Summary: [PP]Editor Plain Text-Needs to commit twice to display Japanese chars → [PP][IME-X]Editor Plain Text-Needs to commit twice to display Japanese chars
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
This does not apply since Plain Text Editer window is not there.
The plaintext editor now lives in the editor debug menu.
Target Milestone: M12
Teruko-san, have you tested this again with the plantext editor? Will you please
try
this again with latest build?
I tested this in 11-15-12 Linux build.  I found the Plain Text editor from Debug
menu.  I could not reproduce this anymore.
You need to log in before you can comment on or make changes to this bug.