Importing Translations of Generated Text
Once you have received a translated XLIFF file from your translator, you must import it into the stylesheet. The purpose of this action is to match the translations in the XLIFF file with their source translation units in the stylesheet. When the source and target have matched, and import of a new translation has succeeded, Arbortext Styler will mark the translation in the stylesheet as current.
The expected result of an import of translated generated text is a stylesheet where all the translation units that were marked as needing translation receive their translations and are marked as current. When this has been done, the correct language version of generated text will be output when you publish a language version of your document.
Before beginning the import, note that changes to generated text may or may not have caused a change in the status of its translation:
• If you have created a new translation unit in the stylesheet, or modified the content of an existing translation unit, its translation will be marked as not current. It will need a first or new translation to be imported for it to be marked as current.
• If you have only modified the markup in a translation unit, Arbortext Styler will not change the status of the translation. These changes can be propagated to the translation.
You may want to check the status of translations in your stylesheet. Choose the > menu option to view information on the status of all the translation units in the stylesheet, as well as the dates the XLIFF files were last exported and imported. Refer to
Translation Statistics for a summary of the information this report contains.
To import translations of generated text:
The menu option is not available if you have not specified any target languages for generated text.
2. In the dialog box, select the XLIFF file(s) that you wish to import and click Import to begin the process.
3. Arbortext Styler will import translations from the XLIFF files into your stylesheet, according to the following rules:
◦ If the target value of the trans-unit in an XLIFF file has not changed since the last import and the translation in the stylesheet is marked as current - the target is not imported.
◦ If the target value of the trans-unit in an XLIFF file has not changed and the translation in the stylesheet is not current, you will receive a prompt to confirm whether you want the existing translation in the stylesheet to be marked as current.
▪ If you want to mark the existing translation as current, answer Yes.
For example, you may have changed the generated text in the stylesheet but do not want to change the translation.
▪ If you don’t want to change the status of the translation in the stylesheet, answer No.
For example, you may have changed the generated text in the stylesheet and intend to change the translation, but have not yet done so.
◦ If the target value of the trans-unit in an XLIFF file remains the same as the source value, and the status attribute still has a value of new, and the translation in the stylesheet is not current, you will receive a prompt to confirm whether you want the existing translation in the stylesheet to be marked as current.
▪ If you want to mark the existing translation as current, answer Yes.
For example, it is feasible that the translation is the same as the source.
▪ If you don’t want to change the status of the translation in the stylesheet, answer No.
For example, you may not have translated this generated text yet, but intend to do so.
◦ If the target value of the trans-unit in an XLIFF file is different from the translation in the stylesheet, and the translation in the stylesheet is marked as not current, the translation will be imported. This is the usual case - a translation has been requested and is available for import.
◦ If the target value of the trans-unit in an XLIFF file is different from the translation in the stylesheet, but the translation in the stylesheet is already marked as current, you will receive a prompt to confirm that you want to continue with the import.
▪ If you want to overwrite the current existing translation, answer Yes.
For example, you may have refined the translation and wish to apply it.
▪ If you wish to maintain the current existing translation, answer No.
◦ If the source value of the trans-unit in an XLIFF file does not match the source in the stylesheet, the translation will not be imported. If you have changed generated text in the stylesheet after exporting the XLIFF file, you must re-export the XLIFF file.
Note that if you have only changed markup in the generated text, you do not need to re-export the stylesheet.
4. If you receive an error that reports a tag pair mismatch, correct the target to ensure it includes balanced and properly nested markers for parameter markers representing tag pairs. Refer to
Guidelines for working with XLIFF files in
XLIFF Files for further information.
5. The Arbortext Styler log will display the results of your import. See Import Generated Text Translation Results Information below.
You can import an XLIFF programmatically via API. Please refer to
Using ACL to Import XLIFF Files for information.
Import Generated Text Translation Results Information
Arbortext Styler provides information about the status of a generated text import, and how each individual translation unit has been processed, when an import has finished. This information is written in the Arbortext Styler log window.
The following columns of information are available in the report:
• File Name - The name of the XLIFF file(s) imported during the import process.
• Language - The language(s) imported from the translation file(s).
• Total in Translation File - The number of translation units in each translation file.
• Total in Stylesheet - The number of translation units in the stylesheet that are set to be translated for each language. If the stylesheet has not been modified since the translation file was exported, this column should equal the number in the Total in Translation File column.
• Updated - The number of translation units in the stylesheet that have been updated or marked as current for each language, as a result of this import. The total number of current translation units in the stylesheet may be higher.
• Not Present in Translation File - The number of translation units in the stylesheet that did not have a corresponding translation unit in the translation file. This could happen if you edited the stylesheet after the translation file was created.
• Not Accepted - The number of translation units in the translation file you did not accept during the import process, by making either of two statements in dialogs presented during the import process:
◦ Do not import
◦ Do not mark as current in the stylesheet for this import