Developers’ Roles in Localizing and Internationalizing Software Products
summary
Recommends using utf-8 for DB and HTTP headers, storing dates as store timestamps in UTC and converting on render, and keeping translations in separate files like en_GB.json served by a lightweight translation API (endpoints: list locales, return keys+values). Mentions libraries (moment.js, Carbon) for timezone formatting, font fallbacks for non‑Latin scripts, and that a translation-management service avoids rebuilds when copy changes.
AI-written summary · about
chapters (9)
- 0:00Introduction to talk
- 7:06Defining i18n and l10n
- 14:51Best practices overview
- 17:20Encoding and data storage
- 21:47Date and time zone handling
- 26:26Language translation strategies
- 31:01Continuous deployment for translations
- 33:09Q&A session begins
- 45:37Closing remarks
related talks
30mInfluence your customer outreach with best practices for internationalization
26mBoost your developer site with localisation
01h 11mSpeak My Language %app%
31mSimple Internationalization for Your Project with ttag
19mSimeon Griggs-Localization for real-world use-cases: Key learnings from onboarding global brands
23mAutomating Localization
34mMass Frontend Refactors: Less Stress; More Success
48mContinuous Localization in Enterprise Web Projects