Finding translations, localisation and internationalisation
summary
Concrete workflow and tools are described: extract view copy to YAML, use rails i8n for keys and plural rules, run i18n-tasks to find missing keys, and use Localapp or Globalize for translators and model translations; Geocoder auto-selects locales by IP. Claims include 30% text expansion for French and much larger for Spanish, warnings about merge conflicts when everyone edits YAML, and advice to provide context for translators and variable-based interpolation instead of string fragments. Watch if those exact fixes matter.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:24Definitions
- 1:14Translation
- 2:19Localisation
- 2:55When to start
- 3:51Yellow file
- 5:05I18N guide
- 5:44Other gems
- 8:11Yellow files
- 9:22Merge conflicts
- 10:03What needs to be translated
- 10:56Misconceptions about translation
- 11:11Fragments of sentences
- 12:17Pluralisation
- 13:08Language specificity
- 14:09Screen space
- 16:08Character sets
- 16:39Cultural and legal implications
- 17:59Summary
- 18:46Questions
related talks
29mFinding Translations: Localization and Internationalization
34mLocalize your Rails application like a pro
29mInternationalization on Rails: Unpacking the Rails I18n Toolkit
22mInternationalisation(i18n) & Localisation(l10n)
38mSacré bleu! The trials and tribulaciones of internationalising your ẨṔṔŁîÇåŤḯṏÑ���
39mThink globally, act locally with i18n on the web
31mInternationalizing your App
08mLocalization for Real-World Use-Cases: Key Learnings from Onboarding Global Brands