Feature Request: Add Spanish language support (i18n)

[rento27]

Feature Request

Description

Add internationalization (i18n) support to 1Code, starting with Spanish language.

Use Case

Many users in Spanish-speaking countries would benefit from having the UI in their native language.

Suggested Implementation

1. Add an i18n framework (e.g., react-i18next)
2. Extract all hardcoded strings to translation files
3. Add language selector in Settings
4. Start with Spanish (es-MX / es-ES)

Would be happy to contribute translations!

[1code-async]

Task completed.

I've analyzed the codebase and posted an enrichment comment on issue #160. Here's a summary of what I found:

Current State:

• No existing i18n infrastructure - all UI strings are hardcoded in English
• No translation libraries installed
• Strings are scattered across ~12+ settings tab files and various UI components

Key Implementation Points:

• Recommended approach: react-i18next + i18next
• Language preference can be stored using the existing Jotai atomWithStorage pattern
• Existing platform locale detection in src/main/lib/terminal/env.ts could be leveraged for auto-detection
• date-fns (already installed) has locale support for date formatting

Files Identified:

• src/renderer/lib/atoms/index.ts - Add language preference atom
• src/renderer/components/dialogs/settings-tabs/agents-preferences-tab.tsx - Add language selector + 458 lines of strings to extract
• src/renderer/features/settings/settings-sidebar.tsx - Tab labels to translate
• All settings tabs in src/renderer/components/dialogs/settings-tabs/*.tsx

No duplicate issues were found for this feature request.

---

View full conversation

Powered by 1Code

[1code-async]

Codebase Analysis for i18n Implementation

Thanks for this feature request! Here's an analysis of what would be involved:

Current State

No existing i18n infrastructure - All UI strings are currently hardcoded in English directly in React components. There are no translation libraries or language files in the project.

Key Files to Modify

File	Purpose
package.json	Add i18n dependencies (e.g., react-i18next, i18next)
src/renderer/lib/atoms/index.ts:365-460	Add preferredLanguageAtom for language preference storage
src/renderer/components/dialogs/settings-tabs/agents-preferences-tab.tsx	Add language selector dropdown (458 lines of hardcoded strings to extract)
src/renderer/features/settings/settings-sidebar.tsx:36-96	Hardcoded tab labels (Preferences, Account, Appearance, etc.)

Components with Hardcoded Strings

A quick survey shows strings are scattered across many files:

• Settings tabs - src/renderer/components/dialogs/settings-tabs/*.tsx (all ~12 tab files)
• Sidebar - src/renderer/features/sidebar/
• Agent chat UI - src/renderer/features/agents/
• Dialogs - src/renderer/components/dialogs/

Existing Locale Detection (System-level only)

There's already platform-specific locale detection for the terminal environment in:

• src/main/lib/terminal/env.ts:17-83 - getLocale(), detectLocaleAsync()
• src/main/lib/platform/types.ts:87-90 - detectLocale() interface

This could be leveraged to auto-detect the user's preferred language on first launch.

Suggested Implementation Approach

1. Add dependencies - react-i18next and i18next (recommended for React apps)
2. Create translation structure:

   src/renderer/locales/
   ├── en.json     # English (default)
   ├── es-ES.json  # Spanish (Spain)
   └── es-MX.json  # Spanish (Mexico)
   

3. Add language preference atom in src/renderer/lib/atoms/index.ts
4. Add language selector in the Preferences tab
5. Wrap app with i18n provider in src/renderer/App.tsx
6. Extract strings incrementally - Start with high-visibility areas (settings, sidebar)

Related Infrastructure

• State management: Uses Jotai atoms with atomWithStorage for persisted preferences
• date-fns v3.6.0 is already installed and has locale support that could be used for date formatting

No Duplicate Issues Found

This is the first i18n-related feature request.

---

Happy to discuss the approach further! The offer to contribute translations is much appreciated - that's often the hardest part 🙂