Are you writing code from scratch?
If so, you'll probably want
to read up on GWT's
static string internationalization
techniques.
Do you want to internationalize mostly settings or end-user messages?
If you have mostly settings (the kind of thing for which you'd
normally use simple properties files), consider
Constants. If you have a lot a of
end-user messages, then Messages is
probably what you want.
Do you have existing localized properties files you'd like to reuse?
The
i18nCreator tool
can automatically generate interfaces that extend either
Constants or
Messages.
Are you adding GWT functionality to an existing web application that
already has a localization process defined?
Dictionary will help you interoperate
with existing pages without requiring you to use
GWT's concept of locale.
Do you really just want a simple way to get properties files down to the
client regardless of localization?
You can do that, too. Try
using Constants without
specifying a locale.
Static string internationalization refers to a family of efficient and type-safe techniques that rely on strongly-typed Java interfaces, properties files, and code generation to provide locale-aware messages and configuration settings. These techniques depend on the interfaces Constants and Messages.
At the other end of the spectrum, dynamic string internationalization is a simplistic and flexible technique for looking up localized values defined in a module's host page without needing to recompile your application. This technique is supported by the class Dictionary.
Using an approach similar to static string internationalization, GWT also supports internationalizing sets of algorithms using locale-sensitive type substitution. This is an advanced technique that you probably will not need to use directly, although it is useful for implementing complex internationalized libraries. For details on this technique, see Localizable.
com.google.gwt.i18n
package:
The GWT internationalization types are included in the module
com.google.gwt.i18n.I18N
. To use any of these types, your
module must inherit from it:
<!-- --> <!-- Copyright 2007 Google Inc. --> <!-- Licensed under the Apache License, Version 2.0 (the "License"); you --> <!-- may not use this file except in compliance with the License. You may --> <!-- may obtain a copy of the License at --> <!-- --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or --> <!-- implied. License for the specific language governing permissions and --> <!-- limitations under the License. --> <module> <!-- other inherited modules, such as com.google.gwt.user.User --> <inherits name="com.google.gwt.i18n.I18N"/> <!-- additional module settings --> </module>
locale
client property.locale
client
property during deployment.