Databases Reference
In-Depth Information
The download will generate a
.xlf
(XLIFF) file containing the source application ID, the target
application ID, the source language, and the target language.
It is good practice to keep a copy of the XLIFF file with the export of your application. This way, if
ever a restore of the application is required, the corresponding XLIFF file will be available and you will be
able to publish and regenerate the corresponding mapped applications.
The XLIFF file contains all translatable elements, including labels, region titles, button names, and
more.
If we look at the header of the file, the source and target languages, as well as the generated XLIFF
filename, are specified. When using source control software, this gives indications of when the file was
generated:
<?xml version="1.0" encoding="UTF-8"?>
<!--
******************
** Source : 122
** Source Lang: en-ca
** Target : 9122
** Target Lang: fr-ca
** Filename: f122 9122 en-ca fr-ca.xlf
** Generated By: ADMIN
** Date: 07-FEB-2011 13:15:21
******************
-->
<xliff version="1.0">
<file original="f122 9122 en-ca fr-ca.xlf" source-language="en-ca" target-language="fr-ca"
datatype="html">
<header></header>
<body>
<trans-unit id="S-4-4463613133056390-122">
<source>Projets</source>
<target>Projets</target>
</trans-unit>
<trans-unit id="S-5-1-122">
<source>Projets</source>
<target>Projets</target>
</trans-unit>
<source>Login</source>
<target>Connexion</target>
</trans-unit>
.
.
.
Each trans-unit id is loaded into the translation repository and mapped with a specific component
in the primary application during the seed process. The trans-unit id is composed of a unit ID, a
metadata ID, and the application ID. In the example
<trans-unit id="S-4-4463613133056390-122">
, S-4
is an internal code that corresponds to the text of a tab, 4463613133056390 is the metadata ID, and 122 is
the primary application ID.
