Choosing Names For Message Catalogs - BEA WebLogic Server Manual

Note: This directory path may vary, depending on where you chose to install
Catalogs that provide different localizations of the base catalogs are defined in
subdirectories named for the locale (for example,
might have a top-level catalog named
called
not required for any catalogs except the installed WebLogic Server catalogs.
Locale designations (for example,
java.util.Locale
variant. Language is the most common locale designation. Language can be extended
with a country code. For instance,
the associated catalog is
browser-specific and are used to introduce minor differences (for example, collation
sequences) between two or more locales defined by either language or country.

Choosing Names for Message Catalogs

Because the name of a message catalog file (without the
generate runtime class and property names, you should choose the name carefully.
Follow these guidelines for naming message catalogs:
For example, the resulting class names for a catalog named
XyzLogLocalizer
The following considerations also apply to message catalog files:
WebLogic Server.
..\de\mycat.xml
documentation. A locale can include a language, country, and
..\en\US\mycat.xml
Do not choose a message catalog name that conflicts with any names of existing
classes in the target package.
The message catalog name should only contain characters that are allowed in
class names.
Follow class naming standards.
and
XyzLogger
Message IDs are generally six-character strings with leading zeros. Some
interfaces also support integer representations.
Choosing Names for Message Catalogs
mycat.xml
. Typically the top-level catalog is English, but English is
) also have a hierarchy as defined in the
de
, indicates American English. The name of
en\US
.
for Germany). You
msgcat\de
, and a German translation of it
. Variants are vendor or
extension) is used to
.xml
are
Xyz.xml
Internationalization Guide
msgcat
2-3