Think globally, act locally with i18n on the web
summary
About 51% of websites are in English while only about 25% of web users speak English, so i18n becomes accessibility work: use Unicode, the CLDR and ICU MessageFormat for real plural and direction rules, and the ECMAScript Intl API for dates and currencies. Continuous localization via platforms like SmartLink hooks GitHub, returns translations in minutes or hours, and avoids blocking releases. A train ticket UI needed a redesign (weeks of work) to handle German word lengths; fixing a fixed-height CSS rule proves small changes can make i18n actually work.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 1:57Internationalization
- 2:45i18n
- 3:49Statistics
- 5:09Accessibility
- 5:39Internationalize
- 7:15JSON
- 8:00Language
- 11:07Unicode
- 11:59Bidirectional
- 13:52Internet Engineering Task Force
- 14:20Language Tags
- 15:26Location
- 16:31CLDR
- 17:20Spanish
- 18:28ICU International Components
- 18:58Welcome Name
- 20:52How do you write strings
- 21:32Example
- 23:14JavaScript ACMA
- 26:07Work in progress
- 26:30Libraries disclaimer
- 27:29React Integration
- 28:47Format JavaScript
- 29:19Logistics
- 29:31Translation
- 29:44Deploy
- 29:57Languages
- 31:57Trainline
- 32:25Ticket search
- 32:53Try German
- 33:10Fixed height
- 33:46Pricing
- 34:11Redesign
- 34:44Style
- 35:28Line breaks
- 35:55No spaces
- 36:42Conclusion
related talks
31mThink Globally, Act Locally on the Web
34mWhat is the deal with internationalisation?
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
28mi18n, l10n & Principles for a More Accessible Web
22mInternationalisation(i18n) & Localisation(l10n)
17mi18n: A Brief Primer of Web Internationalization
25mInternationalisation is a Piece of Cake
25mLocalization: Implementation and Testing... Locally