1

If I input "niji" the option just doesn't show up.
I added it as a custom word in the IME dictionary, but it still doesn't show up.
I have to write "futaji" to get "二時".
Is there a way to make it so "niji" gives you "二時" as an option?

Also, this problem seems to be unique to niji, other times don't have this problem. ichiji becomes 一時, sanji becomes 三時, it really is only niji that gives this problem.

  • This looks like a question for our meta site. I'll flag it to be transferred over there. :) – ajsmart Jul 9 '20 at 15:05
  • Works fine for me. – istrasci Jul 9 '20 at 16:08
  • I migrated your question. To me it looks more like a question for Super User, the Stack Exchange site where you can also ask questions about the Windows OS. I don't see any language-specific reason that niji shouldn't convert to 二時. You do realize that you might have to go down further in the list of suggestions, right? – Earthliŋ Jul 9 '20 at 19:58
3

Just to be clear, the below is all about using the Microsoft Japanese IME that comes in Windows 10. Different versions of Windows IME should work similarly, but I have no idea about third-party IMEs such as ATOK.

Here's what I see when I change to Japanese input mode and type niji:

Initial kana entry

Remember -- you also have to hit the spacebar to tell the IME that you want to convert. That initial pop-up is the IME's attempt at predictive completion. It doesn't convert anything until you hit the spacebar.

After you hit the spacebar, the current kana string (with the squiggly underline) changes to whatever the IME has as its first conversion candidate. In my case, the kana are にじ, and the kanji it changed to is 虹, since that was the kanji I've apparently chosen either most often, or most recently (I forget which), as the conversion for the kana にじ. When I hit the spacebar again, I get a pop-up showing all the conversion candidates:

After hitting the spacebar twice

If this is what you're doing, and you don't see 二時 anywhere in the list of conversion candidates, something is seriously wrong with your IME configuration. Any fix of that is beyond the scope of this answer.

Hope this helps!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .