Globalization - Expert Oracle Application Express - page 259

Import the primary application using the same application ID in the other environment. Seed the
mapped application in the other environment to populate the translation repository.
Finally, apply the XLIFF previously downloaded and publish the translated applications.
Using this method will populate the translation repository and ensure you will have the same
translated version as your primary application. It will also allow the republishing of your translated
applications if changes must be made to the primary application.
Changing the Application ID
The translation metadata uses the application ID to generate the translated applications and to generate
its internal IDs used in the XLIFF file. If you make a copy of your primary application—that is, export and
import your application in another application ID—it will not be possible to apply the original XLIFF file
again. APEX will treat this application as a new application and the translation will have to be done all
over again. Imagine all the work that implies for an application of a 100 pages or more.
To re-create a proper XLIFF file when that is the case, an application is available on the Oracle
website here: http://apex.oracle.com/pls/apex/f?p=46992:1 . This application can map an XLIFF file to
a new application ID. This application generates a new XLIFF file with the appropriate IDs to match the
new application ID for the primary application. Please refer to Joel Kallman's blog post for more details:
http://joelkallman.blogspot.com/2010/07/moving-your-xliff-files.html.
A copy of the XLIFF file should then be stored with the source of the applications in a source version
control tool. This way, if a change must be made to that version of the application, a corresponding
XLIFF file will exist and therefore will make it possible to regenerate and publish the translated
applications.
Also note that in order to apply the XLIFF in another environment, a seed must first be created to
populate the translation repository before applying the XLIFF file. Data must exist in the translation
metadata repository in order to apply an XLIFF file and publish. Applying an XLIFF file against an empty
repository will not do anything.
Localization
Localization refers to when data is displayed to the end-user based on his location. It could be the time
and date of a meeting or the number format used in the end user's region, for example. When localizing
applications, special attention must be paid to the different formats used for dates and numbers. Date
formats are different depending on the user's location.
Since APEX is a set of PL/SQL programs and runs in the Oracle Database, every database NLS setting
can be changed using an alter session.
Oracle also provides locale-sensitive date formats which, of course, can be used in APEX. For
example, a Long Date format DL can be used to show the date in different languages:
Alter session set NLS TERRITORY='CANADA';
Alter session set NLS LANGUAGE = 'FRENCH'
Select to char(sysdate,'DL') from dual;
TO CHAR(SYSDATE,'DL')
---------------------
lundi 21 février 2011
Alter session set NLS TERRITORY='CANADA';
Alter session set NLS LANGUAGE='ENGLISH'
Select to char(sysdate,'DL') from dual;