1k-i18n
Internationalization and translation guidelines for OneKey. Use when adding text strings, using translations, or working with locales. Triggers on i18n, translation, locale, intl, formatMessage, ETranslations, language, text.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
OneKey Internationalization (i18n) Guidelines
Translation Management - CRITICAL RESTRICTIONS
ABSOLUTELY FORBIDDEN (These files are AUTO-GENERATED):
- ❌ NEVER modify
@onekeyhq/shared/src/locale/enum/translations.ts- Will be overwritten and break i18n system - ❌ NEVER modify locale JSON files in
@onekeyhq/shared/src/locale/json/*- Managed by external translation system - ❌ NEVER hardcode text strings in components - ALWAYS use translation keys
- ❌ NEVER add translation keys directly to enum files - Use proper workflow
CONSEQUENCES OF VIOLATION:
- Translation system corruption
- Loss of translation work
- Build failures in i18n pipeline
- Breaking localization for international users
Using Translations
- Use
useFormatMessageorformatMessagefunctions for displaying translated text - Define new translation keys in the appropriate modules
- Always use translation keys instead of hardcoding text strings
- Follow the established pattern for translation keys:
namespace__action_or_description
Updating Translation Keys
- Direct translation from design specs: Update i18n directly based on design spec annotations without searching existing translation keys
- Run
yarn fetch:localeto pull the latest translation keys from the remote system - This command automatically updates
@onekeyhq/shared/src/locale/enum/translations.tswith new translation enums - For design spec translation keys like
prime::restore_purchases, convert to code format:- Replace
::with_(underscore) - Use the enum:
ETranslations.prime_restore_purchases - In component code:
{intl.formatMessage({ id: ETranslations.prime_restore_purchases, })}
- Replace
Locale Handling
- The system uses automatic locale detection with fallbacks
- Default locale fallback chain is implemented in
getDefaultLocale.ts - Respect platform-specific locale handling (web, native, desktop, extension)
Code Examples
Using Translations in Components
import { useIntl } from 'react-intl';
import { ETranslations } from '@onekeyhq/shared/src/locale';
function MyComponent() {
const intl = useIntl();
return (
<SizableText>
{intl.formatMessage({
id: ETranslations.global__confirm,
})}
</SizableText>
);
}
Using formatMessage Outside Components
import { appLocale } from '@onekeyhq/shared/src/locale/appLocale';
import { ETranslations } from '@onekeyhq/shared/src/locale';
const message = appLocale.intl.formatMessage({
id: ETranslations.global__cancel,
});
Translation Key Naming Pattern
namespace__action_description
Examples:
- global__confirm
- global__cancel
- swap__select_token
- wallet__create_wallet
- settings__dark_mode
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-26
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!