How to Version a Custom Skin What Happens When You Version Custom Skins

Customizing the Appearance Using Styles and Skins 20-29 Note the two leading periods in front of the image path ..adforacleskinimagescfsortl.png. This allows the search for the META-INF root to start one directory above the META-INFskin directory in which the CSS is located. 3. Check that the trinidad-skins.xml file is located in the META-INF directory and that it contains content in a format similar to this: ?xml version=1.0 encoding=ISO-8859-1? skins xmlns=http:myfaces.apache.orgtrinidadskin skin idrichdemo.desktopid familyrichDemofamily extendsfusion.desktopextends render-kit-idorg.apache.myfaces.trinidad.desktoprender-kit-id style-sheet-nameskinsrichdemorichdemo.cssstyle-sheet-name skin skins This example defines the skin as richdemo.desktop in the richDemo family. The trinidad-skins.xml file can have more than one skin definition. The richdemo.css file or your custom CSS file is referenced from the style-sheet-name element. 4. To create the JAR file, issue the following command from the c:\temp directory: jar -cvf customSkin.jar META-INF 5. Copy the resulting customSkin.jar file to the WEB-INFlib directory of the consuming ADF project. Configure the trinidad-skins.xml file located on the WEB-INF directory of the ADF project. ?xml version=1.0 encoding=windows-1252? trinidad-config xmlns=http:myfaces.apache.orgtrinidadconfig skin-familyoracleblafskin-family trinidad-config Because the skin can be discovered at runtime, you do not need to code the skin family name. Note: The skin definition in the JAR file is not displayed in the JDeveloper visual editor. You may see a message in the log window that the skin family could not be found. You can ignore this message. 20-30 Web User Interface Developers Guide for Oracle Application Development Framework 21 Internationalizing and Localizing Pages 21-1 21 Internationalizing and Localizing Pages This chapter describes how to configure JSF pages or an application to display text in the correct language of a user’s browser. This chapter includes the following sections: ■ Section 21.1, Introduction to Internationalization and Localization of ADF Faces Pages ■ Section 21.2, Using Automatic Resource Bundle Integration in JDeveloper ■ Section 21.3, Manually Defining Resource Bundles and Locales ■ Section 21.4, Configuring Pages for an End User to Specify Locale at Runtime ■ Section 21.5, Configuring Optional ADF Faces Localization Properties

21.1 Introduction to Internationalization and Localization of ADF Faces Pages

Internationalization is the process of designing and developing products for easy adaptation to specific local languages and cultures. Localization is the process of adapting a product for a specific local language or culture by translating text and adding locale-specific components. A successfully localized application will appear to have been developed within the local culture. JDeveloper supports easy localization of ADF Faces components using the abstract class java.util.ResourceBundle to provide locale-specific resources. When your application will be viewed by users in more than one country, you can configure your JSF page or application to use different locales so that it displays the correct language for the language setting of a user’s browser. For example, if you know your page will be viewed in Italy, you can localize your page so that when a user’s browser is set to use the Italian language, text strings in the browser page will appear in Italian. ADF Faces components may include text that is part of the component, for example the af:table component uses the resource string af_table.LABEL_FETCHING for the message text that is displayed in the browser while the table is fetching data during the initial load of data or while the table is being scrolled. JDeveloper provides automatic translation of these text resources into 28 languages. These text resources are referenced in a resource bundle. If you set the browser to use the language in Italy, any text contained within the components will automatically be displayed in Italian. For more information on skins and resource bundles, see Chapter 20, Customizing the Appearance Using Styles and Skins .