About Internationalization and Localization Standards Understanding Internationalization and Localization for WebLogic Server

3 Internationalization and Localization for WebLogic Server 3-1 3 Internationalization and Localization for WebLogic Server The following sections provide an overview of localization and internationalization: ■ Section 3.1, About Internationalization and Localization Standards ■ Section 3.2, Understanding Internationalization and Localization for WebLogic Server ■ Section 3.3, Understanding Message Catalogs ■ Section 3.4, Understanding Java Interfaces for Internationalization ■ Section 3.5, Main Steps for Creating an Internationalized Message

3.1 About Internationalization and Localization Standards

Oracle has adopted the World Wide Web Consortiums W3C recommendations for standard formats and protocols that are usable worldwide in all languages and in all writing systems. These standards are part of the Java internationalization APIs that are used by WebLogic Server. Internationalization I18N refers to the process of designing software so that it can be adapted to various languages and regions easily, cost-effectively, and, in particular, without engineering changes to the software. Localization L10N is the use of locale-specific language and constructs at run time.

3.2 Understanding Internationalization and Localization for WebLogic Server

Localization covers not only language, but collation, date and time formats, monetary formats, and character encoding. Messages that are logged to the WebLogic server log can be localized to meet your particular requirements. WebLogic Server internationalization supports localization of two types of data: ■ Log messages - Log messages are informational messages that are written to the server log, and may also contain error messages if the appropriate message arguments are included in the message definition. See Section 4.5.2, Elements of a Log Message Catalog. ■ Simple text - Simple text is any text other than log messages and exceptions that the server must display, such as the output from a utility. Examples of simple text include usage messages, graphical user interface GUI labels, and error messages. See Section 4.5.4, Elements of a Simple Text Catalog. 3-2 Oracle Fusion Middleware Using Logging Services for Application Logging for Oracle WebLogic Server

3.3 Understanding Message Catalogs