Maofeng
36 lines
1.2 KiB
Plaintext
36 lines
1.2 KiB
Plaintext
---
|
|
title: Overview
|
|
description: Follow the complete path from application configuration to translated production catalogs.
|
|
order: 1
|
|
toc:
|
|
- id: ownership-model
|
|
title: Ownership model
|
|
- id: workflow
|
|
title: Workflow
|
|
- id: package-entries
|
|
title: Package entries
|
|
---
|
|
|
|
## Ownership model {#ownership-model}
|
|
|
|
Every application owns its `i18n.config.json` and application catalogs. Reusable packages may ship built-in catalogs, but the application chooses which ones to merge and may override their messages.
|
|
|
|
This keeps product copy under application control without duplicating translations from shared packages.
|
|
|
|
## Workflow {#workflow}
|
|
|
|
1. Configure locales and catalog sources.
|
|
2. Install the Vite plugin.
|
|
3. Load one catalog into `I18nProvider`.
|
|
4. Extract and translate application messages.
|
|
5. Use the Devtool or Message Studio during development.
|
|
6. Compile compact, cacheable production assets.
|
|
|
|
## Package entries {#package-entries}
|
|
|
|
- `@workspace/i18n` provides the React runtime.
|
|
- `@workspace/i18n/catalogs` loads generated catalogs.
|
|
- `@workspace/i18n/devtool` provides development surfaces.
|
|
- `@workspace/i18n/vite` configures Vite.
|
|
- `workspace-i18n` exposes the CLI.
|