Kanji is logographic: each symbol is a complete word, phrase, or idea. Hangul is alphabetic-syllabic: each symbol is a segment (vowel-or-consonant), except that they're written in two- or three-letter blocks each representing a syllable.
I'm not sure it's that different IME wise. I only know Chinese pinyin IME, but I assume since Kanji in contrast to Chinese can map to multiple syllables you probably need to keep the state of the last few syllables as well and then let the user choose the appropriate Kanji (if available).
With pinyin input it's the same in Chinese. You enter the Latin characters and the IME gives you options to select from. Also even abstracting from the single syllables you often can narrow down the selection of compound words in Chinese IME if you continue typing. So again state is important.
Correct, this is why I'm wondering. Input is done through hiragana such as "わたし" (or even a step further removed, transliterated from "watashi") and then the IME is triggered to convert it to "私" (or other matches).
On a laptop, my experience is that romaji -> hiragana is as-you-type due to being unambiguous, while the default trigger for hiragana -> kanji is the spacebar, same as described for Korean. Hence my confusion as to how it's different - the individual characters certainly are, but it sounds functionally identical.
On my phone just now, typing this comment, the experience was switching to a Japanese keyboard and inputting the hiragana directly, then the kanji suggestions appeared where autocorrect suggestions normally would.
Typing Hangul is just like typing Latin, Greek, Cyrillic, Hebrew, Arabic, etc., text: one alphabetic unit at a time. The only thing a Hangul IME does is it groups the typed jamo into syllables. The grouping is unambiguous, so there's no need for popups or space presses to guide the grouping.
(If there had been the kind of rendering technology that is used for Indic text today back when Korean text processing on computers started, chances are that the syllable grouping would be handled as rendering-time shaping and not as an input-time IME issue.)
Additionally, Korean IMEs have a feature to convert a word into Hanja, but it's something you need to take action to invoke as opposed to Japanese IMEs offering to convert to Kanji by default.
> The grouping is unambiguous, so there's no need for popups or space presses to guide the grouping.
...that's the opposite of the comments that triggered my question. Multiple people said space is needed to trigger it, then backspace to remove an erroneously-added space character.
Is the answer that they're using it wrong, and are actually inputting a space directly because the IME already acted for them?
