### XLIFF 2.2 with ITS Annotations Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-extended-v2.2-csd02-part2.html

This example demonstrates a basic XLIFF 2.2 file structure with ITS annotations for localization quality issues and provenance records.

```xml
<xliff version="2.2" xmlns="urn:oasis:names:tc:xliff:document:2.2"
    srcLang="en" trgLang="fr"
    xmlns:its="http://www.w3.org/2005/11/its"
    its:version="2.0"
    xmlns:itsm="urn:oasis:names:tc:xliff:itsm:2.1">
  <!-- Each unit in the file element shows one ITS data category. -->
  <!-- The its:annotatorsRef attribute inherits through the whole file
      but is only relevant for some elements-->
  <file id="f1" 
        its:annotatorsRef="allowed-characters|http://example.com/myAllowedCharactersAnnotationTool
        terminology|http://example.com/mytermTool
        localization-quality-issue|http://example.com/anotherQualityChecker">
    <unit id="u1">
      <its:locQualityIssues xml:id="lqi1">
        <its:locQualityIssue locQualityIssueType="misspelling"
            locQualityIssueComment="'c'es' is unknown. Could be 'c'est'"
            locQualityIssueSeverity="50"/>
        <its:locQualityIssue locQualityIssueType="grammar"
            locQualityIssueComment="Sentence is not capitalized"
            locQualityIssueSeverity="30"/>
      </its:locQualityIssues>
      <its:provenanceRecords xml:id="prov1">
        <its:provenanceRecord revPerson="Franta Kocourek"
            revOrg="Kocourkov s.r.o."/>
        <its:provenanceRecord person="Honza Novák"
            org="Překlady Novák, sro" tool="GreatCATTool"/>
        <its:provenanceRecord tool="Microsoft Hub"/>
      </its:provenanceRecords>
      <its:provenanceRecords xml:id="prov2">
        <its:provenanceRecord revPerson="Květoň Zřídkaveselý"
            revOrg="CoolCopy"/>
        <its:provenanceRecord revTool="ACME QA Checker"
            revOrg="CoolCopy"/>
        <its:provenanceRecord revPerson="Franta Kocourek"
            revOrg="Kocourkov s.r.o."/>
        <its:provenanceRecord person="Honza Novák"
            org="Preklady Novák, sro" tool="GreatCATTool"/>
        <its:provenanceRecord tool="Microsoft Hub"/>
      </its:provenanceRecords>
      <notes>
        <note id="1" priority="1">Check with terminology engineer
            </note>
      </notes>

      <!-- Example for allowed characters data category -->

      <segment>
        <source>
          <mrk id="m1" type="its:generic"
              its:allowedCharacters="\[a-ZA-Z\]">Text</mrk>
        </source>
      </segment>

      <!-- Example for domain data category -->

      <segment>
        <source>Text in the domain domain1</source>
      </segment>

      <!-- Example for locale filter data category -->

      <segment>
        <source>Text <pc id="2"><mrk id="m2" type="its:generic"
            its:localeFilterList="fr" its:localeFilterType="exclude">
            text</mrk></pc></source>
      </segment>

      <!-- Example for localization quality issue data category. The
          standoff information in its:locQualityIssues has the
          annotatorsRef information from this element: <mrk id="m1" 
          type="its:generic" its:locQualityIssuesRef="#its=lqi1"
          its:annotatorsRef="localization-quality-issue|http://example.com/myQualityChecker">. 
      -->

      <segment>
        <source>This is the content</source>
        <target>
          <mrk id="m3" type="its:generic" its:locQualityIssuesRef="#its=lqi1"
           its:annotatorsRef="localization-quality-issue|http://qa.com/Checker">
             c'esle contenu</mrk>
        </target>
      </segment>

      <!-- Example for localization quality rating data category -->

      <segment>
        <source>Some text and a term</source>
        <target>Du texte et un <mrk id="m4" type="its:generic"
            its:locQualityRatingVote="37"
            its:locQualityRatingVoteThreshold="15"
            its:locQualityRatingProfileRef="http://example.org/qaModel
                /v13">terme</mrk></target>
      </segment>

      <!-- Example for text analytics data category -->

      <segment>
        <source>
          <mrk id="m5" type="its:generic"
              its:taClassRef="http://nerd.eurecom.fr/ontology#Place"
              its:taIdentRef="http://dbpedia.org/resource/Arizona">
              Arizona</mrk>
        </source>
      </segment>

      <!-- Example for terminology data category, expressed via native 
           XLIFF markup -->

      <segment>
        <source>This is a <mrk id="m6" type="comment" ref="#n=1">
            motherboard</mrk>.</source>
      </segment>

      <!-- Example for terminology data category, expressed via native XLIFF 
          markup, but with its:termConfidence attribute -->

      <segment>
        <source>Text with a <pc id="3"><mrk id="m7" type="term"
            ref="http://en.wikipedia.org/wiki/Terminology"
            its:termConfidence="0.9">term</mrk></pc>.</source>
      </segment>

      <!-- Example for language information data category -->

      <segment>
        <source>Span of text <pc id="4"><mrk id="m8" itsm:lang="fr"
            type="its:generic">en français</mrk></pc>.</source>
      </segment>

    </unit>
  </file>
</xliff>
```

