Skip to content
svenfuchs edited this page Sep 13, 2010 · 1 revision

We want to establish a convention that will allow Globalize and other i18n plugins to load multiple provided locales for Rails libraries and plugins. Our current idea is to have Globalize slurp up certain files (defined below) for each locale it needs to load. It would then pull in the relevant locale data from those files.

So, if Globalize finds it has to load the German locale, it would slurp locales/de-DE.yml, locales/de-DE/*.yaml and something like locales/all.yml.

This is easy to do, and would give authors the flexibility to put all translations in one file (all.yml), for plugins with just a few translated terms. This would scale to one per-language translations file (locales/de-DE.yml), and up to a bunch of translation files for each locale (locales/de-DE/*.yaml).