I18n

LobeHub Internationalization Guide

• Default language: English (en-US)
• Framework: react-i18next
• Only edit files in packages/locales/src/default/ - Never edit JSON files in locales/ (except hand-written en-US/zh-CN previews)
• Leave generated locales to the daily auto-i18n.yml workflow by default; run bun run i18n manually only when they are needed immediately

Key Naming Convention

Flat keys with dot notation (not nested objects):

// ✅ Correctexport default {  'alert.cloud.action': '立即体验',  'sync.actions.sync': '立即同步',  'sync.status.ready': '已连接',};
// ❌ Avoid nested objectsexport default {  alert: { cloud: { action: '...' } },};

Patterns: {feature}.{context}.{action|status}

Parameters: Use {{variableName}} syntax

'alert.cloud.desc': '我们提供 {{credit}} 额度积分',

Avoid key conflicts:

// ❌ Conflict'clientDB.solve': '自助解决','clientDB.solve.backup.title': '数据备份',
// ✅ Solution'clientDB.solve.action': '自助解决','clientDB.solve.backup.title': '数据备份',

Workflow

1. Add keys to packages/locales/src/default/{namespace}.ts
2. Export new namespace in packages/locales/src/default/index.ts
3. For dev preview: manually translate locales/zh-CN/{namespace}.json and locales/en-US/{namespace}.json
4. Leave all other locales to .github/workflows/auto-i18n.yml, which runs daily and opens an automated translation PR
5. Run bun run i18n manually only when the branch needs those translations immediately; it is slow and requires OPENAI_API_KEY

Usage

import { useTranslation } from 'react-i18next';
const { t } = useTranslation('common');
t('newFeature.title');t('alert.cloud.desc', { credit: '1000' });
// Multiple namespacesconst { t } = useTranslation(['common', 'chat']);t('common:save');

Common Namespaces

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