Sonamu UI provides functionality to export and import i18n dictionaries as Excel files. Translators or planners can work in spreadsheets and apply changes all at once.
Excel Export
Exporting from Sonamu UI
- Access Sonamu UI (
http://localhost:1028/sonamu-ui)
- Click i18n in the left menu
- Click the Export button in the top right
- Download the Excel file
Excel File Structure
| Column | Description |
|---|
key | Dictionary key |
source | entity (auto-extracted) or project (manually written) |
ko, en, β¦ | Translation values for each locale |
Excel Import
Importing After Translation Work
- Perform translation work in the exported Excel file
- Click the Import button on the i18n page in Sonamu UI
- Select the Excel file
- Review and apply the changes
Import Behavior
| source | defaultLocale (ko) | Other locales (en) |
|---|
entity | Updates entity.json | Saved to en.ts |
project | Saved to ko.ts | Saved to en.ts |
The defaultLocale values for entity source directly modify the Entityβs title, prop.desc, and enumLabels.
Translation Workflow
Recommended Workflow
- Development phase: Only write defaultLocale (ko) labels when defining Entities
- Translation phase: Excel export -> Deliver to translation team -> Import after translation is complete
- Maintenance: Repeat the same process when adding new keys
Handling Function Values
Function values are preserved as-is in Excel:
| key | ko |
|---|
common.results | (count: number) => \$κ° κ²°κ³Όβ |
validation.required | (field: string) => \$μ(λ) νμβ |
(...) => ...) are automatically detected and saved as functions.
Important Notes
- Key changes: Changing an existing key adds it as a new key; the original key is retained
- Key deletion: Deleting a row in Excel does not remove it from the existing dictionary
- Source change not allowed: Changes from
entity to project are ignored
- Empty values: Empty cells are ignored (the key is not removed from that locale)