-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLDR-16604 kbd: jis scancodes incorrect #3282
Conversation
The standard btw. is available here: https://www.shoshin.co.jp/c/cons/oadg/oadghwd.pdf. Physical layouts starting on p. 274. None of them has the physical key that would be number 45. I confirm the Japanese hardware I have also does not have it. It is however, reserved to the expected scancode (p. 286): |
930fde0
to
e574254
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
However, the Korean I belive is KS X 5003:2001 (confirmed 2021). That is available at https://e-ks.kr/streamdocs/view/sd;streamdocsId=72059288176667875. Key numbers p. 9, scan code mapping p. 15. As far as I can tell, the key next to backspace should not be 7D but 2B (with the second row having only 12 keys): Sadly I don't have any Korean hardware myself at the moment, although I can see you can buy both one-row- and two-row-enter keyboards (but also ones missing that key completely), and I suspect the former would have 7D and the latter 2B next to the backspace . Poor people. If we want to have an explicit Korean form I would tend to follow the standard. The other option is already covered by the |
2d20601
to
97c0103
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
CLDR-16604
ALLOW_MANY_COMMITS=true
DISABLE_JIRA_ISSUE_MATCH=true
found in review of keymanapp/keyman#9615