- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- 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
- Solution approaches
- The Across solution in detail
- The display text format
- The display text package
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- ObjectManager - Overview
- ProjectManager - Overview
- WanGridManager - Overview
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
The Supply Chain
The Across supply chain is structured as follows.
Thereby the Across Language Server acts as central location for data, rights, etc. A Trusted Server is usually a language service provider that receives and distributes projects. For example, to a freelancer who works with the Translator Edition. He or she receives certain tasks.
The exchange takes place by means of a synchronization package via crossGrid and crossWAN.
We offer numerous connections and automation options. These are implemented using various, tailored Across APIs.
This can result in the following overall picture.
crossAPI System Integration (crossAPI SI) represents the "remote control" of all objects in Across. It is characterized by a deep integration via web services and maximum flexibility. This makes the crossAPI SI very complex and the processes for third-party systems may increase.
The Across Connector allows the exchange of translation data according to the hot folder principle. This means: a folder is constantly monitored and changes are immediately registered and correspondingly defined actions are automatically executed. The connector is characterized by a specific transfer format (Instruction.xml). The transfer format contains meta information. Translation files, reference attachments and loop files (looped, external data) are taken into account.
An optional converter is connected upstream of the Across Connector. This is responsible for creating the transfer file. It converts both input and output packets.
Machine translation systems (MT) can be controlled globally, i.e. from the Across Language Server. If the customer allows it, Trusted Servers can also connect and work with MT systems independently. An Across Translator Edition (ATE) can always use MT for its own projects.