Finding Translations: Localization and Internationalization
summary
Concrete Rails low level advice on making apps translatable and avoidable pitfalls so you can decide fast. Covers using i18n.t and localize for strings and dates pluralization with count, gems that save time like rails-i18n, i18n-tasks, Globalize, Geocoder and Localeapp, plus options for .yml versus Redis or database backends with caching. Explains why concatenating keys breaks syntax and gendered languages why RTL and expanded string length demand layout changes and workflow rules to avoid merge hell.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:43Defining our terms
- 1:40What is translation?
- 5:28When should you think about localization?
- 6:21When should you internationalize?
- 7:11Rails localization conventions
- 9:44There's a gem for that
- 13:42Things to consider
- 24:26But how does your app translate?
- 27:31Key takeaways
related talks
34mLocalize your Rails application like a pro
20mFinding translations, localisation and internationalisation
29mInternationalization on Rails: Unpacking the Rails I18n Toolkit
40mTricks That Rails Didn't Tell You About
32mRails Sustainable Productivity
31mRails Flavored Ruby
41mOff the Tracks - Challenging the Rails Mindset
42mTen Things You Didn't Know Rails Could Do