--------------------------------

### XLIFF 2.2 dataRefStart and dataRefEnd Attributes Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Illustrates the use of 'dataRefStart' and 'dataRefEnd' attributes to reference original data for the start and end markers of an inline element.

```xml
<unit id="1">
  <originalData>
    <data id="d1">&lt;EM></data>
    <data id="d2">&lt;/EM></data>
  </originalData>
  <segment>
    <source><pc id="1" dataRefStart="d1" dataRefEnd="d2">
        Efficiency</pc> is the operative word here.</source>
    <target><pc id="1" dataRefStart="d1" dataRefEnd="d2">
        Efficacité</pc> est le mot clé ici.</target>
  </segment>
</unit>
```

--------------------------------

### XLIFF Rule: String Must Start With Specific Value

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-extended-v2.2-csd02-part2.html

Use the `startsWith` attribute to enforce that the target text begins with a specific string. This example validates that the target starts with '*'.

```xml
<unit id="1">
  <val:validation>
    <val:rule startsWith="*" />
  </val:validation>
  <segment id="1">
    <source>*Choose an option in the online store.</source>
    <target>*Escolha uma opção na loja online.</target>
  </segment>
</unit>
```

--------------------------------

### Using Experimental Website Stylesheet

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/docbook/xsl/RELEASE-NOTES.html

Demonstrates how to process Website documents using the experimental tabular.xsl driver file from the DocBook XSL package.

```text
http://docbook.sourceforge.net/release/xsl/current/website/tabular.xsl
```

--------------------------------

### XLIFF 2.2 Spanning Original Code Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Demonstrates the usage of the 'sc' element to mark the start of a spanning original code segment within an XLIFF unit. This example shows how 'sc' and 'ec' elements are used to enclose text that represents a formatted code element.

```xml
<unit id="1">
  <segment>
    <source><sc id="1" type="fmt" subType="xlf:b"/>
        First sentence. </source>
  </segment>
  <segment>
    <source>Second sentence.<ec startRef="1" type="fmt"
        subType="xlf:b"/></source>
  </segment>
</unit>
```

--------------------------------

### Example of pc element with dataRef

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Demonstrates the usage of the <pc> element for spanning original code, referencing data using dataRefStart and dataRefEnd attributes.

```xml
<unit id="1">
  <originalData>
    <data id="1">&lt;B&gt;</data>
    <data id="2">&lt;/B&gt;</data>
  </originalData>
  <segment>
    <source><pc id="1" dataRefStart="1" dataRefEnd="2">Important</pc>
      text</source>
  </segment>
</unit>
```

--------------------------------

### XLIFF 2.2 Isolated Attribute Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Demonstrates the use of the 'isolated' attribute on <sc> elements to indicate when start or end markers are not in the same <unit> as their corresponding codes.

```xml
<file id="f2" xmlns:abc="urn:abc">
  <unit id="1">
    <mtc:matches>
      <mtc:match id="tc01" ref="seg2">
        <source><sc id="1" isolated="yes"/>Warning:</source>
        <target><sc id="1" isolated="yes"/>Attention :</target>
      </mtc:match>
    </mtc:matches>
    <segment id="seg2">
      <source><pc id="1">Warning: File not found.</pc></source>
    </segment>
  </unit>
</file>
```

--------------------------------

### Importing and Including New Indexing Stylesheet

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/docbook/xsl/RELEASE-NOTES.txt

This example shows how to import a base stylesheet and include the new indexing stylesheet in a customization layer to enable the alternative indexing mechanism with better internationalization support.

```XSLT
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                    version="1.0">

    <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl"/>
    <xsl:include href="http://docbook.sourceforge.net/release/xsl/current/fo/autoidx-ng.xsl"/>

</xsl:stylesheet>
```

--------------------------------

### Term Annotation Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Demonstrates how to use the 'term' annotation to mark a specific term within the source content and associate a reference to it.

```XML
<file id="f-t_a">
  <unit id="1">
    <segment>
      <source>He is my <mrk id="m1" type="term"
          ref="http://dbpedia.org/page/Doppelgänger">
          doppelgänger</mrk>. </source>
    </segment>
  </unit>
</file>
```

