[ENHANCEMENT] Add Hebrew (he) locale support

[lidorshimoni]

Problem (one or two sentences)

Roo Code currently does not support a Hebrew (he) locale, making the interface inaccessible or difficult to use for Hebrew-speaking users.

Context (who is affected and when)

This affects Hebrew-speaking developers and users who prefer or require right-to-left (RTL) language support when using Roo Code. The issue is present across the entire interface, especially in navigation, forms, and text-heavy views.

Desired behavior (conceptual, not technical)

Users should be able to select Hebrew as a language option, with the interface fully translated and properly adapted to right-to-left layout conventions.

Constraints / preferences (optional)

• Ensure proper RTL layout support across all components
• Maintain consistency with existing localization structure
• Consider fallback behavior for untranslated strings
• Keep performance impact minimal

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

I've analyzed the codebase and here's my proposed implementation plan for adding Hebrew (he) locale support:

Changes required across 4 areas:

1. Register "he" in the Language type (packages/types/src/vscode.ts)

   • Add "he" to the languages array (alphabetical order, between "fr" and "hi")

2. Add Hebrew to the language name mapping (src/shared/language.ts)

   • Add he: "עברית" to the LANGUAGES record

3. Create backend translation files (src/i18n/locales/he/)

   • Copy the English namespace files as starting templates: common.json, embeddings.json, marketplace.json, mcp.json, skills.json, tools.json, worktrees.json
   • These will initially contain English strings and can be translated incrementally

4. Create webview-ui translation files (webview-ui/src/i18n/locales/he/)

   • Copy the English namespace files as starting templates: chat.json, cloud.json, common.json, history.json, marketplace.json, mcp.json, prompts.json, settings.json, welcome.json, worktrees.json
   • Add a .gitkeep file for consistency with other locale directories

What's NOT needed (auto-discovered at runtime):

• Both src/i18n/setup.ts and webview-ui/src/i18n/setup.ts dynamically discover locale directories, so no setup file changes are required.

Regarding RTL support:

• The issue mentions RTL layout support. The i18n infrastructure itself (i18next) supports RTL languages, but adding full RTL CSS/layout support across all components is a significantly larger effort and likely warrants a separate issue. This PR would focus on adding the locale scaffolding so Hebrew can be selected and strings can be translated. RTL layout adjustments could follow as a separate enhancement.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[lidorshimoni]

@roomote I approve.

I've seen the approval and will proceed with the implementation. I'll open a PR to share progress shortly.

Opened PR #12021 with my attempt at adding Hebrew locale support. The PR adds the locale scaffolding (type registration, language mapping, and English-template translation files for both backend and webview-ui). Feedback welcome!

[lidorshimoni]

@roomote, please translate all the English template strings to Hebrew, and then I'll review and fix them manually where it's needed.

I've seen your comment and will translate all the English template strings to Hebrew. I'll open a PR with the translations shortly.

All English template strings have been translated to Hebrew across all 17 locale files (7 backend + 10 webview-ui). The translations are pushed to PR #12021. All placeholders and technical terms are preserved. The missing translations validation script confirms complete coverage. Ready for your review and manual corrections where needed!