Open bwagner5 opened 10 years ago
I haven't seen this plugin..seems to be great! I think the ideal thing would be to look for translations in the DB and fallback to i18n properties (I don't know if this plugin does), just overriding the i18n properties with the ones in the database, using the bundles hierarchy in Java. Doing like this, the people that do not need this functionality won't do anything and if they need it in the future, they will just need to add a new record in the DB through the UI.
There's also - https://github.com/goeh/grails-i18n-db (less up-to-date, but recently used as part of the GR8 CRM i18n plugin)
The Localizations (Messages) plugin [http://grails.org/plugin/localizations] :
-Create a domain class and corresponding table called Localization -Prepopulate the table with all the message properties it finds in the i18n folder -Ensure Grails writes i18n messages based on what it finds in the database rather than the 118n folder
In addtion the plugin also has these added features to help you:
-A CRUD UI to add, delete, and update i18n messages -A cache for increased speed -A JSONP action which can be useful in client-side templating.
It would be nice to have the internationalization database backed and integrate a custom UI to update messages. This is a pretty common need for a lot of clients (update i18n messages at runtime).
May be able to use the Localization (Messages) plugin http://grails.org/plugin/localizations