← Back to AI Insights
Gemini Executive Synthesis

Internationalization (i18n) support, keyboard input handling, integrated terminal functionality.

Technical Positioning
Global usability, robust input processing across diverse hardware/software configurations.
SaaS Insight & Market Implications
This issue exposes a critical internationalization flaw in `tode`'s integrated terminal, specifically with non-US keyboard layouts like French AZERTY on macOS. The inability to type essential characters like `/` or `?` renders the terminal unusable for many developers. The root cause lies in the `Kitty keyboard protocol parsing` failing to request 'report alternate keys,' leading to the loss of layout-resolved shifted characters. This severely limits `tode`'s global market appeal and adoption, as fundamental input functionality is broken for a significant user base. Addressing this requires a deep fix in keyboard event handling and protocol implementation.
Proprietary Technical Taxonomy
non-US keyboard layout French AZERTY shifted punctuation characters integrated terminal editor pane Kitty keyboard protocol parsing layout-resolved character unshifted unicode key code

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Aug 20, 2026
Repo: zenbu-labs/terminal-code
Cannot type `/` or `?` in the integrated terminal with a non-US keyboard layout (French AZERTY, macOS)

# Cannot type `/` or `?` in the integrated terminal with a non-US keyboard layout (French AZERTY, macOS)

## Summary

On macOS with a French AZERTY layout, shifted punctuation characters cannot be typed in the VS Code **integrated terminal** inside tode. `/` (Shift+`:` on AZERTY) and `?` (Shift+`,`) produce nothing (or the unshifted character). Typing in the editor pane mostly works.

## Environment

- tode version: v0.1.13 (code-server 4.132.0)
- Host terminal: Ghostty
- macOS: Darwin 25.6.0
- Keyboard layout: French AZERTY (system input source)

## Steps to reproduce

1. Set the macOS input source to French (AZERTY).
2. Launch `tode` and open the integrated terminal.
3. Type `/` (Shift+`:`) or `?` (Shift+`,`).

**Expected:** the character is inserted in the terminal.
**Actual:** nothing is inserted (or the unshifted base character).

Switching the macOS input source to U.S. QWERTY makes both characters work again, which confirms the layout dependency.

## Analysis (from reading terminal-browser source)

The key event is translated at several layers and the *layout-resolved* character is lost along the way:

1. **Kitty keyboard protocol parsing** — `engine/crates/pixel-core/src/terminal.rs`, `parse_kitty_key()`: the engine keeps the protocol's *unshifted* unicode key code (`:` / `,` on AZERTY) as `Key::Char`. The progressive-enhancement flags requested are `\x1b[>27u` (1+2+8+16), i.e. **flag 4 "report alternate keys" is not requested**, so the shifted key code (`/`, `?`) is ...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from zenbu-labs/terminal-code.

Extracted Positioning
Distribution method, package management.
Adherence to JavaScript ecosystem distribution standards, developer convenience.
Extracted Positioning
UI scaling, multi-monitor support, display rendering.
Adaptive and correct UI rendering across diverse display configurations.
Extracted Positioning
Installation and update mechanism, package management.
Adherence to platform-native package management best practices, ease of maintenance and updates.
Extracted Positioning
Installation process, user onboarding, dependency management.
Streamlined, single-command installation experience.
Extracted Positioning
User experience, application lifecycle management, graceful exit.
Intuitive and reliable user interaction, robust application control.

Frequently Asked Questions

Market intelligence mapped to Internationalization (i18n) support, keyboard input handling, integrated terminal functionality..

What is the technical positioning of Internationalization (i18n) support, keyboard input handling, integrated terminal functionality.?
Based on our AI analysis of the original developer request, its primary technical positioning is: Global usability, robust input processing across diverse hardware/software configurations.
What architecture is tied to Internationalization (i18n) support, keyboard input handling, integrated terminal functionality.?
Our proprietary extraction maps Internationalization (i18n) support, keyboard input handling, integrated terminal functionality. to adjacent architectural concepts including non-US keyboard layout, French AZERTY, shifted punctuation characters, integrated terminal.

Engagement Signals

0
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like non-US keyboard layout and French AZERTY by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.