Vimium: Cannot input successive Japanese/Chinese/Korean words on MacOS

Created on 15 Jan 2018  Â·  8Comments  Â·  Source: philc/vimium

When I input some texts written in Japanese/Chinese/Korean, I cannot input any characters following a Japanese/Chinese/Korean word before searching. These languages need to type <enter> key to convert characters to a word that makes sense, but I cannot search two successive words because of this problem.

This problem arises both in find mode and in search window.

Environment:
Mac OS: High Sierra 10.13.1
Google Chrome: 63.0.3239.132 (Official Build)(64 bit)
Vimium: 1.62.4

I put an example below.

output

Most helpful comment

You mean when you entering CJK phonetics in a Vimium input and press Enter intending to confirm the words conversion, Vimium always immediately catches the Enter as send, right?

I cannot repro on Windows, tried Chinese and Japanese IME.

All 8 comments

These languages need to type <enter> key to convert characters to a word that makes sense,

Is it just <Enter> on its own, or is there also a modifier?

Just <Enter> on its own.
In Japanese, only <Enter> key decides what Japanese words I type.
According to my trying to search in other languages, this rule appears to be applicable to Chinese/Korean.

How do other sites differentiate between <Enter> meaning done, and meaning convert characters?

E.g., Whatsapp, where <Enter> normally means send.

Same problem occurs in sites like that.
(Actually I tried only in Slack)

You mean when you entering CJK phonetics in a Vimium input and press Enter intending to confirm the words conversion, Vimium always immediately catches the Enter as send, right?

I cannot repro on Windows, tried Chinese and Japanese IME.

@innaterebel
Thank you for perfect explanation! That's right.

I'm using the Chinese Pinyin IME of Windows 10, and <space> is used to select a word, so I haven't seen such a problem. And when the IME is enabled, <Enter> only types letters to a Vimium input (not commits them).

I tried on Windows10 and Ubuntu16.04, but I cannot repro this problem. This problem seems to be unique to MacOS.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jkbbwr picture jkbbwr  Â·  3Comments

devanshuDesai picture devanshuDesai  Â·  4Comments

JulianDeal picture JulianDeal  Â·  3Comments

everyonesdesign picture everyonesdesign  Â·  3Comments

Poseiden picture Poseiden  Â·  3Comments