So the only way to keep the translated property files in sync with the property file for the default language is to use diff? But that doesn't really solve the problem as the property-files in e.g. Italian and the default language, say English, are completely different by nature.
1) How would you ensure that the Italian property file has exactly the same properties (messages) as the English one using diff? Some kind of combination of the unix "cut" command combined with "diff"? 2) How would you ensure that messages that are only modified (not added nor removed) in the English property file are also updated in the Italian version. In that case the properties indeed exists in both files. Notice that there might be plenty of repository-commits between each upgrade of the Italian translation as the Italian translator is only hired, say once a month. In other words: How should we provide the translator with a list of messages he should addremove and which messages that he should update according to the modifications in their corresponding English versions? (In gettext a "merge"-script keeps track of all this automatically and in that way, all the translator needs to know is written in the gettext-equivalent to the property file) Thanks for your answers! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
