Last night I gave a talk at the Boston Ruby Group on lessons learned working to internationalization our Rails application. I don’t claim to be a i18n (or Iñtërnâtiônàlizætiøn) guru, but have done my time in the trenches in Java-land and now in Rails. The good news is that the i18n story has gotten much better with Rails 2.2, but there still are pitfalls and pain points. I gave an overview of i18n concerns, how Rails supports i18n and, of course, plugged my plugin, Translator that aims to make it a little simpler.

The slides from the talk are below, on slideshare or in pdf format.