saitarrun Skill: Localization (i18n/l10n)
String externalization + translation workflow + cultural adaptation = global product.
String Externalization
Don't embed strings in code:
# ✗ Bad
message = "Hello, " + user.name
# ✓ Good (externalizable)
message = t("greeting", name=user.name)
Translation File Format
# locales/en.yaml
greeting: "Hello, {name}"
hello_world: "Hello, World!"
# locales/es.yaml
greeting: "Hola, {name}"
hello_world: "¡Hola, Mundo!"
# locales/fr.yaml
greeting: "Bonjour, {name}"
hello_world: "Bonjour, le monde!"
Pluralization
messages:
en:
item_count:
one: "You have 1 item"
other: "You have {count} items"
es:
item_count:
one: "Tienes 1 artículo"
other: "Tienes {count} artículos"
Right-to-Left (RTL) Support
<!-- Auto-detect -->
<html dir="auto">
...
</html>
<!-- or explicit -->
<html lang="ar" dir="rtl">
<!-- Arabic content -->
</html>
<!-- CSS -->
body {
direction: rtl;
text-align: right;
}
Dates & Times
en-US: 01/15/2024
en-GB: 15/01/2024
de-DE: 15.01.2024
Use locale-aware formatting:
from babel.dates import format_date
format_date(date, format='medium', locale='de_DE')
Translation Workflow
- Extract: Find translatable strings
- Upload: To translation platform (Crowdin, Transifex)
- Translate: Humans + review
- Download: Translated files
- Test: Each locale
- Deploy: With fallback to English
Status: Ready for localization work
Best for: i18n implementation, translation management, global expansion