Eita! Why Internationalization and Localization matter
summary
Defines i18n vs l10n and shows concrete tooling and tradeoffs: uses gettext/PO/MO workflow and Python’s locale module to format dates numbers and currency, demonstrates Django’s built‑in i18n where Django uses Accept‑Language header for locale selection, and explains time handling where the app stores times in UTC with aware datetimes. Notes surprising facts (≈360M native English speakers; few countries use MDY), describes changing the deploy pipeline to push PO files to translation platforms and gating production on completed translations.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:25Design and development
- 3:28Agenda
- 10:14Why does it matter?
- 17:10Python locale module
- 19:14Translations
- 24:29Format Localization
- 28:24Time Zone
- 34:44Deploy Process
related talks
29mSpanish Spoken Here
22mInternationalisation(i18n) & Localisation(l10n)
25mInternationalisation is a Piece of Cake
29mEast Meets West When Translating Django Apps
20mFinding translations, localisation and internationalisation
19mData internationalization in Django
46mInternationalization — What Are You?
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���