Step 2: Seed and Export Text to a Translation File

The second step is to seed the translation table and then export the translation text to a translation file.

Topics:

Seeding Translatable Text
Exporting Text to a Translation File

Seeding Translatable Text

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:

Navigate to the Translate Application page:
1. On the Workspace home page, click the Application Builder icon.
2. Select an application.
3. Click Shared Components.
4. Under Globalization, click Translate Application.
  
  The Translate Application page appears.
On the Translate Application page, select Seed translatable text to translation repository.
From Language Mapping, select the appropriate primary and target application ID map and click Next.

Click Seed Translatable Text.

The XLIFF Export page appears.

Note:

XML Localization Interchange File Format (XLIFF) is an XML-based format for exchanging localization data. For information about the XLIFF or to view the XLIFF specification, see:

http://www.xliff.org

Exporting Text to a Translation File

After 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, including 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 if you must export translatable text for an entire application or just a specific page.

The XLIFF Export page is divided into two sections. Use the upper section 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.

Exporting Translatable Text for an Entire Application

To export translatable text for an entire application:

Seed the translatable text. See "Seeding Translatable Text".
Click Download translatable text from repository to translation file (XLIFF FILE):
1. From Application, select the appropriate primary and target application ID map.
2. Specify whether to include XLIFF target elements.
3. Under Export, specify what translation text is included in your XLIFF file.
4. Click Export XLIFF.
Follow the on-screen instructions.

Exporting Translatable Text for a Specific Page

To export translatable text for a specific page:

Seed the translatable text as described in "Seeding Translatable Text".
Click Download translatable text from repository to translation file (XLIFF FILE):
1. From Download XLIFF file for Application Page, select the appropriate primary and target application ID map.
2. Specify whether to include XLIFF target elements.
3. Under Export, specify what translation text is included in your XLIFF file.
4. Click Export XLIFF.
Follow the on-screen instructions.

About Including XLIFF Target Elements

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.

About Export

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