Re: internationalization

On 17 mai, 12:14, Joschua <cit_corperat...@gmx.net> wrote:
> Hello guys, there are three (open) questions about the
> internationalization of GWT, I have:
>
> 1) Is it a (huge) performance issue, to use only "Messages" for
> constant and parameterized text, where usually would use both
> "Messages" and "Constants"?

No. Constants in "Messages" are finally compiled to the exact same
code as if they were in a "Constants". The real difference is that
Messages is limited to Strings.

> 2) Is there a way to specify the original text in the source code,
> whose translations can then be specified somewhere? (e.g.
> Translate("Hello") in the source code and than in a properties file
> for e.g. spanish: Hello = ¡Hola!)

Only using the @DefaultXxxValue or @DefaultMessage annotations

> 3) Do you know any translation-tools, which generate the properties
> and interfaces for you?

You'd generally create the interfaces "on the go", adding methods
while you need a new constant. Then, compiling your app with the -gen
argument will create the corresponding *.properties file that you can
now translate,using any tool you like (I don't use any but I know
there exists some) or give to translators (we're generating an Excel
file that we give to our customer, one column per language, and
generate the *.properties back when translated)

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.