I found this gem a while back and it was great. I had already done internationalization for some sites using different approaches, so I was familiar with the basics of the internationalization capabilities of Rails applications. If you are interested, you should definitively read this guide.
I wanted to learn how to make my own gems and this approach of saving the translations in a database through ActiveRecord was really cool. And I did learn a lot. It was extracted from the master I18n repo some years back and was a bit abandoned. I submitted some patches and tried to gain some traction on the development of the gem, mainly:
- Updated the failing, 3 years old, test suite to pass and be compatible with Rails 4.
- Fix some bugs on the feature to store and manage missing translations.
Some of my pull requests are dated form more over a year ago and no one has said a word about them. That’s okay, though. I understand that is was not mainstream or widely used. So I maintained my own fork with the latest patches :)
This project served me to conceptualize the gem I18nline and helped me understand the trade-offs between different backend approaches and I am thankful for that.
In the latest development of i18nline I am moving on from this gem and instead I am using my own customization of a key-value backend, with Redis as my translations store. I18nline gem is now much faster on general querying, adding new translitions on the fly when parsing a page for the first time and also when caches need to be invalidated (as my active_record gem was using a chain backend with Simple at the tail, and every chache invalidation reloaded all yaml files).