> Anyone care to comment on the need to anticipate that a user will > switch their browser's language settings mid-use in a GWT app, thereby > encountering the problem that i8N constants are compile-time?
That only seems to reload the application which could be dealt with by using history to get you back to the same place. I use a locale string in the url ["&locale=jp"] and even if I change firefox Character Encloding to "Western ISO-8859-1" it reloads and then still displays Japanese as requested by &locale=jp. Thus if I wanted to change to English, I'd need to have a button or link to request &locale=en. I could see this as necessary if a Japanese user asks and English one for help. The key would be having history able to navigate back to the same page (and a cookie to not need to re-signin, but I'm not quite that far yet). Shawn -- 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.
