If I understand your question correctly, what you're looking for is a tool to let you know if there are strings in your codebase that you haven't yet removed and put into .properties files.
If that's the case, I don't think mergelocales.py will help you much. What we did with our app is two things: 1) Running old fashioned regexs on *.ui.xml files and on the .java files. I don't have the strings handy but roughly: -- UI-Binder Files: strings between tags, title attributes, value attributes... and any other custom attributes you might use with widgets. -- Java Files: anything between two " marks :-) 2) Make a "translation" in one of the languages (in our case we chose German) and just put empty strings or "XXX" for all the translations. When you run the app in locale=de, any strings that pop out, you'll know you need to go back and internationalize. Mergelocales.py is a great library, btw. We use it on our project with great success. It's just that it solves a different problem (If I've understood your question correctly, of course!) --Erik On Mon, May 30, 2011 at 22:32, spierce7 <[email protected]> wrote: > Thank you very much. I'll look into it. > > On May 30, 4:05 am, Jānis Ābele <[email protected]> wrote: > > Look athttp://code.google.com/p/gwt-platform/wiki/MergeLocale, it does > what > > you want. > > -- > 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. > > -- 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.
