Comments on: Rocking your application with Rails 2.2 i18n support

By: George Lee

George Lee — Tue, 24 Mar 2009 20:36:29 +0000

I’m trying to build a system that allows users to submit user-generated translations. If I store those user-generated translations in the database, any thoughts on how I do a “merge” the user-generated translations and my default yml file in the load_path?

By: Diego Carrion

Diego Carrion — Tue, 03 Feb 2009 13:29:51 +0000

Are you talking about the locale files Sanjay? In that case, you have to populate them manually.

By: Sanjay

Sanjay — Tue, 03 Feb 2009 02:13:09 +0000

A simple question, Who would provide all the country specific locale ? It seems Rails 2.2 doesn’t. Right ?

By: Diego Carrion

Diego Carrion — Sat, 01 Nov 2008 17:14:10 +0000

Hahaha bom saber Marcos. Nem teve tempo de fazer o teste, mas ainda bem parece que temos um problema a menos

O Rails 2.2 RC1 tem se mostrado bem estavel para mim, ate agora tudo andou bem (:

By: nofxx

nofxx — Sat, 01 Nov 2008 17:13:35 +0000

Eu sai do edge esses dias por uns probs estranhos, voltarei no 2.2.
Bom saber. Anotado…

Valeu denovo! Ah… offtpic here, aquela nossa discussion sobre o autosepc… parece que fix na versao 1.1.11 (25/10)

By: dc.rec1

dc.rec1 — Sat, 01 Nov 2008 17:09:48 +0000

Hi Sven, thanks for the corrections, will update the post right now

By: Sven

Sven — Sat, 01 Nov 2008 17:05:36 +0000

Hey, thanks for the awesome writeup!

Two minor things:

It probably should be:

I18n.load_path += Dir.glob(”config/locales/*.yml”)

so that existing paths (such as those provided by Rails) aren’t overwritten. This is what Karel does in his demo app:

I18n.load_path += Dir[ File.join(RAILS_ROOT, ‘lib’, ‘locale’, ‘*.{rb,yml}’) ]

Also, you might want to add a note that any direct access to the backend should rather be considered a hack Public I18n methods are always on the I18n module itself, backend implementations might change at any time