L10n, i18n and t9n in the JVM World
summary
Shows how a JVM backend originally Polish is internationalized by moving text into UTF‑8 ResourceBundle properties, using Java Locale and MessageFormat plus ICU4J/CLDR for proper plural, number and currency formatting, and flipping layout/icons for RTL locales. Describes an automated translation workflow using XLIFF‑style exchanges with screenshots and glossary, falling back to pl_PL for missing keys, and handling prices by storing per‑currency values tied to NBP exchange rates for accounting rather than doing live conversions.
AI-written summary · about
chapters (16)
- 0:00L10n and i18n intro
- 3:58L10n, i18n basics
- 9:41Locales in JVM
- 12:36Resource bundles
- 16:08Text formatting
- 18:34Currency/date/number formatting
- 19:15Date validation errors
- 20:19Fallbacks and defaults
- 21:43Language UI differences
- 23:08User language detection
- 24:12Market expansion
- 24:55Translation automation
- 26:41Glossary consistency
- 27:45Global expansion approach
- 31:17Summary
- 31:43Q&A
related talks
22mInternationalisation(i18n) & Localisation(l10n)
39mThink globally, act locally with i18n on the web
25mInternationalisation is a Piece of Cake
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
31mThink Globally, Act Locally on the Web
20mFinding translations, localisation and internationalisation
29mInternationalization on Rails: Unpacking the Rails I18n Toolkit
20mInternationalization (and not only)