i18n is one of those matters which is really important, but few people in the English-speaking world really care about or understand. Clemens gave a good overview of how Rails i18n works now and what's coming next, illustrated with examples of both good and bad code from an i18n perspective. I found it very helpful.

Internalization (i18n) is a really important part of web frameworks, therefore it is essential in Rails as well. Given a framework like Rails you can interact with libraries in a simple and efficient way, which is often enough for most developers. i18n is not an exception either.

However, when you have to deal with more advanced features and tasks, you often end up having difficulties, you have to have a wider understanding of how the magic works in the background. And this is when Clemens comes in:

He presented the whole problem in a simple and sensible way, pretty much telling us how to 'domesticate' the library which would look like a monster for the first look. Good examples and simple explanation. I'm not afraid of digging deeper into the i18n library of Rails. Thank you.