@Egon-Olsen , @Alan-Kilborn , @Ekopalypse
Yeah, it’s the old new thing about keyboard layouts.
On all PC keyboards world wide, no matter of which locale, keys have the same scan codes depending on their physical position on the keyboard. The keyboard driver for a certain locale translates them (under Windows) into virtual key codes. That’s what applications see when they read keyboard input. These virtual key codes are translated into the actual glyphs of the characters (at the end of the day a bitmap image) when they are displayed on the screen.
If the keyboard driver supports so called “dead keys” it waits for a second key press to compose them to a resulting character, e.g. all these â,ê,î,ô,û,… letters used in various european languages. This way there are not so much weird key combos to input these characters.
Unfortunately, in the shortcut mapper of Notepad++ all this isn’t taken into account. The person who programmed the key selector has used a hard coded table for the mapping of physical keys to their character representation, which is wrong for most locales. I wasn’t able to figure out yet, which keyboard locale this person used as a basis for the mapping.
This is the mapping table for german keyboards between the key list in Notepad++'s shortcut mapper and the physical keys:
| Npp shortcut mapper | German Keyboard | | |---------+------------| | | solo | with SHIFT | |---------------------+---------+------------| | ~ | ö | Ö | | - | - | _ | | = | + | * | | [ | ß | ? | | ] | ´ (DK) | ` (DK) | | ; | ü | Ü | | ' | ä | Ä | | \ | ^ (DK) | ° | | , | , | ; | | . | . | : | | / | # | ' | | <> | < | > |(DK) marks dead keys.
I often thought about filing an issue about that but I think it will be nothing more than another forgotten minor bug in the issue tracker…