Punctuation keys move with language layouts, so the same physical key emits different characters

What it is

Letter grids on many Latin layouts look roughly alike; punctuation does not travel with them. US QWERTY Shift on the number row yields !@#$%. German QWERTZ parks ß, ü, and brackets elsewhere. French AZERTY often puts digits on a Shift layer, and semicolon, quotes, and slash each move a step. A physical key emits a scan code; the character is looked up in the layout table. Muscle memory that says “right pinky types a quote” types a different mark after a regional switch.

Why it happens

The OS translates hardware scan codes through a table that changes with the input source. Punctuation is more bound to orthography than letters are: French needs accented letters and «», German needs umlauts, Spanish needs inverted questions, so those characters crowd the number row, the right-hand symbol cluster, or an AltGr layer. The letter field can still “look similar”; the symbol field almost cannot be touch-typed across layouts. Software that treats a scan code as a character—hard-coding “the key left of 3” as a path separator—receives an unrelated token under another table. This is a different layer from mnemonic shortcuts drifting with letters: literal output breaks even when the app defines no shortcuts at all.

Studying it

Give bilingual typists short strings that include paths, regex, currency, and quotes, switching only the input source, not the hardware. Record glances, hesitations, and substitution errors per punctuation class. Code character errors separately from adjacent-key misses. A scan-code log that maps one physical key to Unicode under en, de, and fr sources shows the migration directly. English-only punctuation materials systematically understate the regional gap.

Where it stops holding

Programmers and command-line users feel symbol placement more; prose with a small punctuation set is hurt less. Soft keyboards often redraw the whole symbol page for the current language, weakening the “same physical key” problem, though an attached desktop board still has it. Custom drivers can pin symbols to scan codes, at the cost of fighting the system input source. In East Asian pinyin, punctuation often has an extra Chinese/English punctuation mode, so regional layout differences stack with IME mode.

Applying it

• When users must enter paths, wildcards, or currency signs, offer a visible insert control or a pasteable example rather than copy that says “press this key.”
• Parse input by character (/, \, ,), not by key-code position.
• Keyboard callouts in screenshot tutorials must name the layout; do not ship the same highlight art unchanged to German and French markets.
• Verify by typing the product's special-character list under en, de, and fr sources, listing which marks come from the same physical key and which need another key or layer.

Related

• Same group: C6.18.1 ISO and ANSI boards differ in Enter and left-Shift geometry, a gap software cannot close · C6.18.3 Non-Latin boards often print dual legends, with layout switching selecting the writing system · C6.18.4 Training and documentation driven by regional layouts must be prepared per region, not shared as one copy
• Adjacent: C6.01 QWERTY and layouts · C6.21 Dead keys and layered layouts
• Search: punctuation layout · AZERTY · scan code mapping