language

[Ca6mmm]

希望可以支持中文

[1code-async]

Task completed.

Done. I've posted an enrichment comment on issue #169. Here's a summary of the analysis:

Issue #169 requests Chinese language support (希望可以支持中文 = "Hope to support Chinese").

Key findings:

• Duplicate/related: Issue Feature Request: Add Spanish language support (i18n) #160 requested Spanish/i18n support and was closed by a maintainer as "Not a priority at this moment"
• No i18n exists: All 500+ user-facing strings are hardcoded in English across 50+ files
• Foundations exist: System locale detection is already implemented cross-platform, and date-fns (with Chinese locale support) is already installed
• Scope: Non-trivial — would require adding react-i18next, extracting strings from settings tabs (13 files), sidebar, chat interface, dialogs, slash commands, and toast notifications

The comment includes a detailed breakdown of affected files, string counts by area, and a suggested implementation approach.

---

View full conversation

Powered by 1Code

[1code-async]

Task completed.

I've posted an enrichment comment on issue #169. Here's a summary of what was found and commented:

Issue #169 requests Chinese language support. The analysis found:

1. Related issue: Feature Request: Add Spanish language support (i18n) #160 (Spanish i18n support) was closed by a maintainer as "not a priority at this moment" — making language #169 effectively a duplicate request for a different language.

2. No i18n infrastructure exists — all UI strings are hardcoded in English across 20+ files with no translation framework, language files, or language selector.

3. Significant scope — would require adding react-i18next, extracting hundreds of strings, creating translation files, and building a language selector UI.

4. Existing leverage points — platform locale detection already exists (could auto-detect Chinese), Jotai atom storage pattern could persist preference, and date-fns already supports Chinese locales.

The comment links to specific files and provides context about the prior related issue's closure.

---

View full conversation

Powered by 1Code

[1code-async]

Issue Analysis: Chinese Language Support (i18n)

Thanks for the feature request! This is asking for Chinese (中文) language support in the 1Code application.

Current State

The application currently has no internationalization (i18n) infrastructure. All UI strings are hardcoded in English throughout the renderer components. Specifically:

• No i18n library installed (no react-intl, i18next, etc. in package.json)
• No translation files or locale directories exist
• No language switching UI in settings
• 100+ hardcoded English strings across renderer components

The only locale-related code that exists is:

• Terminal locale detection in src/main/lib/terminal/env.ts:59 — used for passing LANG to shell sessions, not UI translation
• Voice transcription language parameter in src/main/lib/trpc/routers/voice.ts:192 — used for Whisper API, not UI

No Duplicates Found

This is the first issue requesting language/i18n support. No prior issues exist on this topic.

Implementation Scope

Adding Chinese (or any non-English) language support would require:

