Closed
Bug 30304
Opened 26 years ago
Closed 26 years ago
Short-cut keys for copy/paste are not working while IME is turned on.
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
WONTFIX
M15
People
(Reporter: ji, Assigned: tajima)
Details
(Keywords: relnote)
OS: RH6.0 + Japanese package
While Japanese IME is turned on, short-cut keys for copy/paste (Alt c and Alt
v) are not working. This is very inconvenient. We have this function
working for windows.
Steps of repro:
1. Launch composer in Ja locale
2. Trun on Japanese IME by pressing Shift + space key
3. Enter Japanese chars in the editor.
4. Highligh those JPN chars you enters and press Alt c
you'll see the highlighted chars are erased,
Comment 1•26 years ago
|
||
Is that true the IME will EAT the key up/down event ?
Assignee: ftang → tajima
| Assignee | ||
Comment 2•26 years ago
|
||
Accepted. I'll look into it, but from Monday.
Status: NEW → ASSIGNED
Target Milestone: M15
| Assignee | ||
Comment 3•26 years ago
|
||
Kinput2's problem. It seems that kinput2 does not
check Mod1Mask of input events. Actually, typing
Alt+c on kterm while Japanese conversion is ON
just inserts a character for 'c' into precomposed
window. I also verified Alt+c on Mozilla works fine
using Sun's XIM while japnese conversion is ON.
| Assignee | ||
Comment 4•26 years ago
|
||
The highlighted chars are erased when you type
Alt+c while conversion is on, because kinput2
returns a plain 'c' instead of Alt+c, and it replaces
the previous selected chars with that 'c'. I don't
think we can fix the problem by modifying Mozilla codes, but kinput2 must be
fixed.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
How do we file bugs against kinput2?
This info should be added to the release notes.
Keywords: relnote
| Assignee | ||
Comment 6•26 years ago
|
||
Bob, this is from README file of kinput2 source,
included in redhat6.1 ja source distribution:
* Bugs
If you find a bug, please send a bug report to kinput2@sra.co.jp.
Please don't forget to include the description of your environment (your
machine, OS version, X window patchlevel, etc.) as well as the version
of kinput2 ("kinput2 -version" prints version information).
Filed a bug to kinput2@sra.co.jp and will release note this bug.
This is the reply from the engineer working on kinput2. Tajima-san,
please take a look at it and let me know if I need to reopen or file a
seperate bug for it. Thanks.
don't think it is a kinput2's bug. kinput2 simply performs
XLookupString() on the Alc+c keypress event, and alas, XLookupString()
returns ASCII character 'c'. Maybe kinput2 should check Alt modifier
on keypress events and avoid calling XLookupString()..
Anyway, there is a work around. If you just want kinput2 to send back
Alt+c to the application, add the following line to the definition of
mode "All" in file ccdef.kinput2.
"" mod1-c "" send-back
The default definition of mode All looks like:
mode All "?"
### ...
### ...
### ...
"" control-Kanji "" end-conversion goto Kana
"" shift-space "" end-conversion goto Kana
... more lines ...
endmode
Insert the above line anywhere between "mode All" and "endmode".
If this doesn't work for you, please let me know.
-- ishisone@sra.co.jp
| Assignee | ||
Comment 10•26 years ago
|
||
Teruko-san, please try the workaround solution Ishisone-san mentioned,
and let me know whether it works or not.
If it works, we should write this information in Mozilla release notes.
| Reporter | ||
Comment 11•26 years ago
|
||
Changed the ccdef.kinput2 file in /usr/X11R6/lib/X11/ccdef as told.
But it didn't actually help.
1.On kterm window, with IME on, pressing Alt C does't erase the highlited
chars, but an extra c is inserted, and it dones't get the chars into the
buffer because pressing Alt v doesn't get those chars copied.
2. On mozilla's mail compose page, situation doesn't change at all.
Pressing Alt C still erase the highlited chars.
I'll write Ishisone-san an email about this. At the same time, we may need
to investigate why mozilla doesn't get better as kinput2 does with the
workaround.
You need to log in
before you can comment on or make changes to this bug.
Description
•