You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some issues with the Japanese keymap display for kana-input usage:
This layout is a 104-key layout, but the shown layout is missing the left-most key on the top row, ろ and the right-most key on the second-from-top row む.
(Based on the keymap data, I don't have a 104-key keyboard to test with): The shifted value of the ほ key should be ー, i.e., the long vowel marker in, e.g., ラーメン "ramen", but currently appears to be ほ.
"Next key" mode does not show the next key if the next character has a marker.
"Next key" mode, when expecting marker input (゛or ゜), shows the next character as the expected key instead.
In the "japanese katakana" language mode, no keys highlight at all.
As an example of the "next" key issues, if the next word to type is すずめ:
Typing ゛, め remains highlighted, and the ず is now bold (correct).
Expected Behavior
In the keymap
The ろ key, and the む key are present.
When holding Shift, ほ keys is replaced with ー.
When the next expected character has a marker, the "next" key press shown on the keyboard should be the unmarked character.
When the next expected keypress is a marker (゛or ゜), that key is highlighted.
In the "japanese katakana" language mode, the hiragana keycaps highlight for their katakana equivalents.
In example of the "next" key issues, if the next word to type is すずめ:
Initially, the す key is highlighted.
Typing す, the す key is still highlighted.
Typing す again, now the ゛ key is highlighted.
Typing ゛, め remains highlighted, and the ず is no longer underlined.
Steps To Reproduce
Enable Kana input and select Hiragana mode in the Microsoft IME
Load the supplied config. Specifically, enables "next" mode keymap with the "japanese hiragana" keymap layout and dynamic legend.
Note the absence of the ろ key in the top row, it should appear to the left of ぬ (`~ key in US English)
Note the absence of the ー key in the bottom row, it should appear to the right of へ (\| key in US English)
Start a "japanese hiragana" test
Note that no key highlight is shown when the next character to type has a marker.
Note that when the next key input is expected to be a marker, the next character's key is highlighted instead.
Environment
OS: Windows 11
Browser: Google Chrome
Browser Version: Version 130.0.6723.58 (Official Build) (64-bit
Anything else?
This keyboard layout is actually an ANSI 104-key emulation of a full OADG 109-key keyboard, which has a slightly different layout for some of the keys. It'd be nice to add another keyboard layout that matches the full OADG109A layout, but that's actually a separate issue (feature request/future simple PR) but which might expose more layout issues as it needs another key in the bottom row.
Also, I had a quick look, and it looks like the missing ろ and む keycaps are in the layout data file, so that part must be a limitation elsewhere.
The text was updated successfully, but these errors were encountered:
Keys in the data file but not shown on the keymap appears to be a generic problem: On examination, even the "qwerty" layout suffers from this, not showing the ` or \ keys.
Did you clear cache before opening an issue?
Is there an existing issue for this?
Does the issue happen when logged in?
Yes
Does the issue happen when logged out?
Yes
Does the issue happen in incognito mode when logged in?
Yes
Does the issue happen in incognito mode when logged out?
Yes
Account name
TBBle
Account config
Current Behavior
Some issues with the Japanese keymap display for kana-input usage:
As an example of the "next" key issues, if the next word to type is すずめ:
Expected Behavior
In the keymap
In example of the "next" key issues, if the next word to type is すずめ:
Steps To Reproduce
Environment
Anything else?
This keyboard layout is actually an ANSI 104-key emulation of a full OADG 109-key keyboard, which has a slightly different layout for some of the keys. It'd be nice to add another keyboard layout that matches the full OADG109A layout, but that's actually a separate issue (feature request/future simple PR) but which might expose more layout issues as it needs another key in the bottom row.
Also, I had a quick look, and it looks like the missing ろ and む keycaps are in the layout data file, so that part must be a limitation elsewhere.
The text was updated successfully, but these errors were encountered: