Windows Terminal version
1.25.923.0
Windows build number
10.0.26100.0
Other Software
Terminal.Gui
Steps to reproduce
When running a project from the Terminal.Gui repository with the default AnsiDriver that uses the Kitty Keyboard Protocol, using a Portuguese (pt) keyboard, some pressed keys are not encoded as CSI-u in the input but only as simple characters. The keys in question are «, », ç, Ç, º, ª. Furthermore, since there is no distinction between a pressed key and a released key, the character is printed twice. However, they won't notice this duplication now because a workaround has been introduced to avoid it, although it's not ideal because it gets even more complicated when combined with other keys. Here is an example of how the ç key appears in the input:
ç -> çç
Shift+ç -> ÇÇ
Ctrl+ç - > "ç" -> Ctrl -> çç
Alt+ç -> "\u001bç" -> Alt -> Swallowed up because it wasn't recognized
Ctrl+Shift+ç -> Ç -> Ctrl+Shift -> ÇÇ
Alt+Shift+ç -> "\u001bÇ" -> Alt+Shift -> Swallowed up because it wasn't recognized
Ctrl+Alt+ç -> "\u001bç" -> Ctrl+Alt -> Swallowed up because it wasn't recognized
Ctrl+Alt+Shift+ç -> "\u001bÇ" -> Ctrl+Alt+Shift -> Swallowed up because it wasn't recognized
Expected Behavior
I would expect to receive the key pressed and released with Kitty Keyboard Protocol CSI-u encode.
Actual Behavior
Only receive as described above.
Windows Terminal version
1.25.923.0
Windows build number
10.0.26100.0
Other Software
Terminal.Gui
Steps to reproduce
When running a project from the Terminal.Gui repository with the default AnsiDriver that uses the Kitty Keyboard Protocol, using a Portuguese (pt) keyboard, some pressed keys are not encoded as CSI-u in the input but only as simple characters. The keys in question are «, », ç, Ç, º, ª. Furthermore, since there is no distinction between a pressed key and a released key, the character is printed twice. However, they won't notice this duplication now because a workaround has been introduced to avoid it, although it's not ideal because it gets even more complicated when combined with other keys. Here is an example of how the ç key appears in the input:
ç -> çç
Shift+ç -> ÇÇ
Ctrl+ç - > "ç" -> Ctrl -> çç
Alt+ç -> "\u001bç" -> Alt -> Swallowed up because it wasn't recognized
Ctrl+Shift+ç -> Ç -> Ctrl+Shift -> ÇÇ
Alt+Shift+ç -> "\u001bÇ" -> Alt+Shift -> Swallowed up because it wasn't recognized
Ctrl+Alt+ç -> "\u001bç" -> Ctrl+Alt -> Swallowed up because it wasn't recognized
Ctrl+Alt+Shift+ç -> "\u001bÇ" -> Ctrl+Alt+Shift -> Swallowed up because it wasn't recognized
Expected Behavior
I would expect to receive the key pressed and released with Kitty Keyboard Protocol CSI-u encode.
Actual Behavior
Only receive as described above.