Soluling home Document home
Wizard - XLIFF Properties
Use this sheet to specify the properties of the XLIFF file that is written.
There are lots of different options for how to write an XLIFF file. Not every tool supports them all. This list lets you quickly select the properties set that is suitable for your tool. Possible values are:
|Default||Exported file contains the default properties.|
|Minimal||Exported file contains only the required properties.|
|Trados||Exported file contains the properties that are compatible with Trados.|
If your tool is not on the list, select Default or Minimal or set the properties manually.
Specifies the character set that the file uses. Possible values are:
|ANSI||Code page encoded. Each string uses the default Windows code page for the language of the string.|
|UTF-8||Unicode, UTF-8 encoded.|
|UTF-16, little-endian||Unicode, UTF-16 little-endian encoded.|
|UTF-16, big-endian||Unicode, UTF-16 big-endian encoded.|
|UTF-32, little-endian||Unicode, UTF-32 little-endian encoded.|
|UTF-32, big-endian||Unicode, UTF-32 big-endian encoded.|
|GB18030||Unicode, GB18030 encoded.|
UTF-8 is the default value. TMX and TBX support only Unicode formats.
Specifies the XLIFF version that is used when writing the file. Possible values are:
1.2 is the default value.
Specifies the target language. This is the language that the XLIFF file uses in the target elements. Only one languages can be the target language. If you have selected several language to be exported, the target language list contains them all. You have to select what is the target language. The other language will be exported as alternative translations.
For example the following XLIFF file use Japanese as target language and German as alternative translation:
<file source-language="en" target-language="ja"> <trans-unit> <source>Car</source> <target>車</target> <alt-trans>
Specifies the format of language ids. Right-click to choose a format from a popup menu or click ... to edit settings.
If checked, each id attribute contains a full context id. This is the parent id and the element id combined. If unchecked, each id attribute contains only the element id.
Note! If unchecked, the XLIFF file that Soluling creates is not necessarily strictly valid because some trans-unit elements might have the same id.
If checked, other selected languages but target language will be written into alt-trans elements.
The remaining checkboxes let you add some optional and custom properties into the export file. Possible values are:
|Data type||If checked, data types are written into the file.|
|Translation status||If checked, translation statuses are written into the file.|
|Invalidated||If checked, invalidated flags are written into the file.|
|Comment||If checked, comment values are written into the file.|
|Context||If checked, context values are written into the file.|
|Row status||If checked, row states are written into the file.|
|Disabled||If checked, disabled flags are written into the file.|
|Marked||If checked, marked flags are written into the file.|
|Max characters||If checked, the maximum length in characters values is written into the file.|
|Max pixels||If checked, the maximum length in pixels values is written into the file.|
These are available only when exporting from a project. When exporting from translation memory, these options are not available.
Specifies how the translation element is written. Possible values are:
|Write empty if no translation value||If there is no translation value, an empty translation element is written.|
|Write original if no translation value||If there is no translation value, the original value is written into the translation element.|
|Write always empty||An empty translation element is always written even if there is a translation value.|
|Write always original||The original value is always written into the translation element, even if there is a translation value.|
Write empty if no translation value is the default value.
Shows a sample file based on the current settings.