• Show convenient version of this site
  • Deutsch
  • English
Contact
Newsletter
  • Products
    • ALS
      • Across Language Server
        • Translation Management
        • Terminology Management
        • Translation Memory
      • Editions
      • Interfaces
    • ATE
      • Across Translator Edition
      • Editions
      • Download
      • Across Account
    • Elanion
      • Overview
      • Login
  • Solutions
    • Customers
      • Enterprises
      • Language Service Providers
      • Translators
    • Industries
      • E-Commerce & Trade
      • Pharmaceuticals & medicine
      • IT & Software
    • Departments
      • Marketing & E-Commerce
      • Technical Documentation
      • Software User Interfaces
  • Services
    • Hosting
    • Training
    • Consulting
  • Partners
    • Language Service Providers
    • Universities
    • Organisations
  • Company
    • Across Systems
    • News
    • Events
    • Career
    • Contact
  • Knowledge
    • Blog
    • Video Library
    • Case Studies
    • White Papers
    • Fact Sheets
    • File Formats
    • Expert Features
  • Support
    • Online Help
    • FAQ
    • Support Request
    • Updates
    • New Functions
Schedule Consultation
  • Online-Help
  • SDK
  • Connecting Third-party Systems
  • Generic File Connector
  • Package Format
  • Control File
  • General Information
    • Connectors
    • LCIDs
    • GUIDs
    • Paragraph states and flags
    • crossTerm Web
    • crossTransform
      • crossTransform - examples
  • Connecting Third-party Systems
    • crossConnect for content systems
      • Requirements
      • Configuration
        • Configuring the connector
        • Job configuration
        • Testing crossConnect
      • Troubleshooting
    • crossConnect for External Editing
      • Purpose and usage
        • Use case - Machine translation
        • Use Case - Review and QA
        • Use case - Machine review
      • 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
          • Adding workflows to crossAutomate Host Manager
          • Adjusting preset watchfolders
          • The filter rules
          • External editing workflows
        • Sample code - Integrated solution
    • Generic File Connector
      • Process Overview
      • Exchange Folder Structure
      • Package Format
        • Control File
  • Display Texts
    • Solution approaches
    • The Across solution in detail
    • Requirements
    • Integration
    • The display text format
      • Line height vs. line spacing
      • DT-XML format structure
        • DT-XML - Main elements
        • Children of paragraphStyles and characterStyles
        • Children of the sizeInfos element
        • Children of the paragraph element
        • DT-XML v5 example
        • DT-XML v4 example
    • The display text package
      • Creating a display text package
  • APIs
    • APIs - Technology
    • crossTank API v1
      • Requirements
      • Testing the crossTank API installation
      • OData-URLs in Chrome
      • Example
    • crossTank API v2
      • Requirements
      • QuickStart
        • Searching for Translations
        • Creating Translations
      • crossTank API v2 Overview
        • Finding Translations
        • Creating Translations
        • Translation Properties
        • Formatting and Auto-Adjustment of Formatting and Numbers
      • C# Example
    • crossTerm API v1
      • Scenarios of use
        • Example - usage information
        • Example - finding terms
      • Requirements
      • Special Controllers
      • OData-URLs in Chrome
      • crossTerm API with C#
      • crossTerm API with Java
      • crossTerm API with JavaScript
    • crossTerm API v2
      • Requirements
      • QuickStart
        • Authentication Basics
        • First Request Examples
      • crossTerm API v2 Example in C#
        • Used Functions
      • crossTank API, crossTerm API v2 - Authentication
      • crossTerm API v2 - Examples of Use
        • Finding Terms of Entry
        • Searching Terminology via API
    • crossAPI SI
      • Requirements
      • Function Return Types
      • crossAPI SI and Java
        • Example: hot integration
        • Executing the hot integration example
      • List of Objects in crossAPI SI
        • AssignManager
        • Authorization
        • CheckInManager
        • CheckOutManager
        • CrossTankManager
        • CrossTermManager
        • DocumentManager
        • FileManager
        • LanguageJobManager
        • LanguageManager
        • LicenseManager
        • Message
        • ObjectManager - Overview
          • Part 1
          • Part 2
          • Part 3
        • ReportManager
          • ID values for analysis and analysis-result
        • ProjectManager - Overview
          • Part 1
          • Part 2
          • Attribute Information
        • SqlQuery
        • SystemManager
        • TaskManager
        • WanGridManager - Overview
          • Part 1
          • Part 2
      • Sample - transferring checkout files via FileManager
      • Sample - VBS
    • Text Preprocessing API
      • Introduction
      • How to browse the API
      • Sentence splitting
      • Abbreviations

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>

Sections and Settings

Below you will find information on all the sections and settings in the control file.

Mandatory items are marked with an asterisk (*).

<instruction>*

The root node of the instruction file.

source*

Name of the creating CMS. The name is used to check for compatibility.

Element
Attribute
XPath
instruction
 
/instruction
source
/instruction/@source

<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

<attachment>

Entry for a project attachment. Multiple attachments can be specified.

path*

File name and relative path within the package. The name must be different for all specified attachments.

Element
Attribute
XPath
attachment
 
/instruction/project/attachment
path
/instruction/project/attachment/@path

<attribute>

Entry for additional project attributes. Multiple attributes can be specified.

name*

Name of the attribute. The name needs to be spelled as it is in Across.

Element
Attribute
XPath
attribute
 
/instruction/project/attribute
name
/instruction/project/attribute/@name

<value>*

Entry for attribute values. At least one value must be specified within the context of the containing attribute. Multiple values can be specified. Currently, this value is supported via XPath extraction.

Element
XPath
value
/instruction/project/attribute[@name='Attribute name']/value

<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

<projectdescription>

Contains the text of the project description.

Element
XPath
projectdescription
/instruction/project/projectdescription

<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

<source>*

Contains the specification of the source language for all documents.

Element
XPath
source
/instruction/source

<target>*

Contains the specification of the target languages for all documents.

Element
XPath
target
/instruction/target

<language>*

Contains the definition of a language.

Element
XPath
language
/instruction/source/language
/instruction/target/language

<languageDef>*

Contains the definition of a language.

Element
XPath
languageDef
/instruction/source/language/languageDef
/instruction/target/language/languageDef

<ISO>*

Contains the definition of an ISO language.

Element
XPath
ISO
/instruction/source/language/languageDef/ISO
/instruction/target/language/languageDef/ISO

<language>*

Contains the ISO language code for a language.

Element
XPath
language
/instruction/source/language/languageDef/ISO/language
/instruction/target/language/languageDef/ISO/language
Register for our Newsletter now

Our newsletter provides you with exclusive news about the Across Language Server, often even before the official announcement. The newsletter also provides you with early information on events, webinars, and training sessions.

  • Legal Notice
  • GTC
  • Privacy Statement
  • Cookies
  • info@across.net