Monday, February 23, 2015

Re: Static vs dynamic String internationalization


- The big advantage of dynamic internationalization to me, is that I can store my translations in a database, and update texts without the need of stopping servers to deploy a new compiled version of my application.
 
Not sure if its that big of an advantage. IMHO translations rarely change and the number of supported languages is probably already known upfront and does not change often either.

Also if done right, updating an app does not cause any downtime especially if only translations have changed or languages have been added. The worst case is that a user gets a message "App has been updated and needs to be reloaded". If your app uses history tokens (e.g. GWT places) then reloading the current place doesn't really hurt.

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment