- 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
Control File
instruction.xml Example
Below you will find the content of an uncommented instruction.xml file.
You can download a commented instruction.xml file here.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <instruction source="CMS Name" xmlns="http://www.across.net" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.across.net instructions.xsd"> <files> <file name="File1.xml" workflow="Translation and correction" /> <file name="SubFolder1\File2.xml" workflow="Translation and correction" /> </files> <project name="Project Name" deadline="2121-08-13 23:00 +02:00" projectsettings="Default" > <projectmanager name="project.manager.one" /> <projectmanager name="project.manager.two" /> <attribute name="Subjects"> <value>Marketing</value> </attribute> <attribute name="Relations"> <value>Relation A</value> <value>Relation B</value> </attribute> <attachment path="attachment1.docx" /> <attachment path="SubFolder2\attachment2.docx" /> <loopfile path="loopMe.txt" /> </project> <source> <language> <languageDef> <ISO> <language>en-US</language> </ISO> </languageDef> </language> </source> <target> <language> <languageDef> <ISO> <language>de-DE</language> </ISO> </languageDef> </language> <language> <languageDef> <ISO> <language>fr-FR</language> </ISO> </languageDef> </language> </target> <meta /> </instruction>
<file>*
Entry for a translation file. At least one file must be specified. Multiple files can be specified.
name*
File name and relative path within the package. The name must be different for all specified files.
workflow
Name of the Across workflow. Only the first value specified will be used for all files. Currently, this value is supported via XPath extraction.
Element | Attribute | XPath |
file | /instruction/files/file | |
name | /instruction/files/file/@name | |
workflow | /instruction/files/file/@workflow |
<project>*
Entry for a project.
name*
Name of the project.
deadline
Due date of the project. The supported date format is: yyyy-MM-dd HH:mm zzz
The value must be in the future and must contain timezone information. If the value is omitted, a default offset of 14 days is used.
projectsettings
Name of the project settings template in the TMS. The name needs to be spelled as it is in Across, but the comparison is case insensitive. Currently, this value is supported via XPath extraction.
Element | Attribute | XPath |
project | /instruction/project | |
name | /instruction/project/@name | |
deadline | /instruction/project/@deadline | |
projectsettings | /instruction/project/@projectsettings |
<loopfile>
Entry for a file that will be contained in the output package unchanged. This setting can be used if the CMS needs specific files in the package to also be present in output packages. Multiple files can be specified.
path*
File name and relative path within the package. The name must be different for all specified files.
Element | Attribute | XPath |
loopfile | /instruction/project/loopfile | |
path | /instruction/project/loopfile/@path |
<project manager>
Specifies an additional project manager in the TMS.
name*
Name of the project manager in the TMS. Supports both login name and display name in the TMS. Currently, this value is supported via XPath extraction.
Element | Attribute | XPath |
project manager | /instruction/project/projectmanager | |
name | /instruction/project/projectmanager/@name |