i18n

Internationalization setup for React apps using react-i18next with flat dot-notation keys. Flat keys with dot notation (not nested objects): Patterns: {feature}.{context}.{action|status} Parameters: Use {{variableName}} syntax Avoid key conflicts: Most used: common (shared UI), chat (chat features), setting (settings) Others: auth, changelog, components, discover, editor, electron, error, file, hotkey, knowledgeBase, memory, models, plugin, portal, providers, tool, topic - Use flat key structure with dot notation (e.g., feature.context.action ) in src/locales/default/ files; never edit JSON files in locales/ - Support dynamic parameters via {{variableName}} syntax and access translations in components with useTranslation() hook - Run pnpm i18n to auto-generate translations for all languages; manually translate zh-CN and en-US files for dev preview - Common namespaces include common , chat , and setting ; avoid key conflicts by ensuring parent keys don't duplicate child key prefixes - Default language: English (en-US) - Framework: react-i18next - Only edit files in src/locales/default/ - Never edit JSON files in locales/ - Run pnpm i18n to generate translations (or manually translate zh-CN/en-US for dev preview) - Add keys to src/locales/default/{namespace}.ts - Export new namespace in src/locales/default/index.ts - For dev preview: manually translate...