I was reading up on GWT localization, and I came upon this strange
thing. Apparently, GWT designer uses the standard java localization
package (com.i18n.*), as can be seen on
http://code.google.com/webtoolkit/tools/gwtdesigner/features/internationalization.html.
On the other hand, GWT itself, through the tutorial and the
documentation (see 
http://code.google.com/webtoolkit/doc/latest/tutorial/i18n.html),
suggests using their custom package (com.google.gwt.i18n.*)

This seems more than weird. On one side, I like the integration of the
designer with internationalization; it makes it a much less cumbersome
process. But on the other hand, this approach is never mentioned on
another page. Is there actually a reason why the custom GWT
internationalization package is better than the default java version?

And if there is an advantage, wouldn't it make more sense for GWT
Designer to use it as well?

Kind regards,
Karel

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to