End-to-End i18n
summary
A small shopping‑list app gets fully internationalized end‑to‑end: strings are defined as IDs with defaults, extracted into gettext PO files by an extract_strings script, handed to translators (or quick Google/Upwork), rebuilt with build_strings into JSON and pulled into react intel. Currency, number and date formatting use custom format_currency/format_date (dayjs) because platform i18n differs; pluralization and variable interpolation work; the pipeline runs against apps shared across web and Expo mobile and proves reliable in over 30 countries.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:48Internationalize a React App
- 3:09Localization Settings
- 3:57Constants
- 4:22Date Formats
- 5:49Locale Context
- 7:57Formatting Um Internationalized Strings
- 12:20Date and Number Formatting
- 13:04Format Currency
- 15:40To Manage the Translation Process
- 19:08Pluralization
- 23:03Step Three
related talks
22mInternationalizing React
39mThink globally, act locally with i18n on the web
33mFearless Localization and Internationalization Across the Nations
31mBuilding Angular apps with internationalization (i18n) in mind
25mLocalization: Implementation and Testing... Locally
32mInternationalize your Web App with GlobalizeJS
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
29mMake apps for a global audience - Naomi Meyer