Internationalisation(i18n) & Localisation(l10n)
summary
Explains concrete steps: extract strings to config as key/value files, translate per-locale and load based on user preference, and avoid concatenating fragments. Describes number/currency differences and shows using JS Intl/toLocaleString for formatting. Covers RTL needs for Arabic/Hebrew — toggle dir=rtl, use use dir=rtl and CSS mirroring or separate RTL stylesheet plus common CSS. Suggests partial-translation tactics (namespaced or split resources), flags contextual translation issues, and notes ongoing translation and QA costs.
AI-written summary · about
chapters (12)
- 0:00Introduction to internationalisation and localisation
- 3:25What is i18n
- 5:09Localisation process and goals
- 8:42Extracting text for localisation
- 10:48Localising numbers and currency
- 11:31i18n and l10n challenges
- 12:13Contextual translation costs
- 14:22Partial translation management
- 16:07RTL language support
- 18:57RTL CSS and browser support
- 20:45Multilingual app best practices
- 21:49Summary
related talks
25mInternationalisation is a Piece of Cake
39mThink globally, act locally with i18n on the web
20mFinding translations, localisation and internationalisation
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
31mThink Globally, Act Locally on the Web
34mWhat is the deal with internationalisation?
24mInternationalization-ing
25mLocalization: Implementation and Testing... Locally