ITS Test Implementation

This page allows you to test some of the XML Internationalization Tag Set (ITS) rules. See the How to Use This? section for for information. Last update: Feb-15-2007, 08:45am MST.

IMPORTANT: This is a BETA implementation of the Okapi XML Filter and its support for ITS. You may (will!) experience problems with some files.

Enter the XML source (with ITS markup if needed):

<doc attr="Attributes are not translatable by default"> <text>Elements are translatable by default</text> </doc>

Type of test:

What is This?

This page is a test implementation of the W3C Internationalization Tag Set, a vocabulary to provide internationalization features to XML documents.

See the W3C ITS Working Group for more information about the Internationalization Tag Set.

Feedback or questions?

Bug, crash, runtime error (anything to do with the application itself): Send an email.
ITS-related issue, suggestion, comments: ITS Public Mailing List.

How to Use This?

Enter you XML code in the input area (or copy one of the pre-defined examples from the list), then generate one of the outputs:

XLIFF Output - Click Extract to XLIFF. This will generate an XLIFF document where only the translatable text is extracted. The way the text is broken down into different <trans-unit> depends on the <its:withinTextRule> rules. Non translatable text embedded within translatable text is represented inside <ph> elements.
Pseudo-Translation Output - Click Pseudo-Translate. This will generate an XML document identical to the original one, but where all translatable text is replaced: all letters by Xs (same case as the original letter), digits by Ns, all other characters are left alone. Any no-translatable text remains unchanged. The layout of tags in the resulting XML document may vary a bit from the source document (since the document is read then re-written).
Test Output - Select data category you want to test from the Type of test listbox, then click Test Results. This will generate an XML document where each element and attribute in the original document is listed with the ITS information that is applied to it. This format is used by the ITS Working Group to test compatibility between ITS processors, and conformance with the ITS processing expectations.
Terms Output - Click Terms. This will generate a tab-delimited file with the list of all terms in the original document and, if available, their corresponding information. The <its:termRule> rules and the corresponding local attributes determine what are terms. The header line indicates the number of terms extracted.

Note: The rules implemented in this tool here should be (more or less) the reflection of the current work of the ITS WG. They may not be the same as in the latest published draft, and may reflect some undergoing experimental changes. This application allows you to test only global and local rules within the document (no external rules or linked rules).

ITS Rules Summary

Global rules are specified in <its:rules> elements. You can have several <its:rules> elements per document, but they are evaluated as one set, in the order they appear in the document. Their location in the document (at the top, at the bottom) has no bearing to their effect as all global rules are expressed from the root of the document.

Use the xmlns attribute to specify any namespace to use in the XPath expressions specified in the ITS rules.

Global rules are used to specify mapping of internationalization features of the host format to ITS, or to apply ITS features to selections of the host format.

Local ITS markup is used to override any global rule for a give element inside the document. You can also use the <its:span> element to delimit portions of text if the host format does not have an equivalent element.

For more details on any ITS rules always refer to the latest ITS Specification document, or to the latest Editor's copy of the document and to the ITS Public Mailing List to see what may be under discussion.

Data Category: Translate

Global: SUPPORTED

<its:translateRule translate="yes|no"
 selector="AbsoluteXPathExpression" />

Local: SUPPORTED

its:translate="yes|no"

Data Category: Localization Note

Global: SUPPORTED

<its:locNoteRule selector="AbsoluteXPathExpression"
 locNoteType="description|alert" (optional)>
 <its:locNote>Text of the note</its:locNote>
</its:locNoteRule>

Local: SUPPORTED

its:locNote="Text of the note"
its:locNoteType="description|alert" (optional)

Global: SUPPORTED

<its:locNoteRule selector="AbsoluteXPathExpression"
 locNoteType="description|alert" (optional)>
 locNotePointer="RelativeXPathExpression" />

Global: SUPPORTED

<its:locNoteRule selector="AbsoluteXPathExpression"
 locNoteType="description|alert" (optional)>
 locNoteRef="SomeURI" />

Local: SUPPORTED


its:locNoteRef="SomeURI"
its:locNoteType="description|alert" (optional)

Global: SUPPORTED

<its:locNoteRule selector="AbsoluteXPathExpression"
 locNoteType="description|alert" (optional)>
 locNoteRefPointer="RelativeXPathExpression" />

Data Category: Terminology

Global: SUPPORTED

<its:termRule selector="AbsoluteXPathExpression"
 termInfoRef="SomeURI" (optional) />

Local: SUPPORTED

its:term="yes"
its:termInfoRef="SomeURI" (optional)

Global: SUPPORTED

<its:termRule selector="AbsoluteXPathExpression"
 termInfoRefPointer="RelativeXPathExpression" />

Global: SUPPORTED

<its:termRule selector="AbsoluteXPathExpression"
 termInfoPointer="RelativeXPathExpression" />

Data Category: Elements Within Text

Global: SUPPORTED

<its:withinTextRule selector="AbsoluteXPathExpression"
 withinText="yes|no|nested" />

Extensions

This application supports a few extensions to demonstrate how you can add features to ITS.

The extension namespace is "okapi-framework:its-extensions". You must declare it along with the ITS namespace to use the extensions. there are two extensions:

Target Location

This attribute, placed in a <its:translateRule> element, allows you to specify where the translated text should go. This is useful for XML formats that are designed to work with source and target text. The value is an XPath expression relative to the location pointed by the selector attribute.

<its:translateRule translate="yes|no"
 selector="AbsoluteXPathExpression"
 itsext:targetPointer="RelativeXPathExpression"/>

Identifier Pointer

This attribute, placed in a <its:translateRule> element, allows you to associate specify that a given element or attribute is the identifier for the selected item. This is useful for example when extracting data to XLIFF to map the resname attribute of XLIFF to the identifier of the extracted item. The value is an XPath expression relative to the location pointed by the selector attribute.

<its:translateRule translate="yes|no"
 selector="AbsoluteXPathExpression"
 itsext:idPointer="RelativeXPathExpression"/>