--------------------------------

### XLIFF 2.2 Unit with Source and Inline Codes

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Example demonstrating the use of <sc> (start code) and <ec> (end code) elements within a <source> element to represent inline formatting like bold and italics. The 'dataRef' attribute links to the original data.

```xml
<unit id="1">
  <originalData>
    <data id="d1">\b </data>
    <data id="d2">\i </data>
    <data id="d3">\b0 </data>
    <data id="d4">\i0 </data>
  </originalData>
  <segment>
    <source>Text in <sc id="1" dataRef="d1"/>bold <sc id="2"
        dataRef="d2"/> and<ec startRef="1" dataRef="d3"/>
         italics<ec startRef="2" dataRef="d4"/>. </source>
  </segment>
</unit>
```

--------------------------------

### Orphan Start Marker of Spanning Code in XLIFF

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-extended-v2.2-csd02-part2.html

Represents an orphaned start marker of a spanning code in XLIFF. This indicates that the start marker exists without a corresponding end marker within the same context.

```xml
<sc id='1' isolated='yes'/>
```

--------------------------------

### Inline Simplelist Output Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/docbook/xsl/RELEASE-NOTES.html

Illustrates the expected output for an inline simplelist with a generated choice separator, as processed for English.

```text
> Choose from ONE and only ONE of the following choices: A, B, or C.
```

--------------------------------

### Example: Extracting Domain at Structural Levels

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-extended-v2.2-csd01-part2.html

Demonstrates how the Domain data category can be extracted at structural levels in an HTML document and represented in an XLIFF extraction.

```html
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>Data Category: Domain</title>
    <script type="application/its+xml">
      <its:rules xmlns:its="[http://www.w3.org/2005/11/its](http://www.w3.org/2005/11/its)" version="2.0"
          xmlns:h="[http://www.w3.org/1999/xhtml](http://www.w3.org/1999/xhtml)">
        <its:domainRule selector="//h:*[@class='dom1']"
            domainPointer="./@class" domainMapping="dom1 domain1" />
      </its:rules>
    </script>
  </head>
  <body>
    <p class="dom1">Text in the domain domain1</p>
  </body>
</html>

```

--------------------------------

### XLIFF 2.2 startRef Attribute Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

Illustrates the use of the 'startRef' attribute in <ec> elements to link them to their corresponding <sc> elements, defining text formatting.

```xml
<unit id="1">
  <segment>
    <source><sc id="1"/>Bold, <sc id="2"/>both
        <ec startRef="1"/>, italics<ec startRef="2"/></source>
  </segment>
</unit>
```

--------------------------------

### XLIFF 2.2 Document Example

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-core-v2.2-csd03-part1.html

An example of an XLIFF 2.2 document containing a file with a unit, segment, source, and target. This structure is typical for localization workflows.

```xml
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.2" version="2.2"
    srcLang="en" trgLang="fr">
  <file id="f1">
    <notes>
      <note id="n1">note for file.</note>
    </notes>
    <unit id="u1">
      <my:elem xmlns:my="myNamespaceURI" id="x1">data</my:elem>
      <notes>
        <note id="n1">note for unit</note>
      </notes>
      <segment id="s1">
        <source><pc id="1">Hello <mrk id="m1" type="term">World</mrk>!</pc>
            </source>
        <target><pc id="1">Bonjour le <mrk id="m1" type="term">Monde</mrk>
            ! </pc></target>
      </segment>
    </unit>
  </file>
</xliff>
```

--------------------------------

### Running DocBook XSL with Saxon and Custom Options

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/docbook/xsl/RELEASE-NOTES.txt

This command demonstrates how to run DocBook XSL using Saxon with specific Java system properties for encoding, XML parsers, and transformers. It's useful for complex transformations requiring custom configurations.

```bash
java \
  -Dencoding.windows-1252=com.nwalsh.saxon.Windows1252 \
  -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl \
  -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl \
  -Djavax.xml.transform.TransformerFactory=com.icl.saxon.TransformerFactoryImpl \
  com.icl.saxon.StyleSheet \
  -x org.apache.xml.resolver.tools.ResolvingXMLReader \
  -y org.apache.xml.resolver.tools.ResolvingXMLReader \
  -r org.apache.xml.resolver.tools.CatalogResolver \
  mydoc.xml mystylesheet.xsl
```

--------------------------------

### Start Marker of Spanning Code in XLIFF

Source: https://github.com/oasis-tcs/xliff-xliff-22/blob/master/xliff-22/xliff-extended-v2.2-csd02-part2.html

Represents the start marker of a spanning code in XLIFF. This is used when a code begins within a segment but may end in another.

```xml
<sc id='1'/>
```