Building Elixir Apps for Global Audiences or an Audience of One
summary
Demonstrates using the CLDR data via ex_cldr/ex_money to derive real preferences from a BCP‑47 tag and to format numbers, dates, currencies and units; shows accept_language.best_match, unit conversions (feet ↔ meters, mph ↔ L/min), and parsed money in 504 locales. Reveals surprising facts used: 83 number systems, 105 disputed territories, France owning the most time zone IDs, and territory‑specific cash rounding rules (Switzerland/Australia). Builds an e‑commerce demo with Ecto translation columns and localized inspect output — practical code that runs and matches CLDR.
AI-written summary · about
chapters (8)
- 0:0004:13 - Intro
- 4:1406:57 - What is Localisation and why Localise?
- 6:5712:50 - Identifying the Users Locale and Preferences
- 12:5114:02 - What does a Language Tag Tell Us?
- 14:0323:06 - A note about Countries, Territories and Regions
- 23:0725:46 - Introducing CLDR
- 25:4739:15 - Localising Basic Data Types
- 39:1643:08 - In Summary
related talks
44mUnicode Beyond Just Characters: Localization with the CLDR
31mThink Globally, Act Locally on the Web
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
25mInternationalisation is a Piece of Cake
31mJavaScript Apps Go Intl
25mLocalization: Implementation and Testing... Locally
29mMake apps for a global audience - Naomi Meyer
43mJavaScript apps go Int(ernationa)l