Great idea to pluginize this, Andreas! However, it didn't work as expected for me. I mess with I18n.load_path in a config/initializers file. Since these are loaded after plugin initialization, the plugin simply did not see my locale.yml files and thus failed to import the respective localisation files.
To work around this, I've put your init.rb stuff into after_initialize which is executed after config/initializers. Here's the corresponding commit: http://github.com/Nielsomat/rails-i18n/commit/01d6f7448c6ec1637c8ef0cfa98b9488a21a28d3 Best, Niels On Dec 27 2008, 1:19 pm, Andreas Neuhaus <[email protected]> wrote: > Hi everybody, > > As a result of looking for an easier way to pull in core translations > from Sven's rails-i18n repository into my own apps, I refactorerd his > repository so that it can now be used as a Rails plugin. Installing > rails-i18n as a plugin automatically pulls in core translations for > locales used by the application. This makes it easier to manage Rails > core translations in an app (e.g. simply update the plugin to get new/ > udated core translations). > > My fork of the repository is athttp://github.com/zargony/rails-i18n. > What do you think? > > regards, > Andreas Neuhaushttp://zargony.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