1. Integrate an i18n library (e.g., i18next + react-i18next) into the React renderer
2. Extract all hardcoded strings into translation key files — major files include:
   • src/renderer/features/agents/main/active-chat.tsx (~40+ strings)
   • src/renderer/features/agents/commands/builtin-commands.ts (command descriptions)
   • src/renderer/components/dialogs/settings-tabs/*.tsx (settings labels)
   • src/renderer/components/chat-markdown-renderer.tsx (copy/UI actions)
   • src/renderer/components/dialogs/claude-login-modal.tsx (auth flow text)
3. Create translation files (en.json, zh-CN.json, etc.)
4. Add a language selector in the settings UI (likely in src/renderer/components/dialogs/settings-tabs/agents-preferences-tab.tsx)
5. Persist language preference (via Electron store or the existing SQLite database)

Suggested Approach

A phased rollout would be practical:

• Phase 1: Add i18next + react-i18next, wrap the app with an I18nextProvider, and extract strings from the most visible components first (sidebar, chat interface, settings)
• Phase 2: Extract remaining strings (tool renderers, dialogs, error messages)
• Phase 3: Add language auto-detection from app.getLocale() and a settings toggle

This is a significant cross-cutting change that touches most renderer components.

---

🤖 Generated with Claude Code

[1code-async]

Codebase Analysis: Chinese Language Support (i18n)

This is a request to add Chinese (中文) language support to the 1Code UI.

Related Issues

• Feature Request: Add Spanish language support (i18n) #160 - "Feature Request: Add Spanish language support (i18n)" — Closed by a maintainer with the comment: "Not a priority at this moment". This issue is essentially a duplicate/continuation of that request, now for Chinese instead of Spanish.

Current State

No i18n infrastructure exists. All UI strings are hardcoded in English directly in React components. There are no translation libraries, language files, or language selection settings.

What Would Be Involved

Dependencies to add: react-i18next + i18next

Key files with hardcoded English strings:

Area	Files
Settings tabs	src/renderer/components/dialogs/settings-tabs/*.tsx (~12 files)
Slash commands	src/renderer/features/agents/commands/builtin-commands.ts
Chat UI	src/renderer/features/agents/main/active-chat.tsx, new-chat-form.tsx, chat-input-area.tsx
Sidebar	src/renderer/features/sidebar/
Dialogs	src/renderer/components/dialogs/ (login, archive, confirm dialogs)
Tool labels	src/renderer/features/agents/main/assistant-message-item.tsx:52-62
OAuth page	src/main/lib/oauth.ts:157-158 (HTML with lang="en")

Existing infrastructure that could be leveraged:

• Platform-specific locale detection already exists in src/main/lib/platform/{darwin,linux,windows}.ts — could auto-detect Chinese locale on first launch
• Jotai atomWithStorage pattern (used throughout src/renderer/lib/atoms/index.ts) could store a language preference
• date-fns v3.6.0 is already installed and supports Chinese locale for date formatting

Context

Given that #160 was closed as not a priority, this feature request for Chinese support may receive the same treatment. The scope of work is significant — it requires extracting hundreds of hardcoded strings across 20+ files, setting up an i18n framework, creating translation files, and adding a language selector UI. This is typically done incrementally, starting with high-visibility areas like settings and the main chat interface.

[1code-async]

Codebase Analysis: Chinese Language / i18n Support

Thanks for the request! Here's an analysis of what this would involve.

Related Issue

• Feature Request: Add Spanish language support (i18n) #160 (closed) — "Feature Request: Add Spanish language support (i18n)" was a similar request for i18n. A maintainer closed it noting it is not a priority at this moment. This issue is effectively a duplicate of the same underlying feature request (internationalization), but for Chinese instead of Spanish.

Current State

No i18n infrastructure exists. All UI strings are hardcoded in English directly in React components. There are no translation libraries, no language files, and no language selector.

However, the app does have some useful foundations:

• System locale detection is already implemented cross-platform in src/main/lib/platform/darwin.ts, linux.ts, windows.ts and cached in src/main/lib/terminal/env.ts
• Date/number formatting partially uses .toLocaleString() and .toLocaleDateString() which would respect a Chinese locale
• date-fns is already installed and has Chinese locale support

Scope of Work

User-facing strings are distributed across many files:

Area	Files	Approximate String Count
Settings tabs	src/renderer/components/dialogs/settings-tabs/*.tsx (~13 files)	200+
Sidebar	src/renderer/features/sidebar/agents-sidebar.tsx	50+
Chat interface	src/renderer/features/agents/main/*.tsx, components/*.tsx	80+
Dialogs & modals	src/renderer/components/dialogs/*.tsx	40+
Slash commands	src/renderer/features/agents/commands/builtin-commands.ts	20+
Toast notifications	Scattered across 30+ files	30+
Tooltips & ARIA labels	Scattered across 40+ files	80+

Total: ~500+ strings would need extraction and translation.

Suggested Implementation Approach

1. Add react-i18next + i18next as the translation framework
2. Create translation file structure:

   src/renderer/locales/
   ├── en.json      # English (default)
   └── zh-CN.json   # Simplified Chinese
   

3. Add a language preference atom in src/renderer/lib/atoms/index.ts (using existing atomWithStorage pattern)
4. Add a language selector in the Preferences settings tab (src/renderer/components/dialogs/settings-tabs/agents-preferences-tab.tsx)
5. Wrap the app with an i18n provider in src/renderer/App.tsx
6. Extract strings incrementally — start with high-visibility areas (sidebar, chat input, settings)
7. Leverage existing locale detection from src/main/lib/terminal/env.ts for auto-detection on first launch

Key Files That Would Need Changes

• package.json — Add i18n dependencies
• src/renderer/App.tsx — Add i18n provider
• src/renderer/lib/atoms/index.ts — Language preference atom
• src/renderer/components/dialogs/settings-tabs/agents-preferences-tab.tsx — Language selector UI
• src/renderer/features/sidebar/agents-sidebar.tsx — Largest single source of UI strings
• src/renderer/features/agents/main/chat-input-area.tsx — Chat placeholders
• src/renderer/features/agents/commands/builtin-commands.ts — Command descriptions
• All settings tab files in src/renderer/components/dialogs/settings-tabs/

Note

Given that the related issue #160 was closed as not a priority, it's likely this request will receive the same treatment for now. The implementation is non-trivial (500+ strings across 50+ files) and would require ongoing maintenance for each new feature added to the app.