I also found this handy site http://99translations.com where you can upload the properties file from GWT and they have a system for tracking changes etc.. no need to hack up any scripts for using Excel!
On Aug 18, 6:04 am, Thomas Broyer <[email protected]> wrote: > On 18 août, 06:38, Dobes <[email protected]> wrote: > > > What tools are people using for localization? > > > For example, currently I've defined all my strings using @DefaultValue > > (...) for my Constants interface instead of a properties file - is > > there a tool out there to convert an interface into a properties file, > > Add a @Generate(format = > "com.google.gwt.i18n.rebind.format.PropertiesFormat") attribute to > your Messages or Constants interface and then just compile your > project (if using GWT 1.6 or higher, pass the -extra argument with the > target directory as the value) and it'll generate the properties file > from the interface (if using GWT 1.5, in the www/<module>-aux > directory). > > > or validation a properties file against and interface? > > AFAICT, you'll have exceptions if a key isn't translated, so there's > some kind of validation built-in when you compile the project. > > > > > > > Has anyone seen a tool to take all the properties from the interface > > including the @Meaning annotations and generate/update and excel > > spreadsheet from that with columns "Untranslated", "Meaning", "ID"? > > This could be used as the first step of the translation workflow. > > > Next I could merge this file with any prior translations by detecting > > any rows where the "Untranslated" or "Meaning" has changed or added > > and produce a new Excel file with additional columns "Old > > Untranslated", "Old Meaning", and "Old Translation". This file can be > > sent to the translators for translation, who would be responsible for > > filling in the "translation" column only. > > > When it comes back I need another tool to extract the ID and > > Translation column data and dump that into the appropriate .properties > > file. > > > I'm thinking I'm not the only one who needs to create and update > > translations of their GWT app, but so far my Googling hasn't turned up > > any tools for this - especically the first step where the interface > > IDs and meanings are extracted out into a useful format. > > > Anybody got anything to help with this? > > We're in the process of translating our app (read: imported the > generated properties file into an Excel sheet –just key/default > message, as we do not (yet) use @Meaning et al.– and have it > translated, translations not yet turned back into a properties file) > so I guess the answer is "not yet", but I'm definitely interested in > whatever you could find about it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
