Think Globally, Act Locally on the Web
summary
About 51% of websites use English while roughly 25% of internet users are English speakers, so internationalization is an accessibility requirement. Practical stack items are utf-8, BCP‑47 locale tags, the CLDR data, ICU message format, the JavaScript Intl API and libraries like formatjs, plus continuous localization for deployment. A live example rewrites a train-ticket grid: removing a fixed CSS height and redesigning columns returns a currency symbol and fixes overflow but costs weeks/months of work. Always let the user pick their locale.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:44Why internationalization matters
- 8:04Building blocks of i18n
- 13:48Unicode and locale standards
- 19:52JavaScript Internationalization API
- 21:59Using format.js library
- 24:48Logistics and continuous localization
- 26:35Design pitfalls in i18n
- 28:48Key takeaways and tips
related talks
39mThink globally, act locally with i18n on the web
34mWhat is the deal with internationalisation?
28mi18n, l10n & Principles for a More Accessible Web
25mInternationalisation is a Piece of Cake
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
25mLocalization: Implementation and Testing... Locally
22mInternationalisation(i18n) & Localisation(l10n)
19mLost in Translation? Intl, the Rosetta Stone of Web Development