Best practice for tracking i18n shortcuts that need translation in Grails?

Question

I am working on a Grails project that is international (using .properties resource packages), and at the end of each version we send a list of all the i18n messages that need to be translated. The problem is that there is no way to find out which ones need to be updated / which ones are missing without manual marking (for example, adding some “magic word” at the end of each key). It seems very hacked and error prone.

What is common practice for tracking i18n uninterrupted shortcuts?

Thanks.

Answer 1

Missing tags can be automatically detected using ResouceCheck ant. In particular, with a cross bundle check he can tell you if the label is missing in any properties for any language.

For updated labels, I usually store the version number of messages.properties , which was last used as the translation source in the header comments in each messages_xx.properties . Then the difference between the current version of messages.properties and the original version of the translation will display the properties that have been changed and need to be relayed.