|
Oracle® HTML DB
Release 2.0 |
|
 Previous |
 Next |
To translate an application developed in Oracle HTML DB, you must map the primary and target application IDs, seed and export text to a translation file, translate the text, and then apply and publish the translation file.
Topics:
You perform the translation process on the Translate Application page.
To navigate to the Translate Application page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Click Shared Components.
Under Globalization, select Translation Services.
The Translate Application page appears.
The first step in translating an application is to map the primary and target application IDs. The primary application is the application to be translated. The target application is the resulting translated application.
To map the primary and target application IDs:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Map your primary language application to a translated application ID.
The Application Mappings page appears.
Click Create.
On the Translation Application Mapping page:
Translation Application - Type a numeric application ID to identify the target application. The translated application ID must be an integer and cannot end in zero.
Translation Application Language Code - Select the language you are translating to.
Image Directory - Enter the directory where images will be obtained.
This attribute determines the virtual path for translated images. For example, if your primary language application had an image prefix of '/images/', you could define additional virtual directories for other languages such as '/images/de/' for German or '/images/es/' for Spanish.
Click Create.
The second step is to seed the translation table and then export the translation text to a translation file.
Topics:
To translate a application, you must seed the translations. Seeding the translation copies all translatable text into the Translation Text repository. Once you have seeded the application and specific language in the Translation Text repository, you can then generate and export an XLIFF file for translation.
The seeding process keeps your primary language application synchronized with the Translation Text repository. You should run the seed process any time your primary language application changes.
To seed translatable text:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Seed and export the translation text of your application into a translation file.
From Language Mapping, select the appropriate primary and target application ID map.
Click Seed Translatable Text.
The XLIFF Export page appears.
|
Note: XML Localization Interchange File Format (XLIFF) is a XML-based format for exchanging localization data. For information about the XLIFF, or to view the XLIFF specification see: |
Once you have seeded translatable text, a status box displays at the top of the XLIFF Export page indicating the total number of attributes that may require translation as well as the number of:
Existing updated attributes that may require translation
New attributes that may require translation
Purged attributes that no longer require translation
You can use this information to determine whether you need to export translatable text for an entire application or just a specific page.
The XLIFF Export page is divided into two sections. Use the upper half of the page to export translatable text for an entire application (that is, all pages, lists of values, messages, and so on). Use the lower section to export translatable text for a specific page.
To export translatable text for an entire application:
Seed the translatable text as described in the previous procedure, "Seeding Translatable Text".
Under Step 2, Export XLIFF:
From Application, select the appropriate primary and target application ID map
Specify whether to include XLIFF target elements
Under Export, specify what translation text is included in your XLIFF file
Click Export XLIFF for Application
Follow the on-screen instructions.
To export translatable text for a specific page:
Seed translatable text as described in "Seeding Translatable Text".
Under Export XLIFF for specific Page:
From Application, select the appropriate primary and target application ID map
Specify whether to include XLIFF target elements
Under Export, specify what translation text is included in your XLIFF file
Click Export XLIFF for Page
Follow the on-screen instructions.
When Oracle HTML DB generates an XLIFF document, each document contains multiple translation units. Each translation unit consists of a source element and a target element. The XLIFF document can be generated with both the source and target elements for each translation unit. You have the option of generating a file containing only source elements. The updated translations will be applied from the target elements of translation units.
Use the options under Export to specify what translation text is included in your XLIFF file. Select All translatable elements to include all translation text for an application. In contrast, select Only those elements requiring translation to include only new elements that have not yet been translated. Only those elements requiring translation produces an XLIFF file containing new or modified translation units. Also, if translation units were intentionally not previously translated (that is, the source of the translation element equals the target of the translation element), those translation units will also be included in the file.
After you export a translatable file to XLIFF format, you can translate it into the appropriate languages. Since XLIFF is an open standard XML file for exchanging translation, most translation vendors should support it. Oracle HTML DB only supports XLIFF files encoded in UTF-8 character sets. In other words, it exports XLIFF files for translation in UTF-8 and assumes that the translated XLIFF files will be in the same character set.
Translation is a time-consuming task. Oracle HTML DB supports incremental translation so that application development can be done in parallel with the translation. A XLIFF file can be translated and uploaded to Oracle HTML DB even when only part of the XLIFF file is translated. For strings that have no translation in the corresponding translated application, Oracle HTML DB uses the corresponding ones in the primary language.
|
See Also: For more information about the XLIFF, or to view the XLIFF specification see: |
Once your XLIFF document has been translated, the next step is to upload it back into Oracle HTML DB.
To upload a translated XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
Click Upload XLIFF.
On the XLIFF Upload page:
Specify a title
Enter a description
Click Browse and locate the file to be uploaded
Click Upload XLIFF File
The uploaded document appears in the XLIFF Files repository.
Once you upload an XLIFF document, the next step is to apply the XLIFF document and then publish the translated application. When you apply an XLIFF document, the HTML DB engine parses the file and then updates the translation tables with the new translatable text.
Publishing your application creates a copy of the base language application, substituting the translated text strings from your translations table. This published application can then be used to render your application in alternate languages.
Remember that in order to run an application in an alternative language, you need to run it with globalization settings that will cause an alternative language version to display. For example, if the language is derived from the browser language, you must set the browser language to the same language as the translated application.
To apply and publish a translated XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
In the XLIFF Files repository, click the View icon adjacent to the document you want to publish.
From Apply to, select the appropriate primary and target application ID map.
Click Apply XLIFF Translation File.
Click Publish Application.
To delete an uploaded XLIFF document:
Navigate to the Translate Application page. See "Step 1: Navigate to the Translate Application Page".
On the Translate Application page, select Apply your translation file and publish.
In the XLIFF Files repository, select the check box to the left of the document title.
Click Delete Checked.
You should verify the existence of the translated application once it is published. Translated applications do not display in the Available Applications list on the Application Builder home page. Instead, use the Application Navigate list on the left side of the page.
Note that in order for a translated application to appear in Application Builder, you need to make sure the you have correctly configured the application Globalization attributes.