Add Turkish (Türkçe) UI localization
Feature request — please consider adding an official Turkish language option to the Command Code desktop app.
What I did
The desktop app (v0.1.19) currently ships an English-only UI; the locales/*.pak files only cover Chromium's built-in dialogs, and there is no language setting in the app. To help out, I localized the bundled renderer UI strings to Turkish and verified them:
- Translated the main UI strings across the workspace, settings, browser/design, source, terminal-find, auth and onboarding screens (~712 unique strings).
- Replaced only exact string literals in the renderer bundles (quoted strings), leaving code logic untouched.
- Verified every modified bundle still parses cleanly and that
aria-label/selector references stay consistent.
The full English → Turkish mapping is attached as commandcode-tr.json.
Notes for integration
- Strings that are intentionally left in English: brand/proper names (Command Code, Claude, Anthropic, GitHub Copilot, OpenAI, Playwright, etc.), file names (README.md, Cargo.toml, ...), theme/font names (Pierre Dark, Geist, ...), and internal enum/mode values (e.g. permission mode values such as
ask, plan).
- A few strings are embedded inside template literals or used as keys/selectors (e.g. the composer
aria-label), so they need the same treatment on both sides when wiring into an i18n system.
- Translation pairs are provided as a plain
en -> tr map so they can be dropped into whatever i18n mechanism the app uses.
How I applied it (for reference)
Packaged-app localization via careful string replacement in resources/app/out/renderer/assets/*.js, using a tokenizer that only rewrites complete quoted string tokens (handles single/double quotes, template literals and ${...} expressions, and skips regex literals).
I'd be glad to refine the translations, split them by screen, or adapt them to your i18n format if you tell me what the app's localization pipeline looks like.
Attached: commandcode-tr.json (712 English → Turkish pairs)
Add Turkish (Türkçe) UI localization
Feature request — please consider adding an official Turkish language option to the Command Code desktop app.
What I did
The desktop app (v0.1.19) currently ships an English-only UI; the
locales/*.pakfiles only cover Chromium's built-in dialogs, and there is no language setting in the app. To help out, I localized the bundled renderer UI strings to Turkish and verified them:aria-label/selector references stay consistent.The full English → Turkish mapping is attached as
commandcode-tr.json.Notes for integration
ask,plan).aria-label), so they need the same treatment on both sides when wiring into an i18n system.en -> trmap so they can be dropped into whatever i18n mechanism the app uses.How I applied it (for reference)
Packaged-app localization via careful string replacement in
resources/app/out/renderer/assets/*.js, using a tokenizer that only rewrites complete quoted string tokens (handles single/double quotes, template literals and${...}expressions, and skips regex literals).I'd be glad to refine the translations, split them by screen, or adapt them to your i18n format if you tell me what the app's localization pipeline looks like.
Attached:
commandcode-tr.json(712 English → Turkish pairs)