Translation Workflow and Formatting Complex Translations
summary
A CLI called L10ns() ships a real workflow: it parses code, uses CLDR plural rules (Arabic → six forms), compiles ICU-style messages with ICU MessageFormat for plural/select/number/date, and provides autosync that adds, removes, or migrates keys across JSON storage. Live demos show pluralization and gender selects working and autosync adding/removing keys across locales; the tool is published to npm as v1.0.0 and installs for immediate use.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:31Structure of this talk
- 1:20Part1: Complex translation workflow
- 1:37Pluralization: bad example 1
- 2:13Cons: Locale specific code block
- 3:33CLDR - example of XML data
- 5:31CLDR - plural forms examples
- 6:15General message formatting
- 7:12ICU's messageformat - plural format
- 7:55Try to define a simpler syntax...
- 11:31Select format use case
- 11:53ICU's messageformat - select format
- 12:42ICU's number format
- 14:21ICU's date format
- 14:59Part2: Translation workflow
- 15:14Syncing translation keys
- 15:45Manual sync
- 16:39Auto sync work flow
- 21:26Translator and programmer workflow
- 22:03Anti pattern
- 22:15Content structure - facebook
- 23:24Links
related talks
24mClient Side Internationalization
37mThe UX of Language
39mThink globally, act locally with i18n on the web
20mFinding translations, localisation and internationalisation
25mLocalization: Implementation and Testing... Locally
44mL10n, i18n and t9n in the JVM World
26mThe State of the Art in Localization
15mEz Translation with Deepl