Skip to content
This repository was archived by the owner on Jul 22, 2018. It is now read-only.

i18n on Rails: A Twitter Approach

Ben Oakes edited this page Apr 23, 2012 · 6 revisions

Presenter: Cameron Dutro (@camertron)

Bio

Cameron Dutro has worked for Twitter's International Team for about a year and a half, helping build and maintain the Translation Center, Twitter's crowdsourced translation platform. Although he only started using Ruby and Rails a few years ago, he's a big fan of their extendibility and elegance. Cameron is also the author of the twitter_cldr gem, an attempt to bring JDK-level internationalization capabilities to the Ruby community.

Abstract

Twitter's internationalization (i18n) and localization (l10n) model doesn't follow traditional methods. Instead of contracting out to professional translators, Twitter maintains an active community of over 500,000 volunteers who have helped successfully launch Twitter in 28 languages, including right-to-left languages like Hebrew and Arabic. Learn about some of the technical challenges we face, how to translate a Rails application at scale, and what to do when the i18n gem and po files aren't quite enough. We'll take a look at the tricky stuff too, like dates, times, lists, plurals, alphabetization, and capitalization using the twitter_cldr gem, and go over internationalization best practices. Finally, we'll explain how to maintain internationalization of your Javascript alongside your Rails code for an end-to-end solution.

Notes

  • This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
  • If you're interested in the generator code, see the "generator" directory.
  • This layout is just a suggestion.
  • Bullet points might work well. Paragraphs too. Up to you. :)

External Links

urgetopunt_welcome.jpg
Photo: John Parker (urgetopunt) (CC BY-NC-SA 2.0)

A crowd-sourced RailsConf wiki!
Working together is better. :)



Clone this wiki locally