- 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
Paragraph State Flags
Translation state flags relevant for external processing:
Attention
External applications should only change single flags, but must not create flags from scratch.
Category | Name | Decimal value | Hexadecimal value | Description |
- | Bookmarked | 524288 | 0x00080000 | Bookmark attached to the paragraph. |
Flags set in crossDesk | Keep Source | 1024 | 0x00000400 | The paragraph does not require translation, it stays unchanged in the target document. |
Edit Before cTa Store | 2097152 | 0x00200000 | The translation should be adjusted before storing to the translation memory. | |
Document update | Updated | 65536 | 0x00010000 | Target text changed by a document update. Text was already translated in previous document version, but position of the paragraph changed. |
New In This Version | 268435456 | 0x10000000 | A document update created this paragraph which didn't exist before. | |
How the target text was created | Pre-translated | 131072 | 0x00020000 | Target text filled by a pre-translation with usual match. Set together with Was-Pretranslated. Is reset when target text changes or the paragraph is reset to untouched. |
Was-Pretranslated | 8388608 | 0x00800000 | Set permanently when paragraph was filled with pretranslation process. Is reset when the paragraph is reset to untouched. | |
Pre-translated External | 16777216 | 0x01000000 | Target text filled by an external pre-translation, e.g. a machine translation process. Set together with Was-Pretranslated, Pre-Translated, Was-Pretranslated. Is reset when target text changes. | |
Context Pre-translated | 67108864 | 0x04000000 | Target text filled by a context match. Set together with Was-Pretranslated. Is reset when target text changes. | |
Pre-translated Locked | 134217728 | 0x08000000 | Target text filled by a pre-translation, set to final state and locked to prevent changes. | |
Structure Pre-translated | 536870912 | 0x20000000 | Target text filled by a structure match. Set together with Was-Pretranslated. Is reset when target text changes. | |
Prefilled Multilingually | 1073741824 | 0x40000000 | Target text filled by the check-in of multilingual document (e.g. XLIFF document). |
Export Best Matches
Best crossTank matches for <trans-unit> elements are provided in <alt-trans> elements. For details, see Exporting best matches in Across XLIFF
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>
Encoding of Invalid XML Characters
To ensure that the generated XLIFF file is valid and no information is lost, all invalid XML is encoded using <x> elements, where the ctype attribute contains the hexadecimal Unicode code of the character in the following format: "x-hex:DDDD"
Example
<trans-unitid="4"ax:state-name="Touched"ax:state-id="2"ax:state-flags="8519680"><source>Text with<xid="1"ctype="x-hex:001A"/> invalid XML<xid="2"ctype="x-hex:0003"/> characters.</source><target>Text mit<xid="1"ctype="x-hex:001A"/> unzulässigen XML<xid="2"ctype="x-hex:0003"/> Zeichen.</target></trans-unit>