scan code 0073 and 7E are not unknown

[Sam4p-code]

Hi
in the key list, scan code 0073 and 7E are labelled unknown.

scan code 0073 is IntlRo
is located between the key / and a shorter Right Shift key.
see
https://kbdlayout.info/kbd106/scancodes
VK_OEM_102 Labelled \ろ (ro) on a Japanese keyboard, scan code 0073

https://kbdlayout.info/KBDBR/scancodes
https://www.w3.org/TR/uievents-code/#keyboard-104
VK_ABNT_C1 on Portuguese (Brazil ABNT) Layout, scan code 0073
VK_ABNT_C2 on numpad (key .) scan code 007E

Thanks in advance for the update.
And millions of thanks for this wonderful software!

[DreymaR]

True: The ABNT_C1/2 keys should be named, and the JIS keys preferably too.

Common Japanese Keyboard Scan Codes (Set 1):

Hiragana/Katakana/Romaji: 70
Henkan (Conversion): 79
Muhenkan (Non-conversion): 7b
Hankaku/Zenkaku (Half/Full-width): 29

The scan code 29 is duplicate with ISO/ANSI so don't rename that I guess!

[randyrants]

Henkan and Muhenkan are in there, under the Special section. 70 isn't because I don't think that was stabilized across HW vendors when I started the project. Or maybe it was something with the old NEC PCs. I don't remember.

For International keys, I've tried to sidestep the particulars of a keyboard layout entirely. For example, ro maybe ro for ja-JP but something entirely different for another language. Like I would expect that A-Z scan codes to be anything from a to wo with a few ten-tens thrown in for a Japanese layout and something entirely different for a Cyrillic layout. It's something I discussed at length when the PowerToys team started specking out their keyboard remapper, because they were approaching the problem space from a different angle, such that they might actually need to be keyboard layout aware in ways that Windows and SharpKeys didn't.

The good news is that even if the label in SharpKeys says "unknown" it is just calling out its own ignorance of the key: it can still be remapped within Windows without a second thought.

[Sam4p-code]

Hello, thank you both for your two comments.
I understand your point of view. I would like to add a few points in order to provide complete points of view.

An "old NEC PC" only respects the Japanese standard. At the moment, Asus or Lenovo, for example, produce laptops with these keys for the Japanese market. This is generally rare in the field of laptops to fully comply with the national standard.
For the Japanese standard (JIS), we see:

• For suggestions: Henkan (Conversion) 79 and Muhenkan (Non-conversion) 7B
• For the character style: Hiragana / Katakana / Romaji (Kana) 70 and Hankaku /Zenkaku (Half/Full Width) 29. This 29 key creates a problem, this OEM key is missing for alphabet/signs purposes, and a 7D key (OEM5) is added for the last column (Sharpkeys called it Special Yen) before Backspace.
• For a complete syllabary: the 73 VK_OEM_102 key labeled \ro (ro) on a Japanese keyboard is the exact equivalent of the European OEM_102 key (scancode 0056).

Since all these keys are present on the JIS keyboard, it is strange that not all of them are labeled in sharpkeys, but only 79/7B/7D. Concretely, it is impossible to type Japanese text without the Kana 70 key, so I don't understand that your initial list lacked this key if others are listed.
70 could be called "Special JIS Kana", and 73 "Special JIS 102".
In addition, the Korean keys (Hangul and Hanja) are already both present in the list. And you know how jealous they could be sometimes...

The Brazilian standard ABNT2 (released in 1990) is a rare keyboard standard to also have additional keys: the European 0056 (OEM_102), and the Japanese 0073 (VK_ABNT_C1 for Brazil), plus 007E on the numeric keypad (key . VK_ABNT_C2). Therefore, if Japan and Korea are allowed to have special keys in Sharpkeys, 007E could be called "Special Brazil C2".

As you said, Sharpkeys is already working fine.
The labels in the list are only intended for information, and knowledge dissemination.

Note: If you find it unnecessary to update the software for informational purposes only, I suggest adding a filtering option in both lists (when we map two keys) in order to help find a key by the name or the code of the label. It's a pain the first few times when we don't know how the list is sorted.