- 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
Use case - Machine translation
In case of machine translation, the process is as follows:
Step | Tool | Description |
1 | Across Language Server | A finished pre-translation process triggers a corresponding event. |
2 | crossAutomate |
|
3 | Across Trusted Integration Solution | The Trusted Integration Solution watches for new files in the exchange folder and triggers the integration process. |
4 | The Across Trusted Integration Solution uses the provided vendor library to read the plain XLIFF from the encrypted EWU file. For adding machine translations, the provided XLIFF files have to be parsed.
For the paragraphs processed by the machine translation, the machine translated text should be inserted into the <target> tags.
Tip The Across Trusted Integration Solution must ensure that the decrypted XLIFF file can only be processed in the Trusted Integration Solution. Exports must not be possible. | |
5 | When machine translated strings are added to the XLIFF file, the vendor library comes into play again. The changed XLIFF content is written via the security functions to a so-called External Editing Response Unit (ERU) and stored in the exchange folder ToAcross. | |
6 | crossAutomate | crossAutomate watches for new files in the ToAcross folder and triggers the import process. |
7 | The import process imports the data in Across. |
More information on secure file handling:
More information on XLIFF: