• 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
  • Analysis Results
  • 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

Analysis Results

  • In order not to lose any valuable information from external quality assurance, Across extended the XLIFF format as follows:
  • The extension has a root element analysisResults which contains a collection of analysisResult entries.
  • Each analysisResult entry consists of two parts:
    1. errorRanges - original source and target content with special markup of ranges which are referenced in some found error(s).
    2. Collection of errorInfos - errors found by QA tools.

analysisResult Element

Description
The root element of the structure.
<analysisResult> 
    Content: (errorRanges?, errorInfos) 
</analysisResult>
Parent element
trans-unit
Child elements
errorRanges, errorInfos
Attributes
none
Number of occurences
One ore more

errorRanges Element

Description
Information about ranges in source and/or target content where errors were found.
<errorRanges> 
    Content: (sourceContent, targetContent) 
</errorRanges>
Parent element
analysisResult
Child elements
sourceContent, targetContent
Attributes
none
Number of occurences
none or once

errorInfos Element

Description
Collection of errors found for a paragraph.
<errorInfos> 
    Content: (errorInfo*) 
</errorInfos>
Parent element
analysisResult
Child elements
errorInfo
Attributes
none
Number of occurences
Once

sourceContent Element

Description
Original source content with special markup of error ranges.
<sourceContent> 
    Content: (nonEmptyString | errorRangeStart | errorRangeEnd | Any )* 
</sourceContent>
Parent element
errorRanges
Child elements
errorRangeStart , errorRangeEnd, any valid XML element
Attributes
none
Number of occurences
none or once

targetContent Element

Description
Original target content with special markup of error ranges.
<targetContent> 
    Content: (nonEmptyString | errorRangeStart | errorRangeEnd | Any )* 
</targetContent>
Parent element
errorRanges
Child elements
errorRangeStart, errorRangeEnd, any valid XML element
Attributes
none
Number of occurences
none or once

errorRangeStart Element

Description
Marks the start position of an error range, has a unique id value within the scope of the errorRanges section.
<errorRangeStart 
 id: index of error range > 
    Content: ( empty ) 
</errorRangeStart >
Parent element
sourceContent, targetContent
Child elements
none
Attributes
id - identifier of an error range, unique in scope of errorRanges.
Number of occurences
any

errorRangeEnd element

Description
Marks the end position of an error range, has a unique id value within the scope of the errorRanges section.
<errorRangeEnd 
 id: index of error range > 
    Content: ( empty ) 
</errorRangeEnd >
Parent element
sourceContent, targetContent
Child elements
none
Attributes
id - identifier of an error range, unique in scope of errorRanges.
Number of occurences
any

errorInfo Element

Description
Description of an error.
<errorInfo> 
    Content: (rangeId? | description | explanation? | examples? | proposals? )* 
</errorInfo>
Parent element
errorInfos
Child elements
rangeId, description, proposals
Attributes
none
Number of occurences
any

rangeId element

Description
Reference to a range defined in sourceContent and/or targetContent which the errorInfo is related to.
<rangeId > 
    Content: ( integer ) 
</rangeId >
Parent element
errorInfo
Child elements
none
Attributes
none
Number of occurences
none or once

description Element

Description
Detailed description of an error.
<description> 
    Content: ( errorCode? | type | title? | instruction | explanation | examples ) 
</description>
Parent element
errorInfo
Child elements
type, errorCode, title, instruction, explanation, examples
Attributes
none
Number of occurences
once

type Element

Description
Type of an error, e.g. grammar, spelling, etc.
<type> 
    Content: ( nonEmptyString ) 
</type>
Parent element
description
Child elements
none
Attributes
none
Number of occurences
once

errorCode Element

Description
Error code provided by a tool.
<errorCode> 
    Content: ( nonEmptyString ) 
</errorCode>
Parent element
description
Child elements
none
Attributes
none
Number of occurences
none or once

title Element

Description
Title of an error description.
<explanation> 
    Content: ( nonEmptyString | br | b | i | u | H1 | H2 | H3 )* 
</explanation>
Parent element
description
Child elements
For details see: Rich Formatting Element
Attributes
none
Number of occurences
none or once

instruction Element

Description
Description of an error.
<instruction> 
    Content: ( nonEmptyString | br | b | i | u | H1 | H2 | H3 )* 
</instruction>
Parent element
description
Child elements
For details see: Rich Formatting Element
Attributes
none
Number of occurences
none or once

explanation Element

Description
Detailed explanation of an error.
<explanation> 
    Content: ( nonEmptyString | br | b | i | u | s | H1 | H2 | H3 )* 
</explanation>
Parent element
description
Child elements
For details see: Rich Formatting Element
Attributes
none
Number of occurences
none or once

examples Element

Description
Collection of examples.
<examples> 
    Content: ( example* ) 
</examples>
Parent element
description
Child elements
example
Attributes
none
Number of occurences
none or once

example Element

Description
Example.
<example> 
    Content: ( nonEmptyString | br | b | i | u | s | H1 | H2 | H3 )* 
</example>
Parent element
examples
Child elements
For details see: Rich Formatting Element
Attributes
none
Number of occurences
any

proposals Element

Description
Collection of proposals.
<proposals> 
    Content: ( proposal* ) 
</proposals>
Parent element
errorInfo
Child elements
proposal
Attributes
none
Number of occurences
none or once

proposal Element

Description
Proposal how to correct an error.
<proposals> 
    Content: ( text, extraInfo ) 
</proposals>
Parent element
proposals
Child elements
text, extraInfo
Attributes
none
Number of occurences
any

text Element

Description
Text of proposed replacement.
<text> 
    Content: ( nonEmptyString ) 
</text>
Parent element
proposal
Child elements
none
Attributes
none
Number of occurences
once

extraInfo Element

Description
Additional information to a proposal.
<extraInfo> 
    Content: ( nonEmptyString | br | b | i | u | s | H1 | H2 | H3 )* 
</extraInfo>
Parent element
proposal
Child elements
For details see: Rich Formatting Element
Attributes
none
Number of occurences
none or once

Rich Formatting Element

Description
Any element whose content can contain rich formatting markup.
<RICH_FMT_ELEMEMT> 
    Content: ( nonEmptyString | br | b | i | u | s | h1 | h2 | h3 )* 
</RICH_FMT_ELEMEMT>
Child elements
title1, title2, title3, br, b, i, u, s

Description of available formatting markup elements

Name
Description
h1
First level header
h2
Second level header
h3
Third level header
br
Line break (self-closed)
b
Bold
i
Italic
u
Underline
s
Strikethrough

XML structure example

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