Hi, if I understand it correctly, isn't this what Dynamic String Internationalization on the page you mentioned is about? Depending on your application server, you'll have to put your properties files (or whatever format you use on the server) somewhere in the classpath of your application. There's usually some place you can add such files, but as I said, this depends on your app server.
Or alternatively, you can put the strings e.g. in a database. Chris On Feb 23, 9:37 pm, Micah Whitacre <[email protected]> wrote: > Hey All, > I've been reading all of the documentation on how to > internationalize a GWT application and it seems that all of the > different methodologies relate to having the translations available at > the compile time of the application. Is there a way to support > translations after the fact without having to recompile the entire GWT > application? As an example if I release the application and only > support EN, how can I add other locales such as fr, es, de without > having to edit the *.gwt.xml file or rebuild the war. I'd prefer to > just add jars with the additional translation property files to the > classpath. Is this possible? > > Thanks for your help, > Micah > > [1] -http://code.google.com/webtoolkit/doc/latest/DevGuideI18n.html -- 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.
