Not if you dynamically generate the host html page, e.g. with JSP or simply a plain Servlet. So you could generate a different host page depending on the locale, deciding dynamically if such a locale is already available - without recompiling.
HTH Chris P.S. There may be other techniques that download the translations at a later point - maybe with ExternalTextResource or something similar - I'd be interested to hear what the best solution for this would be, too! On Feb 24, 12:03 am, Micah Whitacre <[email protected]> wrote: > You are referring to this correct?[1] Maybe I'm misunderstanding this > documentation but the localized strings are stored in the host HTML > file. It is storing both the keys and the values in the file. > Therefore wouldn't this require a another compilation of the war to > include the alternate locale host html file? Also wouldn't this > change how consumers use the application? If the html host file was > Foo.html, they would have to navigate to Foo_fr.html, Foo_de.html, > etc, correct? > > I just want to make sure I understand all of the maintenance concerns > down the road. > > Thanks for your help, > Micah > > [1] -http://code.google.com/webtoolkit/doc/latest/DevGuideI18n.html#DevGui... > > > > On Tue, Feb 23, 2010 at 2:57 PM, Chris Lercher <[email protected]> wrote: > > 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 > > athttp://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.
