Databases Reference
In-Depth Information
Warning
If you change the primary application ID by exporting and importing an application, you will not be able
to reuse the XLIFF file. See the section “Moving Translations to Other Environments” for more details.
Translate Text
In this step, you have to edit the XLIFF file and translate all the text extracted from the primary
application.
Editing the XLIFF file is a relatively simple process. Since the XLIFF format is an official XML format
for translations, translators will be able to use the XLIFF files with their specialized software. This way ,
the translation could also be done by a third party. But in the majority of cases, a simple text editor can
be used to perform the translation as long as the text editor is UTF8 compatible. For example, PSPad is a
freeware editor that supports UTF8.
To translate the text, you have to change the values of the text contained between the
<target>
tags.
Only changes on the target tags will be taken into account when the file will be applied to the translation
repository.
<trans-unit id="S-5-101-122">
<source>Login</source>
<target>Connexion</target>
</trans-unit>
If the source tags are changed, these updates will not be applied to the primary application.
In the translation process, sometimes there may be text in the application templates that requires
translation as well. In order to have the template text included in the XLIFF file, these templates have to
be identified as translatable, as shown in Figure 5-11.
Figure 5-11.
Translatable option for templates
Check the Translatable checkbox in the template properties. This tells APEX to include the content
of the template in the XLIFF file.
Apply XLIFF Translation File to Translation Repository
Once the translation of the XLIFF file is complete, it must be uploaded and applied to the translation
repository. This will parse and insert the contents of the file in the APEX translation tables (see Figure
5-12).
