• 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
  • Company
    • Across Systems
    • News
    • Events
    • Career
    • Contact
  • Knowledge
    • Blog
    • Video Library
    • Case Studies
    • White Papers
    • Fact Sheets
    • File Formats
    • Expert Features
  • Support
    • New Functions
    • Online Help
    • FAQ
    • Support Request
    • Updates
Schedule Consultation
  • Online-Help
  • SDK
  • Connecting Third-party Systems
  • crossConnect for External Editing
  • Implementation
  • Across XLIFF format
  • Across XLIFF - import, export and segmentation
  • 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

Across XLIFF - import, export and segmentation

Import algorithm

  • The Across XLIFF import algorithm works as follows:
  • A task will be identified, matching the Across XLIFF document based on src-lang and trg-lang attributes of the <file> element .
  • For each <trans-unit> not marked with the translate="no" attribute, the algorithm compares the content of the <target> element with the target content of the paragraph stored in Across (Text, Format ranges, Elements).
    If content was changed, the XLIFF content is read and stored to Across. The paragraph is considered as changed.
    Check
    What happens in Across
    The flag Pre-translated External appears in states-flags.
    Pre-translated External and Pre-translated are set for that paragraph.
    The paragraph is considered as changed.
    Import of external comments (analysisResult element).
    The paragraph is considered as changed and the comment will be displayed in crossDesk.
    Source and/or target segmentation is changed (see the segmentation rules below)
    The XLIFF segmentation is applied to Across source/target paragraphs.
    XLIFF segmentation is applied to Across source/target paragraphs.
  • If a paragraph in Across is considered as changed, its state is set to default in-progress state. A record is added to the Across change history, considering the Enhanced logging setting.

Export

Just like the import, the export is consistent to the main workflows of Across.

The translate="no" attribute is taken from the current state of a task. Therefore, if a task is in read-only state or paragraphs are protected and cannot be changed or a paragraph is read-only, this cannot be changed with external editing. This means: Everything that cannot be edited in Across in a regular task is also not editable in the exported XLIFF, i.e. is assigned the attribute translate="no".

Example: A translation task must be finished before the correction task can be exported to XLIFF correctly.

If there is the need to have  paragraphs editable for external editing, you could add an additional step to the workflow where the corresponding XLIFF criteria would be met. For example: previous task finished, exporting task not finished, and all paragraphs that should be edited externally are not in final status.

Segmentation rules

There are several rules for the segmentation.

Tip

The general expectation for an XLIFF import is, that only the <trans-unit>, <target> and <seg-source> elements are changed by the external tool. All other content should be unchanged.

  • To change the source segmentation, move segment borders in the <seg-source> element.
  • Tip

    Segment borders are <mrk mtype="seg"> and </mrk> elements.

  • Ensure that <seg-source> textual content is equal to <source> textual content. Segment borders are calculated based on the <seg-source> content but are applied to the <source> content.
  • To change the target segmentation you need to set Segment borders directly in the <target> element.
  • It's advised to keep the same number of source and target segments.
  • It's allowed to have fewer target segments than source segments.
  • It's not allowed to have more target segments than source segments. This is prohibited in XLIFF.
  • Across will perform automatic segmentation for not marked text.
  • Across always treats the first (by order in the XLIFF file) target segment as a translation of the first source segment, the second target segment as translation of the second source segment, and so on. The mid attribute of the <mrk mtype="seg"> element is ignored during import.
  • Across exports the mid attribute of the <mrk mtype="seg"> element, but ignores the mid attribute during import, because source/target segments in Across are related by order in the list of segments from the beginning of the text to the end.
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