4 min lecture • Guide 393 of 877
How to Manage Localization and Internationalization (i18n) Work?
How to manage localization and internationalization (i18n) work?
Manage i18n work by creating language-specific labels (lang:es, lang:fr), tracking string extraction as development tasks, coordinating with translators through dedicated columns, and documenting i18n guidelines in NoteVault. Treat translation as a workflow stage before release, not an afterthought.
i18n board columns
| Column | Purpose |
|---|---|
| Development | Feature with i18n-ready code |
| String Extraction | Export new strings |
| Translation | Per-language translation |
| Review | Native speaker review |
| Integration | Import translations |
| Testing | Verify all locales |
| Released | Shipped with translations |
i18n labels
| Label | Purpose |
|---|---|
| i18n | Internationalization task |
| lang:en | English (source) |
| lang:es | Spanish translation |
| lang:pt | Portuguese translation |
| lang:fr | French translation |
| lang:de | German translation |
| i18n:extract | String extraction needed |
| i18n:new-strings | Has new translatable strings |
| i18n:review | Translation review needed |
i18n workflow for features:
- Development - Write i18n-ready code (no hardcoded strings)
- String extraction - Export new strings to translation files
- Create translation tasks - One per supported language
- Translator work - Translate in parallel
- Native review - Review per language
- Import translations - Merge translation files
- Locale testing - Test each language
- Release - Ship with all translations
Feature task with i18n
## Feature: User Notifications Preferences
Development:
- [ ] Build UI with i18n keys
- [ ] No hardcoded user-facing strings
- [ ] Add i18n:new-strings label
String extraction:
- [ ] Extract 15 new strings
- [ ] Add context comments for translators
- [ ] Create translation tasks
Translations needed:
- [ ] lang:es - Spanish
- [ ] lang:pt - Portuguese
- [ ] lang:fr - French
- [ ] lang:de - German
Definition of Done:
- [ ] All translations complete
- [ ] All locales tested
Translation task template
## Translation: [Feature] - [Language]
Source language: English
Target language: [Language]
String count: [Number]
Context: [Feature description for translator]
Strings file: [Link to file or TMS]
Due date: [Before feature release]
Instructions:
- Maintain consistent terminology with glossary
- Match source tone (formal/casual)
- Test translations in context if possible
Review: @native-speaker-reviewer
NoteVault i18n documentation
# Internationalization Guide
## Supported Locales
| Language | Code | Status |
|----------|------|--------|
| English | en | Source |
| Spanish | es | Full support |
| Portuguese | pt | Full support |
| French | fr | Full support |
| German | de | Partial |
## Glossary
| Term | en | es | pt | fr |
|------|----|----|----|----|
| Dashboard | Dashboard | Panel | Painel | Tableau de bord |
| Settings | Settings | Configuración | Configurações | Paramètres |
## Guidelines for Developers
- Use i18n keys, never hardcode strings
- Provide context comments
- Handle pluralization properly
- Support RTL for future locales
- Test with pseudo-localization
## Translation Process
1. Strings extracted weekly
2. Translators have 3 days
3. Native review 1 day
4. Integration before release
i18n metrics to track
| Metric | What to Measure |
|---|---|
| String coverage | % strings translated per locale |
| Translation turnaround | Days from extract to complete |
| Missing translations | Strings showing in source language |
| Translation quality | Review rejection rate |