Internationalizing a web site is the process of creating a site that is capable of displaying content in different languages. The Oracle Commerce Platform internationalization is based on Java internationalization standards. You can design an Oracle Commerce Platform web site for a single locale or for multiple locales. In your translated web pages, you can vary the display of data such as dates and currencies according to locale-specific formatting rules.
Internationalizing an application and localizing it are different activities:
Internationalization is the process of preparing a site for delivery in different languages.
Localization is the process of translating its contents for a specific locale or locales.
For example, an internationalized site is one that has its text messages separated into easily accessible resource files rather than included in the source code; that same site can then be localized easily by translating the text messages into French, for example. You do not have to localize your Oracle Commerce Platform application to create a web site in another language.
In this chapter
This chapter includes the following topics:
Overview: Briefly describes the basics of creating an internationalized web site.
Setting Up a Multi-Locale Oracle Commerce Platform Web Site: Introduces the steps involved in preparing an Oracle Commerce Platform web site to serve content to different locales.
Using ResourceBundles for Internationalization: Explains how to internationalize
ResourceBundle
files containing Strings that appear in your web site.Setting Character Encoding in JSPs: Describes how to specify a JSP’s character encoding by setting the content type within the page.
Using the EncodingTyper to Set the Character Encoding: Explains how to use the
EncodingTyper
component to determine the character encoding for posted data in forms.Configuring the Request Locale: Explains how to use the
RequestLocale
component to associate a character encoding with a request.Character Encoding and Locale Configuration Examples: Provides examples for setting the
EncodingTyper
andRequestLocale
components for different server and locale configurations.Setting the Java Virtual Machine Locale: Describes how to set the Oracle Commerce Platform server locale by changing the locale of the Java Virtual Machine.
Configuring the Database Encoding: Explains how to set the character encoding for the database server.
Setting the E-mail Encoding: Describes how to determine the character encoding for targeted e-mails.
Internationalizing Content Repositories: Describes how to configure content repositories to serve content for several different locales.
Creating Locale-Specific Content Pages: Explains how to set up and work with content pages for a localized site. Includes information on translating JSP tags.
Designing a Multi-Locale Entry Page: Describes how to create a top-level index page that acts as an entry point for a multi-locale site.
Converting Properties Files to Escaped Unicode: Describes how to convert properties files containing non-Latin or non-Unicode fonts to Unicode so that they can be processed by tools such as the Java compiler.
Localizing the Profile Repository Definition: Explains how to localize the entries in the profile repository definition file.
Localizing Profile Group Names, Scenario Names, and Similar Items: Describes how to localize some of the items that appear in the ATG Control Center interface.
Changing Date and Currency Formats: Introduces some options for displaying dates and currency information in localized web pages.
Using Third-Party Software on an Internationalized Site: Briefly describes the third-party software requirements for an internationalized Oracle Commerce Platform web site.
Before reading this chapter, you should be familiar with Java internationalization standards. For more information, refer to the JavaSoft Internationalization Specification at http://java.sun.com/j2se/1.3/docs/guide/intl/index.html.