- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Requirements
- Implementation
- Across XLIFF format
- Across-specific Extensions
- <xliff> Element Attributes
- <file> Element Extensions
- <trans-unit> Element Extension
- Paragraph States
- Paragraph State Flags
- <source> and <target> Element Content
- <bpt> Element Attributes
- <ph> Element Attributes
- <x> Element Attributes
- Across-specific Properties
- Analysis Results
- Sample Files
- Across XLIFF - import, export and segmentation
- Context information
- Exporting best matches in Across XLIFF
- Hyperlinks to XLIFF
- Secure file handling with C#
- Secure file handling with JAVA
- Workflow and vendor configuration
- Sample code - Integrated solution
- Across XLIFF format
- Generic File Connector
- Display Texts
- APIs
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Requirements
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
Exporting best matches in Across XLIFF
You can supply the Across XLIFF export file with information about best crossTank matches and its attributes (e .g. subject) for <trans-unit> elements. MT engines use this information when propose translations.
For crossGrid projects received on a Trusted Server, the match quality information is only available if another pre-translation has been triggered before the XLIFF export.
Prerequisites and limitations
Since search of the best crossTank matches can be time-consuming, it is not performed directly at export. Instead Across uses results of latest Pre-translation performed for the document. This means, that best matches will be exported to XLIFF only if the pre-translation was performed for the document at least once.
Best matches information is actual for the time of last pre-translation with Update pre-translation statistics flag.
Providing matches
The XLIFF format defines the <alt-trans> element aimed for providing possible translation matches. The match-quality attribute contains rate of the alternative translation. Each <alt-trans> might be associated with a certain segment (sentence) of the translation unit using mid attribute. The mid attribute value refers a segment defined in the <seg-source> section.
Translation unit example
<trans-unitid="4"ax:state-name="Touched"ax:state-id="2"ax:state-flags="8519680"><source>First sentence.</source><target>Translated first sentence.</target><alt-transmatch-quality="80%"><source>My first sentence.</source><target>My translated sentence.</target></alt-trans></trans-unit>
Two-sentences translation unit example
In case the <trans-unit> contains several segments (defined in the <seg-source> section), the mid attribute is used to refer the segment which the <alt-trans> is related to.
<trans-unitid="3"ax:state-name="Touched"ax:state-id="2"ax:state-flags="8519680"><source>First sentence. Second sentence.</source><seg-source><mrkmtype="seg"mid="1">First sentence.</mrk><mrkmtype="seg"mid="2">Second sentence.</mrk></seg-source><target><mrkmtype="seg"mid="1">First translated sentence.</mrk><mrkmtype="seg"mid="2">Second translated sentence.</mrk></target><alt-transmid="1"match-quality="100%"><source>First sentence.</source><target>Translated first sentence.</target></alt-trans><alt-transmid="2"match-quality="70%"><source>Second similar sentence.</source><target>Translated second similar sentence.</target></alt-trans></trans-unit>
Providing properties
To supply MT engines with various information related to crossTank matches, Across XLIFF format supports the extension of <alt-trans> element. This information is stored in the custom section <properties>.
Name | Description |
CreatedBy | Person created the match |
Created | Creation date |
ModifiedBy | Person last modified the match |
Modified | Modification date |
Note | Note text |
State | Possible values: "NewInserted", "SmartInserted", "Aligned", "Released". |
System Attributes (Subjects, Projects, Relations* and user defined attributes) | Attributes, associated with translation. |
Paragraph structure attributes* | Type of the resource which the translation is related to. |
* - name of the property is dependent on the locale of the ALS.
Export match properties example
<trans-unitid="4"ax:state-name="Touched"ax:state-id="2"ax:state-flags="8519680"><source>First sentence.</source><alt-transmatch-quality="80%"><source>My first sentence.</source><target>My translated sentence.</target><ax:properties><ax:propertyname="CreatedBy"><ax:value>Default Supervisor</ax:value></ax:property><ax:propertyname="Created"><ax:value>02/03/2016 19:15:47</ax:value></ax:property><ax:propertyname="ModifiedBy"><ax:value>Default Supervisor</ax:value></ax:property><ax:propertyname="Modified"><ax:value>02/03/2016 19:39:58</ax:value></ax:property><ax:propertyname="Note"><ax:value>Test note text</ax:value></ax:property><ax:propertyname="Subjects"><ax:value>General</ax:value></ax:property><ax:propertyname="Projects"><ax:value>Test project</ax:value></ax:property><ax:propertyname="Paragraph structure attributes"><ax:value>Button</ax:value></ax:property><ax:propertyname="State"><ax:value>Released</ax:value></ax:property></ax:properties></alt-trans></trans-unit>
The date format
To make result XLIFF content independent of a locale used on the server produced it, dates have culture-insensitive format (CultureInfo.InvariantCulture Property).