Created attachment 147825 [details]
Video screencast when inputting Chinese characters
When I input Chinese characters in Writer/Calc/Impress... in CODE 4.0, it will show double words instead of one with each input.
A screencast video is attached.
The bug is not reproducible on Windows. It must be some strange interaction of IME and browser on Linux.
@Franklin: what is your IME software? I tried on my openSUSE, and my IME looked different, and also it worked OK with CODE.
(In reply to Andras Timar from comment #2)
> @Franklin: what is your IME software? I tried on my openSUSE, and my IME
> looked different, and also it worked OK with CODE.
gcin, running on Kubuntu 18.04.
Franklin, could you please share instructions on how to set up and use gcin? Installing it is easy, but when it comes to using the tool, unfortunately not so much.
(In reply to Aron Budea from comment #4)
> Franklin, could you please share instructions on how to set up and use gcin?
> Installing it is easy, but when it comes to using the tool, unfortunately
> not so much.
After installing gcin
1. make sure you are under locale zh_TW.UTF-8 (so you should probably install ubuntu with zh_TW)
2. there should be two files: 26_gcin.conf and 26_gcin.rc under /usr/share/im-config/data
3. run im-config with your own account (not root) to select user input method. You can probably override LC_ALL=C im-config to understand the messages. Answer Yes in the second window then choose gcin.
4. logout (restart X-window or dm) and login again
5. make sure the following environment variables are set:
$ env | grep IM
(In reply to Franklin Weng from comment #5)
> After installing gcin
Thank you for the detailed steps! What is still unclear to me, how do I switch between English and Chinese layouts?
However, in the meantime I managed to reproduce the bug with other input methods as well. Apparently the bug only occurs with Chrome/Chrome-based browsers.
(In reply to Aron Budea from comment #6)
> (In reply to Franklin Weng from comment #5)
> > After installing gcin
> Thank you for the detailed steps! What is still unclear to me, how do I
> switch between English and Chinese layouts?
Ctrl-space can switch between English and Chinese input mode.
Ctrl-Alt-1, Ctrl-Alt-3, ... can directly switch to certain Chinese input method, and then Ctrl-space can switch back to English.
BTW, that's why the shortcut key "Ctrl-space" in Calc can not be used in CJK because it conflicts with our input method engine. But that's another topic.
> However, in the meantime I managed to reproduce the bug with other input
> methods as well. Apparently the bug only occurs with Chrome/Chrome-based
Yes, I found it too. I can input normally in Firefox but not in Google chrome.
*** Bug 122795 has been marked as a duplicate of this bug. ***
I also have this same problem with Chromium based browsers.
This phenomenon does not occur with Firefox. And in Calc, there is no problem with Chromium based when inputting characters into the text input section at the top, not in cells.
Since the timing* when the input method changed in the smartphone version (or narrow window display on desktop PC), but iOS has a problem with input.
*When the blue input mode button is on the lower right of the screen.
There is no problem if the user naturally inputs 2-byte characters. An error occurs when the user tries to convert characters into Chinese characters.
When the user converts an input character into Chinese characters, first, all characters before conversion are input as they are. Then, only one Chinese character(1 word) is added to the end of the previous character. All characters after the second character after Chinese characters conversion are cut.
I want the smartphone version to revert to the old system.
When the window size is narrowed by desktop PC, it changes to the smartphone mode. Blue input button displayed at the bottom right.
At this time, if the user inputs Chinese characters ignoring the blue button, this problem does not seem to occur by Chromium based browser.
Should be fixed by the following two commits. Thanks to Henry Castro for the fixes.
author Henry Castro <email@example.com> 2019-04-11 14:22:15 -0400
committer Henry Castro <firstname.lastname@example.org> 2019-04-12 15:26:56 +0200
lok: add missing parameter to PostExtTextInputEvent function
author Henry Castro <email@example.com> 2019-04-11 14:12:32 -0400
committer Henry Castro <firstname.lastname@example.org> 2019-04-12 15:24:42 +0200
loleaflet: fix the input method when receives 'compositionend' event
Fixed in CODE confirmed. Thanks.