Hi Gary, Here is my view and we could figure out the details in AIFA group discussion. * GWT has i18n guide : * http://code.google.com/webtoolkit/doc/latest/DevGuideI18n.html * http://code.google.com/webtoolkit/doc/latest/tutorial/i18n.html* for static pages, we could have the servlet to do language negotiating and redirect to language specific subpath. We could add options on top bar for language selection to override negotiation result. * first step is to organize folder structures to store those static pages in language category. * servlet/jsp/java also have mature i18n mechanism and would work in App Engine.
In short term, Chrome browser have the built-in translator (using google translate) for web pages and that could be used. rrtom On Dec 16, 12:31 am, Gary Frederick <g...@jsoft.com> wrote: > Howdy > > I am internationalizing an app. It has static pages. Some of it is GWT. > however > The first step is to have the static pages and I hope to use something like > Apache's MultiViews language negotiation. > > Is that the way to go? > > What should I do? > > Gary -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
