There are three types of Oracle ATG Web Commerce ResourceBundles:

The only ResourceBundles that you need to translate to create an internationalized web site are the ResourceBundles that affect the web site visitor’s content.

The visitor’s request locale determines the locale of the ResourceBundles that store user content for an internationalized web site. For example, if the user visits an internationalized Oracle ATG Web Commerce web site, and the user’s visitor locale is Japanese, the file is used to generate user messages in Japanese.

In order to internationalize an Oracle ATG Web Commerce web site, all visitor locale files must be copied and renamed for each locale, according to Java naming guidelines. These naming conventions are necessary in order for the Java locale inheritance system to work correctly. The renamed .properties files must then be translated according to the Oracle ATG Web Commerce translation guidelines.

For information on ResourceBundle inheritance, see the ResourceBundle Inheritance topic. For information on ResourceBundle naming, see the Internationalizing ResourceBundles section. For detailed information on ResourceBundles, see the Java documentation for java.util.ResourceBundle.

By default, Oracle ATG Web Commerce does not log the names or prefixes of resource bundles if the server’s locale is set to en by the JVM (see Setting the Java Virtual Machine Locale). To change this behavior, set the logResourceNames property in the /localconfig/ file to true.