This section describes the process of translating an application. To translate an application developed in App Builder, you must map the primary and target language, seed and export text to a translation file, translate the text, apply the translation file, and publish the translated application.
Topics:
The first step in translating an application is to map the primary and target application language. The primary application is the application to be translated. The target application is the resulting translated application.
To map the primary and target application language:
See Also:
The second step is to seed the translation table and then export the translation text to a translation file.
Seeding the translation copies all translatable text into the Translation Text repository. After you specify the language and seed the Translation Text, 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:
Once the translation mappings are established the translatable text within the application is seeded into a translation repository. This repository is then exported to an XML Localization Interchange File Format (XLIFF) file for translation.
Topics:
The XLIFF Export page is divided into two sections. Use the upper section 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.
Note:
XML Localization Interchange File Format (XLIFF) is an XML-based format for exchanging localization data. For more information about XLIFF and the XLIFF 1.0 specification, see:
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliffTo download an XLIFF file for an complete application:
See Also:
To download an XLIFF file for a specific page:
See Also:
When Oracle Application Express 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 the translation units.
After you export a translatable file to XLIFF format, you can translate it into the appropriate languages. Because XLIFF is an open standard XML file for exchanging translations, most translation vendors should support it. Oracle Application Express 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 are in the same character set.
Translation is a time-consuming task. Oracle Application Express supports incremental translation so that application development can be done in parallel with the translation. An XLIFF file can be translated and uploaded to Oracle Application Express even when only part of the XLIFF file is translated. For strings that have no translation in the corresponding translated application, Oracle Application Express uses the corresponding ones in the primary language.
See Also:
For more information about the XLIFF and the XLIFF 1.0 specification, see:
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
After your XLIFF document has been translated, the next step is to upload and then apply it.
Topics:
After 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 Application Express 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 to run an application in an alternative language, you must run it with globalization settings that 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 a translated XLIFF document:
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 to run an application in an alternative language, you must run it with globalization settings that 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 publish an application:
You should verify the existence of the translated application after it is published. Translated applications do not display in the Available Applications list on the App 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 App Builder, you must ensure that you have correctly configured the application Globalization attributes.