- 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
Workflow and vendor configuration
From Across Language Server v6.3 on, there are predefined workflows and configurations for all current vendors.
- The configuration consists of several parts for each vendor:
- Predefined workflows which have to be added to the crossAutomate Host Manager to enable the External Processing:
- C:\Program Files (x86)\Across\crossAutomate\%vendorname%\AcrossTo%vendorname%.xoml
- C:\Program Files (x86)\Across\crossAutomate\%vendorname%\%vendorname%ToAcross.xoml
- Preset watchfolders
- C:\Program Files (x86)\Across\crossAutomate\%vendorname%\FromAcross
- C:\Program Files (x86)\Across\crossAutomate\%vendorname%\ToAcross
- Filter configuration file where the rules can be configured which kind of tasks are subject of External Processing: C:\Program Files (x86)\Across\crossAutomate\%vendorname%\FilterRules.xml