Converted the XLIFF 1.2 Spec to Docbook

[<bryan.s.schnabel@tektronix.com>]

Hello all,

 

Here's the XLIFF 1.2 Specification transformed into Docbook (fulfilling one of my action items). It's currently at version x.x (instead of 1.2 or 2.0).  I have not yet put it through the transforms to XHTML or PDF. But I assume it should transform just fine.

 

I also mentioned that I would test it in Open Source XML tools. So far, I can say it works just fine in Serna Free Open Source XML Editor (http://www.syntext.com/products/serna-free/), Mac, Linux, and Windows.

 

Please feel free to test it. Once we find it satisfactory, let's ask Rodolfo to post it in its proper OASIS holding spot, and use this format going forward (as we approved by ballot in TC).

 

Thanks,

 

Bryan Schnabel
Content Management Architect
Phone: 503.627.5282
www.tektronix.com

  

 

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";>
<article status="&amp;standard;">
<articleinfo>
<title>XLIFF Version 1.2+</title>
<releaseinfo role="cvs"><?nospell-start?>$Id: XLIFF-core.xml,v 1.2
2008-1-Feb admin Exp $<?nospell-end?> </releaseinfo>
<productname>OASIS Standard</productname>
<productnumber>1.2+</productnumber>
<releaseinfo role="OASIS-specification-this-authoritative">http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html</releaseinfo>
<releaseinfo role="OASIS-specification-this">http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.pdf</releaseinfo>
<releaseinfo role="OASIS-specification-previous">http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html</releaseinfo>
<releaseinfo role="OASIS-specification-previous">http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.pdf</releaseinfo>
<releaseinfo role="OASIS-specification-previous"> </releaseinfo>
<releaseinfo role="OASIS-specification-latest-authoritative">http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html</releaseinfo>
<releaseinfo role="OASIS-specification-latest">http://docs.oasis-open.org/xliff/xliff-core/xliff-core.pdf</releaseinfo>
<?nospell-end?>
<releaseinfo role="committee"> <ulink
url="http://www.oasis-open.org/committees/";>OASIS XLIFF TC</ulink
> </releaseinfo>
<authorgroup>
<editor>
<!-- this is where the Editor(s) is cited -->
<firstname>Rodolfo</firstname><surname>Raya</surname>
<affiliation><orgname>Maxprograms</orgname>
<address> <email>rmraya@maxprograms.com</email> </address>
</affiliation>
</editor>
<othercredit>
<!-- this is where the Chair(s) is cited -->
<firstname>Bryan</firstname><surname>Schnabel</surname>
<affiliation><orgname>Tektronix</orgname>
<address> <email>bryan.s.schnabel@tektronix.com</email> </address>
</affiliation>
</othercredit>
</authorgroup>
<pubdate>1 February 2011</pubdate>
<copyright><year>2010</year><holder>OASIS Open, Inc. All Rights Reserved.</holder>
</copyright>
<legalnotice role="related">
<title>Related Work</title>
<para>This specification replaces or supersedes:</para>
<itemizedlist spacing="compact">
<listitem><para>XLIFF 1.2 OASIS Standard</para></listitem>
</itemizedlist>
</legalnotice>
<legalnotice role="namespaces">
<title>Declared XML Namespaces</title>
<para> <ulink url="urn:oasis:names:tc:xliff:document:1.2+">urn:oasis:names:tc:xliff:document:1.2+</ulink
> </para></legalnotice>
<abstract>
<para>This document defines the XML Localization Interchange File
Format (XLIFF). The purpose of this vocabulary is to store localizable
data and carry it from one step of the localization process to the
other, while allowing interoperability between tools.</para>
</abstract>
<legalnotice role="status">
<title>Status</title>
<para>This document was last revised or approved by the XLIFF TC on
the above date. The level of approval is also listed above. Check
the current location noted above for possible later revisions of this
document. This document is updated periodically on no particular schedule.</para>
<para>Technical Committee members should send comments on this specification
to the Technical Committee's email list. Others should send comments
to the Technical Committee by using the "Send A Comment" button on
the Technical Committee' s web page at www.oasis-open.org/committees/xliff</para>
<para>Technical Committee members should send comments on this specification
to the Technical Committee's email list. Others should send comments
to the Technical Committee by using the "Send A Comment" button on
the Technical Committee's web page at <ulink
url="http://www.oasis-open.org/committees/xliff";>http://www.oasis-open.org/committees/xliff</ulink
>.</para>
<para>For information on whether any patents have been disclosed that
may be essential to implementing this specification, and any offers
of patent licensing terms, please refer to the Intellectual Property
Rights section of the Technical Committee web page (<ulink
url="http://www.oasis-open.org/committees/xliffipr.php";>http://www.oasis-open.org/committees/xliffipr.php</ulink
>).</para>
</legalnotice>
<legalnotice role="notices">
<title>Notices</title>
<para>Copyright &#xa9; OASIS&#xae; Open 2010. All Rights Reserved. </para>
<para>All capitalized terms in the following text have the meanings
assigned to them in the OASIS Intellectual Property Rights Policy
(the "OASIS IPR Policy"). The full Policy may be found at the OASIS
website.</para>
<para>This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise explain
it or assist in its implementation may be prepared, copied, published,
and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this section are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, including by removing the copyright
notice or references to OASIS, except as needed for the purpose of
developing any document or deliverable produced by an OASIS Technical
Committee (in which case the rules applicable to copyrights, as set
forth in the OASIS IPR Policy, must be followed) or as required to
translate it into languages other than English.</para>
<para>The limited permissions granted above are perpetual and will
not be revoked by OASIS or its successors or assigns.</para>
<para>This document and the information contained herein is provided
on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.</para>
<para>OASIS requests that any OASIS Party or any other party that
believes it has patent claims that would necessarily be infringed
by implementations of this OASIS Committee Specification or OASIS
Standard, to notify OASIS TC Administrator and provide an indication
of its willingness to grant patent licenses to such patent claims
in a manner consistent with the IPR Mode of the OASIS Technical Committee
that produced this specification.</para>
<para>OASIS invites any party to contact the OASIS TC Administrator
if it is aware of a claim of ownership of any patent claims that would
necessarily be infringed by implementations of this specification
by a patent holder that is not willing to provide a license to such
patent claims in a manner consistent with the IPR Mode of the OASIS
Technical Committee that produced this specification. OASIS may include
such claims on its website, but disclaims any obligation to do so.</para>
<para>OASIS takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this document
or the extent to which any license under such rights might or might
not be available; neither does it represent that it has made any effort
to identify any such rights. Information on OASIS' procedures with
respect to rights in any document or deliverable produced by an OASIS
Technical Committee can be found on the OASIS website. Copies of claims
of rights made available for publication and any assurances of licenses
to be made available, or the result of an attempt made to obtain a
general license or permission for the use of such proprietary rights
by implementers or users of this OASIS Committee Specification or
OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS
makes no representation that any information or list of intellectual
property rights will at any time be complete, or that any claims in
such list are, in fact, Essential Claims.</para>
<para>The name "OASIS" is a trademark of <ulink
url="http://www.oasis-open.org";>OASIS</ulink>, the owner and developer
of this specification, and should be used only to refer to the organization
and its official outputs. OASIS welcomes reference to, and implementation
and use of, specifications, while reserving the right to enforce its
marks against misleading uses. Please see <ulink
url="http://www.oasis-open.org/who/trademark.php";>http://www.oasis-open.org/who/trademark.php</ulink
> for above guidance.</para>
</legalnotice>
</articleinfo>
<section>
<title id="SectionIntroduction">Introduction</title>
<para>XLIFF is the XML Localization Interchange File Format designed
by a group of software providers, localization service providers,
and localization tools providers. It is intended to give any software
provider a single interchange file format that can be understood by
any localization provider. It is loosely based on the OpenTag version
1.2 specification and borrows from the TMX 1.2 specification. However,
it is different enough from either one to be its own format.</para>
<section>
<title id="Intro_Flavors">Transitional and Strict</title>
<para>XLIFF is specified in two "flavors". Indicate which of these
variants you are using by selecting the appropriate schema. The
schema may be specified in the XLIFF document itself or in an OASIS
catalog. The namespace is the same for both variants. Thus, if you
want to validate the document, the tool used knows which variant
you are using. Each variant has its own schema that defines which
elements and attributes are allowed in certain circumstances.</para>
<para>As newer versions of XLIFF are approved, sometimes changes
are made that render some elements, attributes or constructs in
older versions obsolete. Obsolete items are deprecated and should
not be used even though they are allowed. The XLIFF specification
details which items are deprecated and what new constructs to use.</para>
<itemizedlist>
<listitem id="transitional"><para> <emphasis>Transitional</emphasis
> - Applications that produce older versions of XLIFF may still
use deprecated items. Deprecated elements and attributes are allowed.
 Non-XLIFF items are validated only to ensure they are well-formed.
Use this variant to validate XLIFF documents that you read.</para>
<para> <code>xsi:schemaLocation='urn:oasis:names:tc:xliff:document:1.2
 xliff-core-1.2-transitional.xsd'</code> </para>
</listitem>
<listitem id="strict"><para> <emphasis>Strict</emphasis> - All
deprecated elements and attributes are not allowed. Obsolete items
from previous versions of XLIFF are deprecated and should not
be used when writing new XLIFF documents. In order for XLIFF 
 documents with extensions to validate, the parser MUST find the
 schema for namespaced elements and attributes, and elements and
 attributes MUST be valid. Use this variant to validate XLIFF 
 documents that you create.</para><para> <code>xsi:schemaLocation='urn:oasis:names:tc:xliff:document:1.2
 xliff-core-1.2-strict.xsd'</code> </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title id="SectionStructure">General Structure</title>
<para>XLIFF is an XML application, as such it begins with an XML
declaration. After the XML declaration comes the XLIFF document
itself, enclosed within the <link linkend="xliff"> <code
>&lt;xliff></code> </link> element. An XLIFF document
is composed of one or more sections, each enclosed within a <link
linkend="file"> <code>&lt;file></code> </link
> element. The <link linkend="file"> <code>&lt;file></code
> </link> element consists of a <link linkend="header"> 
 <code>&lt;header></code> </link> element, which
 contains metadata about the <link linkend="file"> <code
>&lt;file></code> </link> , and a <link linkend="body"> 
 <code>&lt;body></code> </link> element, which
contains the extracted translatable data from the <link linkend="file"
> <code>&lt;file></code> </link>. The translatable
data within <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> elements is organized into <link linkend="source"
> <code>&lt;source></code> </link> and <link
linkend="target"> <code>&lt;target></code> </link
> paired elements. These <link linkend="trans-unit"> 
 <code>&lt;trans-unit></code> </link> elements can be grouped
recursively in <link linkend="group"> <code>&lt;group></code
> </link> elements.</para>
<para>In addition, XLIFF provides the ability to maintain information
about the processing of the file via the <link linkend="phase"> 
 <code>&lt;phase></code> </link> element. Possible
 translations for a specific <link linkend="source"> <code
>&lt;source></code> </link> element can be generated from
any number of MT (Machine Translation) and CAT (Computer Assisted
Translation) systems and stored near the <link linkend="source"> 
 <code>&lt;source></code> </link> in <link
linkend="alt-trans"> <code>&lt;alt-trans></code> 
 </link> elements. Context for a <link linkend="source"> 
 <code>&lt;source></code> </link> that could be
used by a translator or a TM (Translation Memory) system is provided
by the <link linkend="context"> <code>&lt;context></code
> </link> element. Binary data can be made available via
the <link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link>, which may also be translated and contain an
associated <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> .</para>
<para>It is strongly recommended that content within the <code> <link
linkend="file">&lt;file></link> </code> element be uniformly
bilingual. In other words, each <code> <link linkend="source">&lt;source></link
> </code> and <code> <link linkend="target">&lt;target></link
> </code> element that is a child of <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> is of the
 same language as the source-language and target-language attributes
 of the <code> <link linkend="file">&lt;file></link> </code
> element, respectively. The <code> <link linkend="xml_lang">xml:lang</link
> </code> attribute should not be used in those elements. The
exception is that <code> <link linkend="source">&lt;source></link
> </code> and <code> <link linkend="target">&lt;target></link
> </code> elements that are children of <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> may contain
an <code> <link linkend="xml_lang">xml:lang</link> </code> attribute
 of a different language than that of the <code> <link
linkend="source-language">source-language</link> </code> and <code
> <link linkend="target-language">target-language</link> </code
> attributes of the <code> <link linkend="file">&lt;file></link
> </code> element.</para>
<programlisting> &lt;xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'> &lt;file original='hello.txt' source-language='en' target-language='fr' datatype='plaintext'> &lt;body> &lt;trans-unit id='hi'> &lt;source>Hello world&lt;/source> &lt;target>Bonjour le monde&lt;/target> &lt;alt-trans> <emphasis
>&lt;target xml:lang='es'>Hola mundo&lt;/target></emphasis> &lt;/alt-trans> &lt;/trans-unit> &lt;/body> &lt;/file> &lt;/xliff> </programlisting>
<para>The complete tree structure is available in <link linkend="AppTree"
>Appendix A</link>.</para>
<section>
<title id="Struct_Header">Header</title>
<para>The XLIFF <link linkend="header"> <code>&lt;header></code
> </link> contains metadata about the file and the localization
process. It contains the <link linkend="skl"> <code
>&lt;skl></code> </link>, <link linkend="phase-group"
> <code>&lt;phase-group></code> </link
>, <link linkend="glossary"> <code>&lt;glossary></code
> </link>, <link linkend="reference"> <code
>&lt;reference></code> </link>, <link linkend="count-group"
> <code>&lt;count-group></code> </link
>, <code> <link linkend="tool_elem">&lt;tool></link> </code>, <link
linkend="prop-group"> <code>&lt;prop-group></code> 
 </link>, and <link linkend="note"> <code
>&lt;note></code> </link> elements. The <link linkend="skl"
> <code>&lt;skl></code> </link> element
contains either a skeleton file of the file submitted for localization
or a hypertext link to that file.</para>
<para>The <link linkend="phase-group"> <code>&lt;phase-group></code
> </link> element contains information about each processing
phase used in localizing the file; references to these phases are
stored along with the translations. The <link linkend="glossary"
> <code>&lt;glossary></code> </link> and <link
linkend="reference"> <code>&lt;reference></code> 
 </link> elements may contain hypertext links to a glossary
and reference file, respectively, or the actual glossary and reference
data that can be used in the localization process.</para>
<para>The <link linkend="count-group"> <code>&lt;count-group></code
> </link> element is a grouping element of count information
of the entire file. The <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link> element (deprecated)
contains tool-specific information used in combining the data with
the skeleton file or storing the data in a repository. The <link
linkend="note"> <code>&lt;note></code> </link
> element contains instructions for the localization process. The <link
linkend="count-group"> <code>&lt;count-group></code
> </link>, <link linkend="prop-group"> <code
>&lt;prop-group></code> </link>, and <link linkend="note"
> <code>&lt;note></code> </link> elements
can also appear in the body of the file.</para>
</section>
<section>
<title id="Struct_Body">Body</title>
<para>The XLIFF <link linkend="body"> <code>&lt;body></code
> </link> contains the structure and the localizable
content from the file. It contains the <link linkend="group"> 
 <code>&lt;group></code> </link>, <link
linkend="trans-unit"> <code>&lt;trans-unit></code> 
 </link> and <link linkend="bin-unit"> <code
>&lt;bin-unit></code> </link> elements. The structure
is described using the <link linkend="group"> <code
>&lt;group></code> </link>, <link linkend="trans-unit"
> <code>&lt;trans-unit></code> </link>, <link
linkend="bin-unit"> <code>&lt;bin-unit></code> 
 </link> elements. The <link linkend="group"> 
 <code>&lt;group></code> </link> element is a general
 purpose structural element used in describing the hierarchy of the
 file; it can contain other <link linkend="group"> 
 <code>&lt;group></code> </link> elements as children
 as well as <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> and <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link> elements.</para>
<para>The <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> and <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link> elements contain 
 the translatable portions of the document. The <link
linkend="trans-unit"> <code>&lt;trans-unit></code> 
 </link> element contains the text to be translated, the
translations, and other related information. The <link
linkend="bin-unit"> <code>&lt;bin-unit></code> 
 </link> contains binary data that may or may not need to
be translated; it also can contain translated versions of the binary
object as well as other related information.</para>
<para>In the <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> element the text to be translated is contained
in a <link linkend="source"> <code>&lt;source></code
> </link> element. This element may contain inline elements
that either remove the codes from the source (<link linkend="g"
> <code>&lt;g></code> </link>, <link linkend="x"> 
 <code>&lt;x/></code> </link>, <link linkend="bx"> 
 <code>&lt;bx/></code> </link> , <link
linkend="ex"> <code>&lt;ex/></code> </link
>) or that mask off codes left inline (<link linkend="bpt"> <code
>&lt;bpt></code> </link>, <link linkend="ept"> <code
>&lt;ept></code> </link>, <link linkend="sub"> 
 <code>&lt;sub></code> </link> , <link linkend="it"
> <code>&lt;it></code> </link>, <link
linkend="ph"> <code>&lt;ph></code> </link
>). The translated text is contained in a <link linkend="target"
> <code>&lt;target></code> </link> element
that has the same inline codes available to it as does the <link
linkend="source"> <code>&lt;source></code> 
 </link> element. Translation matches generated by a TM or MT
or entered by a translator may be provided in an <link
linkend="alt-trans"> <code>&lt;alt-trans></code> 
 </link> element, which also contains the <link
linkend="source"> <code>&lt;source></code> 
 </link> and <link linkend="target"> <code>&lt;target></code
> </link> elements.</para>
<para>At every structural level contextual information for the localization
process can be provided by the <link linkend="context-group"> 
 <code>&lt;context-group></code> </link> named
 group element, count information by the <link linkend="count-group"
> <code>&lt;count-group></code> </link
> named group element, and tool-specific information by the <link
linkend="prop-group"> <code>&lt;prop-group></code> 
 </link> named group element (deprecated).</para>
</section>
<section>
<title id="Struct_NamedGroups">Named Groups</title>
<para>XLIFF allows grouping of certain elements into named groups.
A named group is simply a grouping element with a name attribute.
These named groups can be interspersed throughout the file with
information designed for specific purposes. Using XML processing
instructions different actions can be performed with specific named
groups. The named group elements are <link linkend="context-group"
> <code>&lt;context-group></code> </link
>, <link linkend="count-group"> <code>&lt;count-group></code
> </link> and <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link> (deprecated).</para>
<para>The <link linkend="count-group"> <code>&lt;count-group></code
> </link> element contains counts of words, translations,
dialogs, or anything else that may need to be counted in the file.
A different named group could be stored by the client, translator,
reviewer, and localization engineer. Processing instructions could
inform a system which of these <link linkend="count-group"> 
 <code>&lt;count-group></code> </link> to update
 during the localization process.</para>
<para>The <link linkend="prop-group"> <code>&lt;prop-group></code
> </link> element contains tool specific data that can
be used in creating the translated file, storing the translations,
and any other specific task. Processing instructions can indicate
to the tools which named <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link> to use when
updating the repository or combining the localized data with the
skeleton file to create a translated file. Note that the <link
linkend="prop-group"> <code>&lt;prop-group></code> 
 </link> has been deprecated since version 1.1.</para>
</section>
<section>
<title id="Struct_InLine">Inline Elements</title>
<para>The content of the <code> <link linkend="source">&lt;source></link
> </code> and the <code> <link linkend="target">&lt;target></link
> </code> elements can include one or more inline elements (also
called "content markup"). Those elements are used to represent codes
that reside within the source or target text, for example the formatting
codes to mark a section of a sentence in bold.</para>
<para>There are three different types of inline elements:</para>
<orderedlist>
<listitem><para>Elements that have a content, and for which this content
is the actual native code of the original data (escaped for XML
if necessary). These elements are: <code> <link linkend="bpt">&lt;bpt></link
> </code>, <code> <link linkend="ept">&lt;ept></link> </code
>, <code> <link linkend="it">&lt;it></link> </code>, and <code
> <link linkend="ph">&lt;ph></link> </code> .</para></listitem>
<listitem><para>Elements that are empty and act as placeholders for
a native code that is either in the Skeleton file or generated
 automatically. These elements are:<code> <link linkend="g">&lt;g></link
> </code>, <code> <link linkend="bx">&lt;bx/></link> </code
>, <code> <link linkend="ex">&lt;ex/></link> </code> , and <code
> <link linkend="x">&lt;x/></link> </code>.</para></listitem>
<listitem><para>The <code> <link linkend="sub">&lt;sub></link> 
 </code> element, which can be inside <code> <link linkend="bpt"
>&lt;bpt></link> </code>, <code> <link linkend="ept">&lt;ept></link
> </code>, <code> <link linkend="it">&lt;it></link> </code
>, and <code> <link linkend="ph">&lt;ph></link> </code> to delimit
a translatable run of text within a native inline code, for example
the value of an <code>ALT</code> attribute in a <code>&lt;IMG></code
> element in HTML.</para></listitem>
</orderedlist>
<para>The first two types of inline elements can be classified into
three main categories depending on their function, and regardless
the method they use to hold the native codes:</para>
<para>A) Codes that either begin or end an instruction, and whose
beginning and ending functions both appear within a translation
unit. For example, an instruction to begin embolden for a range
of words which is then followed in the same translation unit by
an instruction to end bold formatting. The elements that can handle
such cases are: <code> <link linkend="bpt">&lt;bpt></link> </code
>, <code> <link linkend="ept">&lt;ept></link> </code>, <code> 
 <link linkend="g">&lt;g></link> </code>, <code> <link linkend="bx"
>&lt;bx/></link> </code>, and <code> <link linkend="ex">&lt;ex/></link
> </code> .</para>
<para>B) Codes that either begin or end an instruction, but whose
beginning and ending functions are not both contained within a single
translation unit. For example, an instruction to embolden text may
apply to the first of three sentences in a paragraph contained within
a single translation unit, but the instruction to turn off bolding
may only appear at the end of the third sentence. Its beginning
instruction is present in the first translation unit, while its
closing tag is present in the third translation unit. The elements
that can handle such cases are: <code> <link linkend="it">&lt;it></link
> </code> and <code> <link linkend="x">&lt;x/></link> </code>.</para>
<para>C) Codes that represent self-contained functions that do not
require explicit ending instructions. Images or cross-reference
tokens are examples of these standalone codes. The elements that
can handle such cases are: <code> <link linkend="ph">&lt;ph></link
> </code> and <code> <link linkend="x">&lt;x/></link> </code>.</para>
<para>The guidelines for using the inline elements are as follows:</para>
<itemizedlist>
<listitem><para>Use <code> <link linkend="bpt">&lt;bpt></link> 
 </code> or <code> <link linkend="bx">&lt;bx/></link> </code> for
opening each code that has a corresponding closing code in the
content. Use <code> <link linkend="bpt">&lt;bpt></link> </code
> to mask the code and <code> <link linkend="bx">&lt;bx/></link> 
 </code> to replace the code. The <code> <link linkend="bpt"
>&lt;bpt></link> </code> and <code> <link linkend="bx">&lt;bx/></link
> </code> elements should be followed by a matching <code> <link
linkend="ept">&lt;ept></link> </code> or <code> <link linkend="ex"
>&lt;ex/></link> </code> element, respectively, within the
same translation unit. These paired elements are matched by setting
their <code> <link linkend="rid">rid</link> </code> attributes
to the same value. For example: <code>&lt;bpt id='2' rid='1'>xx&lt;/bpt>
... &lt;ept id='3' rid='1'>xx&lt;/ept></code> and <code>&lt;bx
id='4' rid='2'/> ... &lt;ex id='5' rid='2'/></code>. If the <code
> <link linkend="rid">rid</link> </code> attribute is not present
(in a 1.0 document for example), the attribute <code> <link
linkend="id">id</link> </code> is used to match both tags. For
example: <code>&lt;bpt id='5'>xx&lt;/bpt> ... &lt;ept id='5'>xx&lt;/ept></code
>.</para></listitem>
<listitem><para>Use <code> <link linkend="ept">&lt;ept></link> 
 </code> or <code> <link linkend="ex">&lt;ex/></link> </code> for
closing each code that has a corresponding opening code in the
content. Use <code> <link linkend="ept">&lt;ept></link> </code
> to mask the code and <code> <link linkend="ex">&lt;ex/></link> 
 </code> to replace the code. The <code> <link linkend="ept"
>&lt;ept></link> </code> and <code> <link linkend="ex">&lt;ex/></link
> </code> elements should be preceded by a matching <code> <link
linkend="bpt">&lt;bpt></link> </code> and <code> <link
linkend="bx">&lt;bx/></link> </code> element, respectively. 
 These paired elements are matched by setting their <code> <link
linkend="rid">rid</link> </code> attributes to the same value.
For example: <code>&lt;bpt id='2' rid='1'>xx&lt;/bpt> ... &lt;ept
id='3' rid='1'>xx&lt;/ept></code> and <code>&lt;bx id='4' rid='2'/>
... &lt;ex id='5' rid='2'/></code>. If the <code> <link linkend="rid"
>rid</link> </code> attribute is not present (in a 1.0 document
for example), the attribute <code> <link linkend="id">id</link> 
 </code> is used to match both tags. For example: <code>&lt;bpt
id='5'>xx&lt;/bpt> ... &lt;ept id='5'>xx&lt;/ept></code>.</para>
</listitem>
<listitem><para>Use <code> <link linkend="g">&lt;g></link> </code
> to replace any inline code of the original document that has
a beginning and an end and can be moved within its parent structural
element.</para></listitem>
<listitem><para>Use <code> <link linkend="ph">&lt;ph></link> </code
> or <code> <link linkend="x">&lt;x/></link> </code> for standalone
codes. Use <code> <link linkend="ph">&lt;ph></link> </code
> to mask the code and <code> <link linkend="x">&lt;x/></link> 
 </code> to replace the code. Standalone codes are codes that
are not opening or closing of a pair, for example empty elements
in XML.</para></listitem>
<listitem><para>Use <code> <link linkend="it">&lt;it></link> </code
> for opening or closing each code that has no corresponding closing
or opening code in the source element. In some cases, because of
the segmentation, you may have opening and closing codes that have
no corresponding closing or opening codes within the same translation
unit. Use <code> <link linkend="it">&lt;it></link> </code> to
encapsulate those codes. The <code> <link linkend="it">&lt;it></link
> </code> element has a mandatory <code> <link linkend="pos">pos</link
> </code> attribute that should be set to <code>"begin</code
>" or "<code>end"</code> depending on whether the isolated code
is an opening or a closing code.</para></listitem>
<listitem><para>Use the <code> <link linkend="xid">xid</link> </code
> attribute of the <code> <link linkend="bx">&lt;bx/></link> 
 </code>, <code> <link linkend="ex">&lt;ex/></link> </code> and <code
> <link linkend="x">&lt;x/></link> </code> elements to relate
a <code> <link linkend="trans-unit">&lt;trans-unit></link> </code
> or <code> <link linkend="bin-unit">&lt;bin-unit></link> </code
> that contains the content of that replaced code.</para></listitem>
<listitem><para>At the time of this document's authoring, TMX 14b
does not support <link linkend="g">&lt;g></link> and <link linkend="x"
>&lt;x/></link> inline tag equivalents. Therefore, if interchange
of translation memory data with TMX is required, use <link
linkend="bpt">&lt;bpt></link> and <link linkend="ept">&lt;ept></link
> tags instead of <link linkend="g">&lt;g></link> and <code> <link
linkend="ph">&lt;ph></link> </code> tags instead of <link linkend="x"
>&lt;x/></link>.</para></listitem>
</itemizedlist>
<para>As XLIFF inline elements are closely related to TMX inline
elements, further examples of usage of these tags may be found in
their specification's <ulink
url="http://www.lisa.org/tmx/tmx.htm#SectionContentMarkup";>Content
 Markup section</ulink>.</para>
<para>Inline elements are normally treated as being transparent
with regard to lexical processing such as segmentation or word tokenisation.
If the inline element also represents a lexical function, such as
implying spacial characteristics or a string of characters or symbols,
then the <link linkend="equiv-text"> <code>equiv-text</code
> </link> attribute must be used to denote any such
lexical characteristics.</para>
<para>For example:</para>
<programlisting>
&lt;p>This HTML break element&lt;br/>is not followed by a white space character&lt;/p>

 
</programlisting>
<para>is represented in an XLIFF document as:</para>
<programlisting>
&lt;source>This HTML break element&lt;x id="x1" ctype="x-html-br" equiv-text=" "/>is not followed
by a white space character.&lt;/source>
 
</programlisting>
</section>
<section>
<title id="Struct_Extension">Extensibility</title>
<para>At times, it may be useful to extend the set of information
available in an XLIFF document by inserting constructs defined in
various other XML vocabularies. You can add non-XLIFF elements,
as well as attributes and attribute values. Adding elements and
attributes use the namespace mechanism [ <link linkend="refXMLNames"
>XML Names</link>]. Adding attribute values generally involves preceding
the value by an "<code>x-</code>" (e.g. <code>&lt;context context-type='x-for-engineers'></code
>).</para>
<para>Although XLIFF offers this extensibility mechanism, in order
to avoid a nimiety of information and increase interoperability
between tools, it is strongly recommended to use XLIFF capabilities
whenever possible, rather than to create non-standard user-defined
elements or attributes.</para>
<section>
<title id="Struct_Extension_Elements">Adding Elements</title>
<para>XLIFF provides several extension points in the following elements: <code
> <link linkend="alt-trans">&lt;alt-trans></link> </code>, <code
> <link linkend="bin-unit">&lt;bin-unit></link> </code>, <code
> <link linkend="group">&lt;group></link> </code>, <code> 
 <link linkend="header">&lt;header></link> </code>, <code> <link
linkend="tool_elem">&lt;tool></link> </code>, <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code>, and <code> 
 <link linkend="xliff">&lt;xliff></link> </code>.</para>
<para>Several non-XLIFF elements can be used at each extension point.
The content of each element can be any valid XML content (empty
content, PCDATA, mixed content, and so forth).</para>
<para>For example, the following XLIFF code shows how to add user-defined
elements (in bold) within an XLIFF document:</para>
<programlisting>
&lt;xliff version='1.2'
 xmlns='urn:oasis:names:tc:xliff:document:1.2'
 <emphasis>xmlns:sup='http://www.ChaucerState.ac.pg/Frm/XLFSup-v1'</emphasis
>>
&lt;file original='passus-1.doc' source-language='enm' datatype='plaintext'>
&lt;group>
<emphasis>&lt;sup:SourceInfo>
&lt;sup:Book>Piers Plowman, Passus 1&lt;/sup:Book>

&lt;sup:Author>William Langland&lt;/sup:Author>
&lt;/sup:SourceInfo></emphasis>
 <emphasis>&lt;sup:WorkInfo Task='transcription' Context='Middle-English:1360'/></emphasis
> 
&lt;trans-unit id='1'>
&lt;source xml:lang='enm'>What this mountaigne bymeneth&lt;/source>
&lt;target xml:lang='en'>What this mountain means&lt;/target>

<emphasis>&lt;sup:Reference Type='strophe'>1-a&lt;/sup:Reference></emphasis
> 
&lt;/trans-unit>
&lt;trans-unit id='2'>
&lt;source xml:lang='enm'>and the merke dale&lt;/source>
&lt;target xml:lang='en'>and the dark dale&lt;/target>
<emphasis>&lt;sup:Reference Type='strophe'>1-b&lt;/sup:Reference></emphasis
> 

&lt;/trans-unit>
&lt;trans-unit id='3'>
&lt;source xml:lang='enm'>And the feld ful of folk&lt;/source>
&lt;target xml:lang='en'>And the field full of folk&lt;/target>
<emphasis>&lt;sup:Reference Type='strophe'>2-a&lt;/sup:Reference></emphasis
>
&lt;/trans-unit>

&lt;trans-unit id='4'>
&lt;source xml:lang='enm'>I shal yow faire shewe.&lt;/source>
&lt;target xml:lang='en'>I fairly will show.&lt;/target>
<emphasis>&lt;sup:Reference Type='strophe'>2-b&lt;/sup:Reference></emphasis
>
&lt;/trans-unit>
&lt;/group>

&lt;/file>
&lt;/xliff>
</programlisting>
<para>The non-XLIFF elements used in the example above would be
defined as the following:</para>
<programlisting>
&lt;xsd:schema targetNamespace="XLFSup-v1"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema";
 xmlns:sup="http://www.ChaucerState.ac.pg/Frm/XLFSup-v1";
 elementFormDefault="qualified" attributeFormDefault="unqualified">
&lt;xsd:element name="SourceInfo">
&lt;xsd:complexType>

 &lt;xsd:sequence maxOccurs="unbounded">

&lt;xsd:element name="Book" type="xsd:string"/>
&lt;xsd:element name="Author" type="xsd:string"/>
&lt;/xsd:sequence>

 &lt;/xsd:complexType>
&lt;/xsd:element>
&lt;xsd:element name="WorkInfo">
&lt;xsd:complexType>
&lt;xsd:attribute name="Task" type="xsd:string"/>
&lt;xsd:attribute name="Context" type="xsd:string"/>

&lt;/xsd:complexType>
&lt;/xsd:element>
&lt;xsd:element name="Reference">
&lt;xsd:complexType>
&lt;xsd:simpleContent>
&lt;xsd:extension base="xsd:string">Struct_InLine
&lt;xsd:attribute name="Type" type="xsd:string"/>
&lt;/xsd:extension>
&lt;/xsd:simpleContent>

&lt;/xsd:complexType>
&lt;/xsd:element>
&lt;/xsd:schema>
</programlisting>
<para>It is not possible to add non-XLIFF elements in either the <code
> <link linkend="source">&lt;source></link> </code> or <code
> <link linkend="target">&lt;target></link> </code> elements.
 However, the <code> <link linkend="mrk">&lt;mrk></link> </code
> element can be used to markup sections of the text with user-defined
values assigned to the <link linkend="mtype"> <code
>mtype</code> </link> attribute. You can also add
non-XLIFF attributes to most of the inline elements used in <code
> <link linkend="source">&lt;source></link> </code> and <code
> <link linkend="target">&lt;target></link> </code>.</para>
</section>
<section>
<title id="Struct_Extension_Attributes">Adding Attributes</title>
<para>Attributes of a namespace different than XLIFF can be included
in several XLIFF elements.</para>
<para>The following elements allow non-XLIFF attributes: <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>, <link linkend="bin-source"> 
 <code>&lt;bin-source></code> </link>, <link
linkend="bin-target"> <code>&lt;bin-target></code
> </link>, <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link>, <link
linkend="bpt"> <code>&lt;bpt></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link>, <link linkend="ept"> <code
>&lt;ept></code> </link> , <link linkend="ex"> 
 <code>&lt;ex/></code> </link>, <link
linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="g"> <code>&lt;g></code
> </link> , <link linkend="group"> 
 <code>&lt;group></code> </link>, <link linkend="it"
> <code>&lt;it></code> </link>, <link
linkend="mrk"> <code>&lt;mrk></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="seg-source"> 
 <code>&lt;seg-source></code> </link>, <link
linkend="source"> <code>&lt;source></code> 
 </link>, <link linkend="target"> <code
>&lt;target></code> </link>, <code> <link
linkend="tool_elem">&lt;tool></link> </code>, <link
linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="x"> <code
>&lt;x/></code> </link>, and <link linkend="xliff"
> <code>&lt;xliff></code> </link
>.</para>
<para>For instance, the following XLIFF code illustrates how to
use attributes from the XHTML vocabulary (in bold) in the <link
linkend="group"> <code>&lt;group></code> 
 </link> and <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link> XLIFF elements. The
example shows how to carry formatting information about an extracted
table:</para>
<programlisting>
&lt;xliff version='1.2'
 xmlns='urn:oasis:names:tc:xliff:document:1.2'
 <emphasis>xmlns:htm='http://www.w3.org/1999/xhtml'</emphasis>>

&lt;file original='table.htm' source-language='en' datatype='html'>
&lt;group restype='table' <emphasis>htm:border='1'</emphasis>
 <emphasis>htm:cellpadding='5'</emphasis>
 <emphasis>htm:cellspacing='0'</emphasis>
 <emphasis>htm:width='100%'</emphasis>>
&lt;group restype='row'>
&lt;trans-unit id='1' <emphasis>htm:valign='top'</emphasis>
 <emphasis>htm:width='30%'</emphasis>>

&lt;source>Text of row 1 column 1&lt;/source>
&lt;/trans-unit>
&lt;trans-unit id='2' <emphasis>htm:valign='top'</emphasis>
 <emphasis>htm:width='30%'</emphasis>>
&lt;source>Text of row 1 column 2&lt;/source>
&lt;/trans-unit>

 &lt;/group>

&lt;group restype='row'>
&lt;trans-unit id='3' <emphasis>htm:valign='top'</emphasis>
 <emphasis>htm:width='30%'</emphasis>>
&lt;source>Text of row 2 column 1&lt;/source>
&lt;/trans-unit>
&lt;trans-unit id='4' <emphasis>htm:valign='top'</emphasis>
 <emphasis>htm:width='30%'</emphasis>>

&lt;source>Text of row 2 column 2&lt;/source>
&lt;/trans-unit>
&lt;/group>
&lt;/group>
&lt;/file>
&lt;/xliff>
</programlisting>
<para>In each of the XLIFF elements allowing non-XLIFF attributes:
there is no specific location where to insert the non-XLIFF attributes,
and there is no limit to the number of non-XLIFF attributes that
can be used.</para>
</section>
<section>
<title id="Struct_Extension_Values">Adding Attribute Values</title>
<para>Many attributes in XLIFF offer a list of enumerated values.
Some applications may find it necessary to add user-defined values
to these lists. XLIFF allows for such extension.</para>
<para>The attributes where the list of values can be extended are
the following: <link linkend="alttranstype"> <code
>alttranstype</code> </link>, <link linkend="context-type"
> <code>context-type</code> </link
>, <code> <link linkend="count-type">count-type</link> </code
>, <code> <link linkend="ctype">ctype</link> </code>, <code
> <link linkend="datatype">datatype</link> </code>, <code> 
 <link linkend="mtype">mtype</link> </code>, <code> <link
linkend="purpose">purpose</link> </code>, <code> <link
linkend="reformat">reformat</link> </code>, <code> <link
linkend="restype">restype</link> </code>, <code> <link
linkend="size-unit">size-unit</link> </code>, <code> <link
linkend="state">state</link> </code>, <code> <link
linkend="state-qualifier">state-qualifier</link> </code> , and <code
> <link linkend="unit">unit</link> </code> .</para>
<para>User-defined values must start with an "<code>x-</code>" prefix.
There is no specified mechanism to validate individual user-defined
values. The XLIFF schema will allow any value starting with "<code
>x-</code>" in addition to the pre-defined values.</para>
<para>For example, the following excerpt shows how the user-defined
value <code>x-for-engineer</code> can be utilized in a document:</para>
<programlisting>
...
&lt;group>
&lt;context-group name='EngineersData'>
&lt;context context-type='<emphasis>x-for-engineers</emphasis>'>Data...&lt;/context>

...
</programlisting>
</section>
<section>
<title id="Struct_Extension_Validation">Validating Documents with
Extensions</title>
<para>In order to validate an XLIFF document that contains non-XLIFF
parts, you can use the schema validation mechanism: In addition
to the namespace declarations, add the <code>schemaLocation</code
> attribute of the XML Schema-instance namespace to define what
schemas to use to validate the document (XLIFF and the non-XLIFF
namespaces).</para>
<para>Note: XLIFF 1.2 XML Schemas set the attribute <code>processContents</code
> to value <code>"skip"</code>, so the only validation requirement
 for non-XLIFF content is to ensure it is well-formed.</para>
<programlisting>
&lt;xliff version='1.2'
 xmlns='urn:oasis:names:tc:xliff:document:1.2'
<emphasis>xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'</emphasis
>
 <emphasis>xsi:schemaLocation='

 urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2.xsd
 http://www.ChaucerState.ac.pg/Frm/XLFSup-v1 XLFSup-v1.xsd'</emphasis
>
>
...
&lt;/xliff>
</programlisting>
<para>See <ulink url="http://www.w3.org/XML/Schema";>http://www.w3.org/XML/Schema</ulink
> for more information on XML Schema and validation.</para>
</section>
</section>
<section>
<title id="Struct_Embedding">Embedding XLIFF</title>
<para>XML Namespace provides a convenient mechanism to use XLIFF
constructs within another XML vocabulary.</para>
<para>If necessary an XLIFF document, or parts of a document, can
be embedded within another XML document. The only requirement for
this is on the side of the XML format that includes the XLIFF data.
For the document to be valid, the schema of the given document type
must include a definition for external elements.</para>
<para>If the including XML format uses XML Schema, it should include
an <code>&lt;any></code> element in the definition of the element
where the XLIFF data can be inserted. For example, the following
XSD excerpt illustrates the case of an element type <code>dataBlockType</code
> that can contain zero, one or more XLIFF constructs after a mandatory
 <code>&lt;type></code> element:</para>
<programlisting>
...
&lt;xsd:complexType name="dataBlockType">

&lt;xsd:sequence>
&lt;xsd:element name="type" type="string" minOccurs="0"/>
&lt;xsd:any namespace="##other" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
&lt;/xsd:sequence>
&lt;/xsd:complexType>
...
</programlisting>
<para>The ways of inserting different vocabulary in an XML document
using XSD are described in section "Any Element, Any Attribute"
in the document "XML Schema Part 0: Primer" available here: <ulink
url="http://www.w3.org/TR/xmlschema-0/#any";>http://www.w3.org/TR/xmlschema-0/#any</ulink
>.</para>
</section>
<section>
<title id="Struct_Nonequiv">Non equivalent translations</title>
<para>Linguistically complete text may have to be broken into a
number of <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> elements due to message size constraints or other reasons.
In these instances the translator is not providing an equivalent
translation for each <code> <link linkend="source">&lt;source></link
> </code>, but rather fitting in the target language text over
a number of <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> <link linkend="source"> <code>&lt;source></code
> </link> / <link linkend="target"> <code
>&lt;target></code> </link> pair elements to meet the
requirements of the target application.</para>
<para>Example:</para>
<programlisting>
&lt;trans-unit id="t1">

&lt;source>Constrained text for limited&lt;/source>
&lt;target>Tekst angielski dla&lt;/target>
&lt;/trans-unit>
&lt;trans-unit id="t2">
&lt;source>display for English&lt;/source>
&lt;target>ograniczonego pola&lt;/target>

&lt;/trans-unit>
</programlisting>
<para>In this circumstance the <code> <link linkend="equiv-trans"
>equiv-trans</link> </code> attribute for the <code> <link
linkend="target">&lt;target></link> </code> element is used to
denote that the translation should not be regarded as a direct translation
of the <code> <link linkend="source">&lt;source></link> </code
> element. The attribute is optional, and default value is <code
>"yes"</code>. The other possible value will be <code>"no"</code
> to indicate that the translation in <link linkend="target">&lt;target></link
> for the given <code> <link linkend="source">&lt;source></link
> </code> is not a direct equivalent linguistically of the source
language text. The following example demonstrates the use of the <code
> <link linkend="equiv-trans">equiv-trans</link> </code> attribute:</para>
<programlisting>
&lt;trans-unit id="t1"> 
&lt;source>Constrained text for limited&lt;/source>

&lt;target equiv-trans="no">Tekst angielski dla&lt;/target>
&lt;/trans-unit>
&lt;trans-unit id="t2">
&lt;source>display for English&lt;/source>
&lt;target equiv-trans="no">ograniczonego pola&lt;/target>
&lt;/trans-unit> 
</programlisting>
</section>
<section>
<title id="Struct_Grouping">Grouping translations across <code>&lt;trans-unit></code
> elements</title>
<para>It is inevitable that individual XLIFF <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> elements may
not represent a piece of text that can be translated without reference
 to one or more following <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> elements. The causes for this may be incorrect segmentation
or bad document design.</para>
<para>Example:</para>
<programlisting>
&lt;trans-unit id="t1"> 
 &lt;source>The German acronym v.&lt;/source>
 &lt;target>Niemiecki skr&Atilde;&sup3;t v. OT oznacza g&Atilde;&sup3;rna; pozycje; silnika.&lt;/target>

&lt;/trans-unit>
&lt;trans-unit id="t2">
 &lt;source> OT signifies the top dead center position for an engine.&lt;/source>
 &lt;target/>
&lt;/trans-unit>
</programlisting>
<para>In these cases the <code> <link linkend="merged-trans">merged-trans</link
> </code> attribute for the <code> <link linkend="group">&lt;group></link
> </code> element can be used to denote that the individual <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code> elements
cannot be regarded as a direct translation, but rather need to be
treated linguistically as a merged group. This attribute has two
possible values: <code>"yes"</code> or <code>"no"</code>. The
default value is <code>"no"</code>. A value of <code>"yes"</code
> indicates that the <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> elements contained within this <code> <link
linkend="group">&lt;group></link> </code> element are to be treated
together for linguistic purposes. All <code> <link linkend="trans-unit"
>&lt;trans-unit></link> </code> elements that are encompassed by
a <code> <link linkend="group">&lt;group></link> </code> element
that has its <code> <link linkend="merged-trans">merged-trans</link
> </code> attribute set to <code>"yes"</code> normally have their
related <code> <link linkend="target">&lt;target></link> <link
linkend="equiv-trans">equiv-trans</link> </code> attribute set to
the value of <code>"no"</code>. The text of all of the <code> 
 <link linkend="source">&lt;source></link> </code> and <code> <link
linkend="target">&lt;target></link> </code> elements taken together
 form one linguistic whole. No requirements are made regarding the
 distribution of the translation in the <code> <link linkend="target"
>&lt;target></link> </code> elements. This will be governed by
the requirements of the individual applications. The translated
text may be placed within the first <code> <link linkend="target"
>&lt;target></link> </code> element leaving the following <code
> <link linkend="target">&lt;target></link> </code> elements
blank, or distributed among the <code> <link linkend="target">&lt;target></link
> </code> elements contained within the <code> <link
linkend="merged-trans">merged-trans</link> </code> attribute of
the <code> <link linkend="group">&lt;group></link> </code> element.
The following example demonstrates the use of the <code> <link
linkend="merged-trans">merged-trans</link> </code> attribute for
the <code> <link linkend="group">&lt;group></link> </code> element:</para>
<programlisting>
&lt;group merged-trans="yes">
&lt;trans-unit id="t1">
&lt;source>The German acronym v.&lt;/source>

&lt;target equiv-trans="no">Niemiecki skr&Atilde;&sup3;t v. OT oznacza g&Atilde;&sup3;rna; pozycje; silnika.&lt;/target>
&lt;/trans-unit>
&lt;trans-unit id="t2">
&lt;source> OT signifies the top dead center position for an engine.&lt;/source>
&lt;target equiv-trans="no"/>
&lt;/trans-unit>

&lt;/group>
</programlisting>
</section>
<section>
<title id="Struct_Segmentation">Segmentation</title>
<para>During some operations, such as translation and leveraging,
it may be important for the user agent to break down the content
of the <code> <link linkend="source">&lt;source></link> </code
> into smaller runs of text (for example, sentences). These smaller
parts of text are called <emphasis>segments</emphasis>. The process
of breaking down a text into segments is known as <emphasis>segmentation</emphasis
>. It is important to note that the manipulation / segmentation
of trans-unit elements is owned by the "translator" domain, not
at the extraction filter domain. This means that segmentation will
be performed by the editing tool or possibly an automated segmentation
process.</para>
<para>In order to avoid modifying the content of the original <code
> <link linkend="source">&lt;source></link> </code> element, 
during segmentation a new element <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> is introduced. The content of the <code
> <link linkend="seg-source">&lt;seg-source></link> </code> element
is the same as the content of the <code> <link linkend="source"
>&lt;source></link> </code> element, but with segmentation markup.
The segmentation markup is also transferred to the <code> <link
linkend="target">&lt;target></link> </code> element as applicable
during translation.</para>
<para>Each segment inside the <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> and <code> <link linkend="target"
>&lt;target></link> </code> content is represented using the <code
> <link linkend="mrk">&lt;mrk></link> </code> element with attribute <code
> <link linkend="mtype">mtype</link> </code> set to the value 
 "<code>seg</code>". For example the following <code> <link
linkend="source">&lt;source></link> </code> element contains three
 segments. After segmentation the content may look as follows:</para>
<programlisting>
&lt;source>Richard stepped out of the kitchen hut. He noticed a movement from the corner of his
eye. A monkey had climbed on top of one of the workshop sheds, trying to get in by the 
ventilation shaft.&lt;/source>
&lt;seg-source>&lt;mrk mtype="seg">Richard stepped out of the kitchen hut.&lt;/mrk>
&lt;mrk mtype="seg">He noticed a movement from the corner of his eye.&lt;/mrk>

&lt;mrk mtype="seg">A monkey had climbed on top of one of the workshop sheds, trying to get in
 by the ventilation shaft.&lt;/mrk>
&lt;/seg-source>
</programlisting>
<para>Note that it may be advisable for XLIFF processing tools to
add any missing opening or closing tags when exporting standalone
segments outside the original XLIFF document.</para>
<para>Non-clonable <link linkend="g">&lt;g></link> elements introduce
a problem for localisation in general and segmentation in particular
when the non-clonable <link linkend="g">&lt;g></link> elements content
spans more than single words or isolated expressions. In this form
they represent localisation-unfriendly content and are very likely
to cause difficulties during translation. Being able to break a
segment inside such an element may be the smallest of the problems
that tools would be faced with. A non-clonable <link linkend="g"
>&lt;g></link> element clearly represents a piece of content that
must be translated as one piece, and cannot be segmented.</para>
<para> <emphasis>Example:</emphasis> This example shows how content
 with clonable <link linkend="g">&lt;g></link> may be localised:</para>
<programlisting>
&lt;source>This is a &lt;g> sentence. It has
&lt;/g> markup.&lt;/source>
</programlisting>
<para>The translation into "Yoda-English" would be:</para>
<programlisting>
&lt;target>A &lt;g>sentence &lt;/g> this is. Markup &lt;g> it has &lt;/g>.&lt;/target>
</programlisting>
<para>In this example the <link linkend="g">&lt;g></link> element
is clonable, and can be localised correctly. However, in the case
where cloning is not possible, the resulting content cannot be correctly
localised, and is in fact irrespective of whether segments are introduced
here or not.</para>
<para>If matching segments need to be identified between <code> 
 <link linkend="seg-source">&lt;seg-source></link> </code> and <code
> <link linkend="target">&lt;target></link> </code>, and/or between <code
> <link linkend="seg-source">&lt;seg-source></link> </code> content
and corresponding <code> <link linkend="alt-trans">&lt;alt-trans></link
> </code> units, the <code> <link linkend="mid">mid</link> </code
> attribute should be used for this purpose.</para>
<para> <emphasis>Example:</emphasis> This example shows how corresponding
segments are referenced between <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> and <code>&lt;target></code> elements
in a <code> <link linkend="trans-unit">&lt;trans-unit></link> </code
>.</para>
<programlisting>
&lt;trans-unit id= "1">
&lt;source>First sentence.Second sentence.&lt;/source>
&lt;seg-source>
&lt;mrk mtype="seg" mid="1">First sentence.&lt;/mrk>
&lt;mrk mtype="seg" mid="2">Second sentence.&lt;/mrk>

&lt;/seg-source>
&lt;target>
&lt;mrk mtype="seg" mid="1">Translated first sentence.&lt;/mrk>
&lt;mrk mtype="seg" mid="2">Translated second sentence.&lt;/mrk>
&lt;/target>
&lt;/trans-unit>
</programlisting>
<para> <emphasis>Example:</emphasis> In the following <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> the <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> represents a 75%
 fuzzy match for the second segment in the <code> <link
linkend="seg-source">&lt;seg-source></link> </code>. This is indicated
 by introducing the <code> <link linkend="mid">mid</link>="2"</code
> attribute on the <code> <link linkend="alt-trans">&lt;alt-trans></link
> </code>.</para>
<programlisting>
&lt;trans-unit id= "2">
&lt;source>First sentence.Second sentence.&lt;/source>
&lt;seg-source>
&lt;mrk mtype="seg" mid="1">First sentence.&lt;/mrk>
&lt;mrk mtype="seg" mid="2">Second sentence.&lt;/mrk>

&lt;/seg-source>
&lt;alt-trans mid="2" match-quality="75%">
&lt;source>The second sentence.&lt;/source>
&lt;target>The translated second sentence.&lt;/target>
&lt;/alt-trans>
&lt;/trans-unit>
</programlisting>
<para> <emphasis>Example:</emphasis> An <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> element may also
 have segmented content:</para>
<programlisting>
&lt;trans-unit id="3">
&lt;source>The second sentence.&lt;/source>

&lt;alt-trans match-quality="50%">
&lt;source>First sentence. Second sentence.&lt;/source>
&lt;seg-source>
&lt;mrk mtype="seg" mid="1">First sentence.&lt;/mrk>
&lt;mrk mtype="seg" mid="2">Second sentence.&lt;/mrk>
&lt;/seg-source>

&lt;target>
&lt;mrk mtype="seg" mid="1">Translated first sentence.&lt;/mrk>
&lt;mrk mtype="seg" mid="2">Translated second sentence.&lt;/mrk>
&lt;/target>
&lt;/alt-trans>
&lt;/trans-unit>
</programlisting>
</section>
</section>
<section>
<title id="SectionSpecs">Detailed Specifications</title>
<section>
<title id="Specs_XMLDecl">XML Declaration</title>
<para>The XML declaration is strongly recommended. It indicates
the XML version and sets the defaults for the encoding of the file.
For example, the following declaration specifies the document is
in ISO 8859-1, the Latin-1 encoding.</para>
<programlisting>
&lt;?xml version="1.0" encoding="iso-8859-1"?>
</programlisting>
<para>As in all XML files, the default encoding for an XLIFF file
is assumed to be either UTF-8, which is a superset of the 7-bit
ASCII character set, or UTF-16, which is UCS-2 with surrogate pairs
for code points above U+FFFF. Thus, for these character sets, the
encoding declaration is not necessary. Further, all XML parsers
support these encodings. If the encoding is in UTF-16 the first
character of the file must be the Unicode Byte-Order-Mark, U+FEFF,
which indicates the endianness of the file. Other encodings may
be desirable and may be generally supported by XML parsers. These
must be declared using the encoding declaration. The values to use
for the encoding declaration are defined in the [<link
linkend="refIANACharsets">IANA Charsets</link>] listing.</para>
<para>If necessary, you can also specify a namespace for XLIFF.
The namespace identifier for this standard is "<code>urn:oasis:names:tc:xliff:document:1.2</code
>".</para>
<para>A minimal XLIFF document with one entry looks something like
this:</para>
<programlisting>
&lt;?xml version="1.0"?>

&lt;xliff version="1.2">
&lt;file source-language="EN" datatype="plaintext" original="file.ext">
&lt;body>
&lt;trans-unit id="1">
&lt;source>Hello World!&lt;/source>
&lt;/trans-unit>
&lt;/body>
&lt;/file>

&lt;/xliff>
</programlisting>
<para>If you need to validate the document, use the schema validation
mechanism: In addition to the namespace declarations, add the <code
>schemaLocation</code> attribute of the XML Schema-instance namespace
to define what schema files to use. The same example as above would
then look like this: </para>
<programlisting>
&lt;?xml version="1.0"?>
&lt;xliff version='1.2'
 xmlns='urn:oasis:names:tc:xliff:document:1.2'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='
 urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2.xsd'>
&lt;file source-language="EN" datatype="plaintext" original="file.ext">

&lt;body>
&lt;trans-unit id="1">
&lt;source>Hello World!&lt;/source>
&lt;/trans-unit>
&lt;/body>
&lt;/file>
&lt;/xliff>
</programlisting>
<para>If a document of a previous compatible version of XLIFF is
to be validated with the schema of a newer version, the document
should use the same mechanism.</para>
<para>For validating documents that include non-XLIFF namespaces
see the section <link linkend="Struct_Extension_Validation">Validating
Documents with Extensions</link>.</para>
</section>
<section>
<title id="Specs_Elem">Elements</title>
<para>XLIFF elements can be divided into five main categories: the
top-level and header elements, the named group elements, the structural
elements, the inline elements, and the delimiter elements. <link
linkend="Specs_Attr">Attributes</link> are shared among them.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <link linkend="Specs_Elem_TopHeader">Top Level and Header</link
> elements</entry>
<entry> <link linkend="xliff"> <code
>&lt;xliff></code> </link>, <link linkend="file"
> <code>&lt;file></code> 
 </link>, <link linkend="header"> 
 <code>&lt;header></code> </link>, <link
linkend="skl"> <code>&lt;skl></code> 
 </link>, <link linkend="external-file"> 
 <code>&lt;external-file></code> 
 </link>, <link linkend="internal-file"> <code
>&lt;internal-file></code> </link>, <link linkend="glossary"> 
 <code>&lt;glossary></code> </link>, <link linkend="reference"
> <code>&lt;reference></code> 
 </link> , <link linkend="phase-group"> 
 <code>&lt;phase-group></code> 
 </link>, <link linkend="phase"> <code
>&lt;phase></code> </link>, <code> <link
linkend="tool_elem">&lt;tool></link> </code>, <link linkend="note"
> <code>&lt;note></code> 
 </link>.</entry>
</row>
<row>
<entry> <link linkend="Specs_Elem_NamedGroups">Named Group</link
> Elements</entry>
<entry> <link linkend="context-group"> 
 <code>&lt;context-group></code> </link>, <link
linkend="context"> <code>&lt;context></code> </link>, <link
linkend="count-group"> <code>&lt;count-group></code
> </link> , <link linkend="count"> 
 <code>&lt;count></code> 
 </link>, <link linkend="prop-group"> <code
>&lt;prop-group></code> </link> , <link
linkend="prop"> <code>&lt;prop></code> 
 </link>.</entry>
</row>
<row>
<entry> <link linkend="Specs_Elem_Struct">Structural</link> elements</entry>
<entry> <link linkend="body"> <code>&lt;body></code
> </link>, <link linkend="group"> 
 <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link
linkend="source"> <code>&lt;source></code
> </link>, <link linkend="target"> 
 <code>&lt;target></code> 
 </link>, <link linkend="bin-unit"> <code
>&lt;bin-unit></code> </link>, <link
linkend="bin-source"> <code>&lt;bin-source></code
> </link>, <link linkend="bin-target"> 
 <code>&lt;bin-target></code> 
 </link> , <link linkend="alt-trans"> 
 <code>&lt;alt-trans></code> </link
> .</entry>
</row>
<row>
<entry> <link linkend="Specs_Elem_Inline">Inline</link> elements</entry>
<entry> <link linkend="g"> <code>&lt;g></code
> </link>, <link linkend="x"> 
 <code>&lt;x/></code> </link
>, <link linkend="bx"> <code>&lt;bx/></code
> </link>, <link linkend="ex"> 
 <code>&lt;ex/></code> </link
>, <link linkend="bpt"> <code>&lt;bpt></code
> </link>, <link linkend="ept"> 
 <code>&lt;ept></code> </link
>, <link linkend="sub"> <code>&lt;sub></code
> </link>, <link linkend="it"> 
 <code>&lt;it></code> </link
>, <link linkend="ph"> <code>&lt;ph></code
> </link>.</entry>
</row>
<row>
<entry> <link linkend="Specs_Elem_Delim">Delimiter</link> element</entry>
<entry> <link linkend="mrk"> <code>&lt;mrk></code
> </link>.</entry>
</row>
</tbody>
</tgroup>
</table>
<section>
<title id="Specs_Elem_TopHeader">Top-level and Header Elements</title>
<para>The top-level and header elements are the following:</para>
<para id="xliff"> &lt;xliff></para>
<para> <emphasis>XLIFF document</emphasis> - The <code>&lt;xliff></code
> element encloses all the other elements of the document. The required <link
linkend="version"> <code>version</code> 
 </link> attribute specifies the version of XLIFF. The optional <link
linkend="xml_lang"> <code>xml:lang</code> 
 </link> attribute is used to specify the language of the
content of the document.</para>
<para>Required attributes:</para>
<para> <link linkend="version"> <code>version</code> 
 </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="xml_lang"> <code>xml:lang</code> 
 </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>One or more <link linkend="file"> <code>&lt;file></code
> </link> elements, followed by Zero, one or more
non-XLIFF elements.</para>
<para id="file"> &lt;file></para>
<para> <emphasis>File</emphasis> - The <code>&lt;file></code> 
element corresponds to a single extracted original document. The 
 required <link linkend="original"> <code>original</code
> </link> attribute specifies the name of the file
from which this file content is derived. The required <link
linkend="datatype"> <code>datatype</code> 
 </link> attribute specifies the format of the original
file; e.g. "html". The required <link linkend="source-language"
> <code>source-language</code> </link
> attribute specifies the language of the <link linkend="source"
> <code>&lt;source></code> </link
> content. The optional <link linkend="target-language"> 
 <code>target-language</code> </link> attribute
 is used to specify the language of the <link linkend="target"> 
 <code>&lt;target></code> </link> content.
The optional <link linkend="tool-id"> <code>tool-id</code
> </link> attribute accepts the id of the <link
linkend="tool_elem"> <code>&lt;tool></code> 
 </link> used to generate this XLIFF document. The optional <link
linkend="date"> <code>date</code> 
 </link> attribute is used to specify the creation date of this
XLIFF file. The optional <link linkend="xml_space"> 
 <code>xml:space</code> </link> attribute is used
to specify how white-spaces are to be treated. The optional <link
linkend="category"> <code>category</code> 
 </link> attribute is used to specify a general category
of the content of the file; e.g. "medical". The optional <link
linkend="product-name"> <code>product-name</code
> </link> attribute is used to specify the name of
the product which uses this file. The optional <link
linkend="product-version"> <code>product-version</code
> </link> and <link linkend="build-num"> 
 <code>build-num</code> </link> attributes are
used to specify the revision of the product from which this file
comes. The <link linkend="tool"> <code>tool</code
> </link> and <link linkend="ts"> 
 <code>ts</code> </link> attributes have been deprecated
in XLIFF 1.1.</para>
<para>Required attributes:</para>
<para> <link linkend="original"> <code>original</code> 
 </link>, <code> <link linkend="source-language">source-language</link
> </code>, <link linkend="datatype"> <code>datatype</code
> </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="tool"> <code>tool</code> </link
>, <code> <link linkend="tool-id">tool-id</link> </code>, <link
linkend="date"> <code>date</code> 
 </link>, <link linkend="xml_space"> <code>xml:space</code
> </link>, <link linkend="ts"> <code
>ts</code> </link>, <link linkend="category"> 
 <code>category</code> </link>, <link
linkend="target-language"> <code>target-language</code
> </link>, <link linkend="product-name"> 
 <code>product-name</code> </link>, <link
linkend="product-version"> <code>product-version</code
> </link>, <link linkend="build-num"> 
 <code>build-num</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Zero or one <link linkend="header"> <code
>&lt;header></code> </link> element, followed by
 One <link linkend="body"> <code>&lt;body></code
> </link> element.</para>
<para id="header"> &lt;header></para>
<para> <emphasis>File header</emphasis> - The <code>&lt;header></code
> element contains metadata relating to the <link linkend="file"
> <code>&lt;file></code> </link> element.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>zero or one <link linkend="skl"> <code>&lt;skl></code
> </link> element, followed by zero or one <link
linkend="phase-group"> <code>&lt;phase-group></code
> </link> element, followed by zero, one or more <link
linkend="glossary"> <code>&lt;glossary></code> 
 </link>, <link linkend="reference"> 
 <code>&lt;reference></code> </link>, <link
linkend="count-group"> <code>&lt;count-group></code
> </link>, <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link>, <link
linkend="note"> <code>&lt;note></code> 
 </link>, <link linkend="tool_elem"> <code
>&lt;tool></code> </link> elements, in any order,
followed by Zero, one or more non-XLIFF elements.</para>
<para>While for backward compatibility reasons no order is enforced
for the elements before the non-XLIFF elements, the recommended
order is the one in which they are listed here.</para>
<para id="skl"> &lt;skl></para>
<para> <emphasis>Skeleton file</emphasis> - The <code>&lt;skl></code
> element contains the skeleton file or the location of the skeleton
file. The skeleton file is a template that can be used in recreating
the original file, from the <link linkend="source"> 
 <code>&lt;source></code> </link> content, or the
 translated file, from the <link linkend="target"> 
 <code>&lt;target></code> </link> content.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None</para>
<para>Contents:</para>
<para>Either exactly one <link linkend="internal-file"> 
 <code>&lt;internal-file></code> </link> or
one <link linkend="external-file"> <code>&lt;external-file></code
> </link> element.</para>
<para id="internal-file"> &lt;internal-file></para>
<para> <emphasis>Internal file</emphasis> - The <code>&lt;internal-file></code
> element contains the actual file being referenced. It is a child
of the <link linkend="skl"> <code>&lt;skl></code
> </link> , <link linkend="glossary"> 
 <code>&lt;glossary></code> </link>, and <link
linkend="reference"> <code>&lt;reference></code
> </link> elements. The format of the file is specified
by the optional <link linkend="form"> <code>form</code
> </link> attribute, which accepts mime-type values.
The <link linkend="crc"> <code>crc</code> 
 </link> attribute accepts a value that can be used to precisely
identify and assure the authenticity of the file.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="form"> <code>form</code> </link
>, <link linkend="crc"> <code>crc</code> 
 </link>.</para>
<para>Contents:</para>
<para>An embedded file.</para>
<para id="external-file"> &lt;external-file></para>
<para> <emphasis>External file</emphasis> - The <code>&lt;external-file></code
> element specifies the location of the actual file being referenced.
The required <link linkend="href"> <code>href</code
> </link> attribute provides a URI to the file. The <link
linkend="crc"> <code>crc</code> </link
> attribute accepts a value that can be used to precisely identify
and assure the authenticity of the file. The <link linkend="uid"
> <code>uid</code> </link> attribute
allows a unique ID to be assigned to the file.</para>
<para>Required attributes:</para>
<para> <link linkend="href"> <code>href</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="uid"> <code>uid</code> </link
>, <link linkend="crc"> <code>crc</code> 
 </link>.</para>
<para>Contents:</para>
<para>The <code>&lt;external-file></code> is an empty element, including
attributes only.</para>
<para id="glossary"> &lt;glossary></para>
<para> <emphasis>Glossary</emphasis> - The <code>&lt;glossary></code
> element points to or contains a glossary, which can be used in
the localization of the file.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>The glossary description and either exactly one <link
linkend="internal-file"> <code>&lt;internal-file></code
> </link> or one <link linkend="external-file"> 
 <code>&lt;external-file></code> </link
> element.</para>
<para id="reference"> &lt;reference></para>
<para> <emphasis>Reference</emphasis> - The <code>&lt;reference></code
> element points to or contains reference material, which can aid
in the localization of the file.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>A description of the reference material and either exactly
one <link linkend="internal-file"> <code>&lt;internal-file></code
> </link> or one <link linkend="external-file"> 
 <code>&lt;external-file></code> </link
> element.</para>
<para arch="" id="note"> &lt;note></para>
<para> <emphasis>Note</emphasis> - The <code>&lt;note></code> 
element is used to add localization-related comments to the XLIFF
 document. The content of <code>&lt;note></code> may be instructions
from developers about how to handle the <code> <link linkend="source"
>&lt;source></link> </code>, comments from the translator about
the translation, or any comment from anyone involved in processing
the XLIFF file. The optional <link linkend="xml_lang"> 
 <code>xml:lang</code> </link> attribute specifies
the language of the note content. The optional <link linkend="from"
> <code>from</code> </link> attribute
indicates who entered the note. The optional <link linkend="priority"
> <code>priority</code> </link> attribute
allows a priority from 1 (high) to 10 (low) to be assigned to the
note. The optional <code> <link linkend="annotates">annotates</link
> </code> attribute indicates if the note is a general note or,
in the case of a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>, pertains specifically to the <code> <link
linkend="source">&lt;source></link> </code> or the <code> <link
linkend="target">&lt;target></link> </code> element.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="xml_lang"> <code>xml:lang</code> 
 </link>, <link linkend="from"> <code>from</code
> </link>, <link linkend="priority"> 
 <code>priority</code> </link>, <code> <link
linkend="annotates">annotates</link> </code> .</para>
<para>Contents:</para>
<para>Text, no standard elements.</para>
<para id="phase-group"> &lt;phase-group></para>
<para> <emphasis>Phase group</emphasis> - The <code>&lt;phase-group></code
> element contains information about the task that has been performed
on the file. This phase information is specific to the tools and
workflow used in processing the file.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>One or more <link linkend="phase"> <code>&lt;phase></code
> </link> elements.</para>
<para id="phase"> &lt;phase></para>
<para> <emphasis>Phase information</emphasis> - The <code>&lt;phase></code
> element contains metadata about the tasks performed in a particular
process. The required <link linkend="phase-name"> 
 <code>phase-name</code> </link> attribute uniquely
 identifies the phase for reference within the <code> <link
linkend="file">&lt;file></link> </code> element. The required <link
linkend="process-name"> <code>process-name</code
> </link> attribute identifies the kind of process
the phase corresponds to; e.g. "proofreading". The optional <link
linkend="company-name"> <code>company-name</code
> </link> attribute identifies the company performing
the task. The optional <code> <link linkend="tool-id">tool-id</link
> </code> attribute references the <link linkend="tool_elem"> 
 <code>&lt;tool></code> </link> used
in performing the task. The optional <link linkend="date"> 
 <code>date</code> </link> attribute
provides a timestamp indicating when the task was performed. The
optional <link linkend="job-id"> <code>job-id</code
> </link> attribute allows an ID to be assigned to
the job. The optional <link linkend="contact-name"> 
 <code>contact-name</code> </link>, <link
linkend="contact-email"> <code>contact-email</code
> </link>, <code>and <link linkend="contact-phone"
>contact-phone</link> </code> attributes all refer to the person
performing the task.</para>
<para>Required attributes:</para>
<para> <link linkend="phase-name"> <code>phase-name</code
> </link>, <link linkend="process-name"> 
 <code>process-name</code> </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="company-name"> <code>company-name</code
> </link>, <link linkend="tool"> <code>tool</code
> </link>, <code> <link linkend="tool-id">tool-id</link
> </code>, <link linkend="date"> <code>date</code
> </link>, <link linkend="job-id"> 
 <code>job-id</code> </link>, <link
linkend="contact-name"> <code>contact-name</code
> </link>, <link linkend="contact-email"> 
 <code>contact-email</code> </link>, <link
linkend="contact-phone"> <code>contact-phone</code
> </link>.</para>
<para>Contents:</para>
<para>Zero, one or more <link linkend="note"> <code
>&lt;note></code> </link> elements.</para>
<para id="tool"> &lt;tool></para>
<para> <emphasis>Tool</emphasis> - The <code>&lt;tool></code> 
element describes the tool that has been used to execute a given 
 task in the document. The required <code> <link linkend="tool-id"
>tool-id</link> </code> attribute uniquely identifies the tool
for reference within the <code> <link linkend="file">&lt;file></link
> </code> element. The required <code> <link linkend="tool-name"
>tool-name</link> </code> attribute specifies the actual tool
name. The optional <code> <link linkend="tool-version">tool-version</link
> </code> attribute provides the version of the tool. The optional <code
> <link linkend="tool-company">tool-company</link> </code> attribute
provides the name of the company that produced the tool.</para>
<para>Required attributes:</para>
<para> <code> <link linkend="tool-id">tool-id</link> </code
>, <code> <link linkend="tool-name">tool-name</link> </code
>.</para>
<para>Optional attributes:</para>
<para> <code> <link linkend="tool-version">tool-version</link
> </code>, <code> <link linkend="tool-company">tool-company</link
> </code>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Zero, one or more non-XLIFF elements.</para>
</section>
<section>
<title id="Specs_Elem_NamedGroups">Named Group Elements</title>
<para>The named group elements are the following:</para>
<para id="count-group"> &lt;count-group></para>
<para> <emphasis>Count group</emphasis> - The <code>&lt;count-group></code
> element holds count elements relating to the level in the tree
in which it occurs. Each group for <code> <link linkend="count"
>&lt;count></link> </code> elements must be named, allowing different
uses for each group. The required <link linkend="name"> 
 <code>name</code> </link> attribute uniquely
identifies the <code>&lt;count-group></code> within the <code> 
 <link linkend="file">&lt;file></link> </code> element.</para>
<para>Required attributes:</para>
<para> <link linkend="name"> <code>name</code> </link
>.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>One or more <link linkend="count"> <code>&lt;count></code
> </link> elements.</para>
<para id="count"> &lt;count></para>
<para> <emphasis>Count</emphasis> - The <code>&lt;count></code> 
 element contains information about counts. For each <code>&lt;count></code
> element the required <link linkend="count-type"> 
 <code>count-type</code> </link> attribute indicates
 what kind of count the element represents, and the optional <code
> <link linkend="unit">unit</link> </code> attribute indicates
the unit of the count (by default: <code>word</code>). A list of
values for <link linkend="count-type"> <code>count-type</code
> </link> and <link linkend="unit"> 
 <code>unit</code> </link> is provided. The optional <link
linkend="phase-name">phase-name</link> attribute references the <link
linkend="phase"> <code>&lt;phase></code> 
 </link> in which the count was produced.</para>
<para>Required attributes:</para>
<para> <link linkend="count-type"> <code>count-type</code
> </link>.</para>
<para>Optional attributes:</para>
<para> <code> <link linkend="phase-name">phase-name</link>,</code
> <link linkend="unit"> <code>unit</code> </link
>.</para>
<para>Contents:</para>
<para>Number (the count value).</para>
<para id="context-group"> &lt;context-group></para>
<para> <emphasis>Context group</emphasis> - The <code>&lt;context-group></code
> element holds context elements relating to the level in the tree
in which it occurs. Thus context can be set at a <code> <link
linkend="group">&lt;group></link> </code> level, a <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> level, or
a <code> <link linkend="alt-trans">&lt;alt-trans></link> </code
> level. Each <code>&lt;context-group></code> element may be named,
allowing different uses for each group. When the &lt;context-group>
is named, these uses can be controlled through the use of XML processing
instructions. Because the <code>&lt;context-group></code> element
may occur at a very high level, a default context can be established
for all <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> elements within a file. This default can be overridden
at many subsequent levels. The optional <code> <link linkend="name"
>name</link> </code> attribute may uniquely identify the <code
>&lt;context-group></code> within the <code> <link linkend="file"
>&lt;file></link> </code> element. The optional <code> <link
linkend="crc">crc</link> </code> attribute allows a verification
 of the data. The optional <code> <link linkend="purpose">purpose</link
> </code> attribute indicates to what use this context information
is used; e.g. "match" indicates the context information is for memory
lookups.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="crc"> <code>crc</code> </link
>, <link linkend="name"> <code>name</code> 
 </link>, <link linkend="purpose"> <code
>purpose</code> </link> </para>
<para>Contents:</para>
<para>One or more <link linkend="context"> <code
>&lt;context></code> </link> elements.</para>
<para id="context"> &lt;context></para>
<para> <emphasis>Context</emphasis> - The <code>&lt;context></code
> element describes the context of a <code> <link linkend="source"
>&lt;source></link> </code> within a <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> or a <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>. The purpose of this context information
is to allow certain pieces of text to have different translations
depending on where they came from. The translation of a piece of
text may differ if it is a web form or a dialog or an Oracle form
or a Lotus form for example. This information is thus required by
a translator when working on the file. Likewise, the information
may be used by any tool proposing to automatically leverage the
text successfully.</para>
<para>The required <code> <link linkend="context-type">context-type</link
> </code> attribute indicates what the context information is;
e.g. "recordtitle" indicates the name of a record in a database.
The optional <code> <link linkend="match-mandatory">match-mandatory</link
> </code> attribute indicates that translations of the <code> 
 <link linkend="source">&lt;source></link> </code> elements within
the scope of this context must have the same context. The optional <code
> <link linkend="crc">crc</link> </code> attribute allows a
verification of the data.</para>
<para>Required attributes:</para>
<para> <link linkend="context-type"> <code>context-type</code
> </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="match-mandatory"> <code>match-mandatory</code
> </link> , <link linkend="crc"> <code>crc</code
> </link>.</para>
<para>Contents:</para>
<para>Text, no standard elements.</para>
<para id="prop-group"> &lt;prop-group></para>
<para> <emphasis>Property group</emphasis> - The <code>&lt;prop-group></code
> element contains <link linkend="prop"> <code>&lt;prop></code
> </link> elements. Each <code>&lt;prop-group></code
> element may be named, allowing different uses for each group.
These uses can be controlled through the use of XML processing instructions.</para>
<para>Important: The <code>&lt;prop-group></code> element was DEPRECATED
in version 1.1. Instead, use attributes defined in a namespace different
from XLIFF. See the <link linkend="Struct_Extension">Extensibility</link
> section for more information.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="name"> <code>name</code> </link
>.</para>
<para>Contents:</para>
<para>One or more <link linkend="prop"> <code>&lt;prop></code
> </link> elements.</para>
<para id="prop"> &lt;prop></para>
<para> <emphasis>Property</emphasis> - The <code>&lt;prop></code
> element allows the tools to specify non-standard information in
the XLIFF document. This information can be used by the tools that
have produced the file or that translate the file or that do any
other amount of processing specific to the producer.</para>
<para>Important: The <code>&lt;prop></code> element was DEPRECATED
in version 1.1. Instead, use attributes defined in a namespace different
from XLIFF. See the <link linkend="Struct_Extension">Extensibility</link
> section for more information.</para>
<para>Required attributes:</para>
<para> <link linkend="prop-type"> <code>prop-type</code
> </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="xml_lang"> <code>xml:lang</code> 
 </link>.</para>
<para>Contents:</para>
<para>Tool-specific data or text, no standard elements.</para>
</section>
<section>
<title id="Specs_Elem_Struct">Structural Elements</title>
<para>The structural elements specify the frame of a XLIFF document
as well as contextual and processing information. The <link
linkend="source"> <code>&lt;source></code> 
 </link> element contains the extracted data and, possibly, <link
linkend="Specs_Elem_Inline">inline elements</link>.</para>
<para id="body"> &lt;body></para>
<para> <emphasis>File body</emphasis> - The <code>&lt;body></code
> element contains the content from the file.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para>None.</para>
<para>Contents:</para>
<para>Zero, one or more <link linkend="group"> <code
>&lt;group></code> </link> , <link linkend="trans-unit"
> <code>&lt;trans-unit></code> </link
>, <link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link> elements, in any order.</para>
<para id="group"> &lt;group></para>
<para> <emphasis>Group</emphasis> - The <code>&lt;group></code> 
 element specifies a set of elements that should be processed together.
For example: all the items of a menu, etc. Note that a <code>&lt;group></code
> element can contain other <code>&lt;group></code> elements. The <code
>&lt;group></code> element can be used to describe the hierarchy
of the file.</para>
<para>The optional <code> <link linkend="id">id</link> </code
> attribute is used to uniquely identify the <code>&lt;group></code
> within the same <link linkend="file"> <code>&lt;file></code
> </link>. The optional <code> <link
linkend="datatype">datatype</link> </code> attribute specifies the
data type of the content of the <code>&lt;group></code>; e.g. 
"winres" for Windows resources. The optional <code> <link
linkend="xml_space">xml:space</link> </code> attribute is used to
specify how white-spaces are to be treated within the <code>&lt;group></code
>. The optional <code> <link linkend="restype">restype</link> 
 </code>, <code> <link linkend="resname">resname</link> </code
>, <code> <link linkend="extradata">extradata</link> </code
>, <code> <link linkend="help-id">help-id</link> </code>, <code
> <link linkend="menu">menu</link> </code> , <code> <link
linkend="menu-option">menu-option</link> </code>, <code> <link
linkend="menu-name">menu-name</link> </code>, <code> <link
linkend="coord">coord</link> </code>, <code> <link linkend="font"
>font</link> </code>, <code> <link linkend="css-style">css-style</link
> </code>, <code> <link linkend="style">style</link> </code
>, <code> <link linkend="exstyle">exstyle</link> </code>, and <code
> <link linkend="extype">extype</link> </code> attributes describe
the resources contained within the <code>&lt;group></code>. The
optional <code>translate</code> attribute provides a default value
for all <code>&lt;trans-unit></code> elements contained within the
 <code>&lt;group></code>. The optional <code> <link
linkend="reformat">reformat</link> </code> attribute specifies whether
 and which attributes can be modified for the <code> <link
linkend="target">&lt;target></link> </code> elements of the <code
>&lt;group></code>. The optional <code> <link linkend="maxbytes"
>maxbytes</link> </code> and <code> <link linkend="minbytes"
>minbytes</link> </code> attributes specify the required maximum
and minimum number of bytes for the translation units within the <code
>&lt;group></code>. The optional <code> <link linkend="size-unit"
>size-unit</link> </code> attribute determines the unit for the
optional <code> <link linkend="maxheight">maxheight</link> </code
>, <code> <link linkend="minheight">minheight</link> </code
>, <code> <link linkend="maxwidth">maxwidth</link> </code>,
and <code> <link linkend="minwidth">minwidth</link> </code> attributes,
which limit the size of the resource described by the <code>&lt;group></code
>. The optional <code> <link linkend="charclass">charclass</link
> </code> attribute restricts all translation units in the scope
of the <code>&lt;group></code> to a subset of characters. The optional
 <link linkend="merged-trans"> <code>merged-trans</code
> </link> attribute indicates if the group element contains
merged <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link> elements. The optional <code> <link
linkend="ts">ts</link> </code> attribute was DEPRECATED in XLIFF
1.1. Lists of values for the <code> <link linkend="datatype">datatype</link
> </code>, <code> <link linkend="restype">restype</link> </code
>, and <code> <link linkend="size-unit">size-unit</link> </code
> attributes are provided by this specification.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>, <link linkend="datatype"> <code>datatype</code
> </link>, <link linkend="xml_space"> 
 <code>xml:space</code> </link>, <link linkend="ts"
> <code>ts</code> </link>, <link
linkend="restype"> <code>restype</code> 
 </link>, <link linkend="resname"> <code>resname</code
> </link>, <link linkend="extradata"> 
 <code>extradata</code> </link>, <link
linkend="help-id"> <code>help-id</code> 
 </link>, <link linkend="menu"> <code>menu</code
> </link>, <link linkend="menu-option"> 
 <code>menu-option</code> </link> , <link
linkend="menu-name"> <code>menu-name</code> 
 </link>, <link linkend="coord"> <code
>coord</code> </link>, <link linkend="font"> 
 <code>font</code> </link>, <link
linkend="css-style"> <code>css-style</code> 
 </link>, <link linkend="style"> <code
>style</code> </link>, <link linkend="exstyle"> 
 <code>exstyle</code> </link>, <link
linkend="extype"> <code>extype</code> 
 </link>, <link linkend="translate"> <code>translate</code
> </link>, <link linkend="reformat"> 
 <code>reformat</code> </link> , <link
linkend="maxbytes"> <code>maxbytes</code> 
 </link>, <link linkend="minbytes"> <code
>minbytes</code> </link>, <link linkend="size-unit"
> <code>size-unit</code> </link>, <link
linkend="maxheight"> <code>maxheight</code> 
 </link>, <link linkend="minheight"> <code
>minheight</code> </link>, <link linkend="maxwidth"
> <code>maxwidth</code> </link> , <link
linkend="minwidth"> <code>minwidth</code> 
 </link>, <link linkend="charclass"> <code
>charclass</code> </link>, <link linkend="merged-trans"
> <code>merged-trans</code> </link
>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Zero, one or more <link linkend="context-group"> 
 <code>&lt;context-group></code> </link> elements,
followed by Zero, one or more <link linkend="count-group"> 
 <code>&lt;count-group></code> </link> elements,
 followed by Zero, one or more <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link> elements,
 followed by Zero, one or more <link linkend="note"> 
 <code>&lt;note></code> </link> elements,
followed by Zero, one or more non-XLIFF elements, followed by 
Zero, one or more <link linkend="group"> <code>&lt;group></code
> </link>, <link linkend="trans-unit"> 
 <code>&lt;trans-unit></code> </link>, <link
linkend="bin-unit"> <code>&lt;bin-unit></code> 
 </link> elements, in any order.</para>
<para>All <link linkend="context-group"> <code>&lt;context-group></code
> </link>, <link linkend="count-group"> 
 <code>&lt;count-group></code> </link>, <link
linkend="prop-group"> <code>&lt;prop-group></code
> </link>, <link linkend="note"> <code
>&lt;note></code> </link> and non-XLIFF elements 
pertain to the subsequent elements in the tree but can be overridden
within a child element.</para>
<para id="trans-unit"> &lt;trans-unit></para>
<para> <emphasis>Translation unit</emphasis> - The <code>&lt;trans-unit></code
> elements contains a <link linkend="source"> <code
>&lt;source></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
> and associated elements.</para>
<para>The required <code> <link linkend="id">id</link> </code
> attribute is used to uniquely identify the <code>&lt;trans-unit></code
> within all &lt;trans-unit> and <link linkend="bin-unit">&lt;bin-unit></link
> elements within the same <link linkend="file">&lt;file></link
>. The optional <code> <link linkend="approved">approved</link
> </code> attribute indicates whether the translation has been
approved by a reviewer. The optional <code> <link
linkend="translate">translate</link> </code> attribute indicates
 whether the <code>&lt;trans-unit></code> is to be translated. 
The optional <code> <link linkend="reformat">reformat</link> 
 </code> attribute specifies whether and which attributes can be
modified for the <code> <link linkend="target">&lt;target></link
> </code> element of the <code>&lt;trans-unit></code> . The optional <code
> <link linkend="xml_space">xml:space</link> </code> attribute
is used to specify how white-spaces are to be treated within the
 <code>&lt;trans-unit></code>. The optional <code> <link
linkend="datatype">datatype</link> </code> attribute specifies the
data type of the content of the <code>&lt;trans-unit></code>; e.g.
 "winres" for Windows resources. The optional <code> <link
linkend="ts">ts</link> </code> attribute was DEPRECATED in XLIFF
1.1. The optional <code> <link linkend="phase-name">phase-name</link
> </code> attribute references the phase that the <code>&lt;trans-unit></code
> is in. The optional <code> <link linkend="restype">restype</link
> </code>, <code> <link linkend="resname">resname</link> </code
>, <code> <link linkend="extradata">extradata</link> </code
>, <code> <link linkend="help-id">help-id</link> </code>, <code
> <link linkend="menu">menu</link> </code>, <code> <link
linkend="menu-option">menu-option</link> </code>, <code> <link
linkend="menu-name">menu-name</link> </code> , <code> <link
linkend="coord">coord</link> </code>, <code> <link linkend="font"
>font</link> </code>, <code> <link linkend="css-style">css-style</link
> </code>, <code> <link linkend="style">style</link> </code
>, <code> <link linkend="exstyle">exstyle</link> </code>, and <code
> <link linkend="extype">extype</link> </code> attributes describe
the resource contained within the <code>&lt;trans-unit></code>.
The optional <code> <link linkend="maxbytes">maxbytes</link
> </code> and <code> <link linkend="minbytes">minbytes</link
> </code> attributes specify the required maximum and minimum
number of bytes for the text inside the <code> <link
linkend="source">&lt;source></link> </code> and <code> <link
linkend="target">&lt;target></link> </code> elements of the <code
>&lt;trans-unit></code>. The optional <code> <link
linkend="size-unit">size-unit</link> </code> attribute determines
the unit for the optional <code> <link linkend="maxheight">maxheight</link
> </code>, <code> <link linkend="minheight">minheight</link
> </code>, <code> <link linkend="maxwidth">maxwidth</link> 
 </code>, and <code> <link linkend="minwidth">minwidth</link> 
 </code> attributes, which limit the size of the resource described
by the <code>&lt;trans-unit></code>. The optional <code> <link
linkend="charclass">charclass</link> </code> attribute restricts
all <code> <link linkend="source">&lt;source></link> </code
> and <code> <link linkend="target">&lt;target></link> </code
> text in the scope of the <code>&lt;trans-unit></code> to a subset
of characters. Lists of values for the <code> <link
linkend="datatype">datatype</link> </code>, <code> <link
linkend="restype">restype</link> </code>, and <code> <link
linkend="size-unit">size-unit</link> </code> attributes are provided
by this specification. During translation the content of the <link
linkend="source"> <code>&lt;source></code> 
 </link> element may be duplicated into a <link
linkend="seg-source"> <code>&lt;seg-source></code
> </link> element, in which additional segmentation
related markup is introduced. See the <link
linkend="Struct_Segmentation">Segmentation</link> section for more
 information.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="approved"> <code>approved</code> 
 </link>, <link linkend="translate"> <code
>translate</code> </link>, <link linkend="reformat"
> <code>reformat</code> </link>, <link
linkend="xml_space"> <code>xml:space</code> 
 </link> , <link linkend="datatype"> <code
>datatype</code> </link>, <link linkend="ts"> 
 <code>ts</code> </link>, <link
linkend="phase-name"> <code>phase-name</code> 
 </link> , <link linkend="restype"> <code
>restype</code> </link>, <link linkend="resname"> 
 <code>resname</code> </link>, <link
linkend="extradata"> <code>extradata</code> 
 </link> , <link linkend="help-id"> <code
>help-id</code> </link>, <link linkend="menu"> 
 <code>menu</code> </link>, <link
linkend="menu-option"> <code>menu-option</code> 
 </link> , <link linkend="menu-name"> 
 <code>menu-name</code> </link>, <link linkend="coord"
> <code>coord</code> </link>, <link
linkend="font"> <code>font</code> 
 </link>, <link linkend="css-style"> <code>css-style</code
> </link>, <link linkend="style"> 
 <code>style</code> </link>, <link linkend="exstyle"
> <code>exstyle</code> </link>, <link
linkend="extype"> <code>extype</code> 
 </link>, <link linkend="maxbytes"> <code>maxbytes</code
> </link>, <link linkend="minbytes"> 
 <code>minbytes</code> </link> , <link
linkend="size-unit"> <code>size-unit</code> 
 </link>, <link linkend="maxheight"> <code
>maxheight</code> </link>, <link linkend="minheight"
> <code>minheight</code> </link>, <link
linkend="maxwidth"> <code>maxwidth</code> 
 </link>, <link linkend="minwidth"> <code
>minwidth</code> </link> , <link linkend="charclass"
> <code>charclass</code> </link>,
non-XLIFF attributes</para>
<para>Contents:</para>
<para>One <link linkend="source"> <code>&lt;source></code
> </link> element, followed by Zero or one <link
linkend="seg-source"> <code>&lt;seg-source></code
> </link> element, followed by Zero or one <link
linkend="target"> <code>&lt;target></code> 
 </link> element, followed by Zero, one or more <link
linkend="context-group"> <code>&lt;context-group></code
> </link>, <link linkend="count-group"> 
 <code>&lt;count-group></code> </link>, <link
linkend="prop-group"> <code>&lt;prop-group></code
> </link>, <link linkend="note"> <code
>&lt;note></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
> elements, in any order, followed by Zero, one or more non-XLIFF
elements.</para>
<para>All child elements of <code>&lt;trans-unit></code> pertain
to their sibling <code> <link linkend="source">&lt;source></link
> </code> element. While for backward compatibility reasons no
order is enforced for the elements before the non-XLIFF elements,
the recommended order is the one in which they are listed here.</para>
<para id="source"> &lt;source></para>
<para> <emphasis>Source text</emphasis> - The <code>&lt;source></code
> element is used to delimit a unit of text that could be a paragraph,
a title, a menu item, a caption, etc. The content of the <code>&lt;source></code
> is generally the translatable text, depending upon the translate
attribute of the parent <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>. The optional <code> <link linkend="xml_lang">xml:lang</link
> </code> attribute is used to specify the content language of
the <code>&lt;source></code>; this should always match <code> 
 <link linkend="source-language">source-language</link> </code
> as a child of <code>&lt;trans-unit></code> but can vary as a child
of <code>&lt;alt-trans></code>. The optional <code> <link
linkend="ts">ts</link> </code> attribute was DEPRECATED in XLIFF
1.1.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="xml_lang"> <code>xml:lang</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link>, <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link> , <link
linkend="ept"> <code>&lt;ept></code> 
 </link>, <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link> , <link linkend="mrk"> 
 <code>&lt;mrk></code> </link>, in any
order.</para>
<para id="target"> &lt;target></para>
<para> <emphasis>Target</emphasis> - The <code>&lt;target></code
> element contains the translation of the content of the sibling
 <code> <link linkend="source">&lt;source></link> </code> element.
The optional <code> <link linkend="state">state</link> </code
> and <code> <link linkend="state-qualifier">state-qualifier</link
> </code> attributes indicate in which state the <code>&lt;target></code
> is. The optional <code> <link linkend="phase-name">phase-name</link
> </code> attribute references the <code> <link linkend="phase"
>&lt;phase></link> </code> in which the <code>&lt;target></code
> was last modified. The optional <code> <link linkend="xml_lang"
>xml:lang</link> </code> attribute is used to specify the content
language of the <code>&lt;target></code>; this should always match <code
> <link linkend="target-language">target-language</link> </code
> as a child of <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> but can vary as a child of <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> . The optional
 <code> <link linkend="coord">coord</link> </code>, <code> 
 <link linkend="font">font</link> </code>, <code> <link
linkend="css-style">css-style</link> </code>, <code> <link
linkend="style">style</link> </code>, and <code> <link
linkend="exstyle">exstyle</link> </code> attributes describe the
resource contained within the <code>&lt;target></code>; these are
the modifiable attributes for the <code> <link linkend="trans-unit"
>&lt;trans-unit></link> </code> depending upon the <code> <link
linkend="reformat">reformat</link> </code> attribute of the parent <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code>.
 The optional <link linkend="equiv-trans"> <code>equiv-trans</code
> </link> describes if the target language translation is
a direct equivalent of the source text. The optional <code> <link
linkend="ts">ts</link> </code> attribute was DEPRECATED in XLIFF
1.1. The <link linkend="restype"> <code>restype</code
> </link> attribute is DEPRECATED in XLIFF 1.2, since <code
>&lt;target></code> will always be of the same <link linkend="restype"
> <code>restype</code> </link> as
its parent <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> or <link linkend="alt-trans"> <code
>&lt;alt-trans></code> </link>. A list of preferred
values for the <code> <link linkend="restype">restype</link> 
 </code>, <code> <link linkend="state">state</link> </code>,
and <code> <link linkend="state-qualifier">state-qualifier</link
> </code> attributes are provided by this specification.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="state"> <code>state</code> 
 </link>, <link linkend="state-qualifier"> <code
>state-qualifier</code> </link>, <link
linkend="phase-name"> <code>phase-name</code> 
 </link>, <link linkend="xml_lang"> <code
>xml:lang</code> </link>, <link linkend="ts"> 
 <code>ts</code> </link>, <link
linkend="restype"> <code>restype</code> 
 </link>, <link linkend="resname"> <code>resname</code
> </link>, <link linkend="coord"> 
 <code>coord</code> </link>, <link linkend="font"> 
 <code>font</code> </link>, <link
linkend="css-style"> <code>css-style</code> 
 </link>, <link linkend="style"> <code
>style</code> </link>, <link linkend="exstyle"> 
 <code>exstyle</code> </link>, <link
linkend="equiv-trans"> <code>equiv-trans</code> 
 </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link>, <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link> , <link
linkend="ept"> <code>&lt;ept></code> 
 </link>, <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link> , <link linkend="mrk"> 
 <code>&lt;mrk></code> </link>, in any
order.</para>
<para id="alt-trans"> &lt;alt-trans></para>
<para> <emphasis>Translation match</emphasis> - The <code>&lt;alt-trans></code
> element contains possible translations in <code> <link
linkend="target">&lt;target></link> </code> elements along with
optional context, notes, etc. The optional <code> <link
linkend="mid">mid</link> </code> attribute indicates that the <code
>&lt;alt-trans></code> applies only to a specific <code> <link
linkend="mrk">&lt;mrk</link> <link linkend="mtype">mtype</link
>="seg"></code> segment in the <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> element of the <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code>. (See the <link
linkend="Struct_Segmentation">Segmentation</link> section for further
details.) The optional <code> <link linkend="match-quality">match-quality</link
> </code> attribute provides a value indicating the exactness
of the match between the <code> <link linkend="source">&lt;source></link
> </code> of the <code> <link linkend="alt-trans">&lt;alt-trans></link
> </code> and that of the <code> <link linkend="source">&lt;source></link
> </code> element of the parent <code> <link linkend="trans-unit"
>&lt;trans-unit></link> </code>; e.g. "90%". The optional <code
> <link linkend="tool-id">tool-id</link> </code> attribute accepts
the id of the <code> <link linkend="tool">&lt;tool></link> 
 </code> used to generate this <code>&lt;alt-trans></code>. The
optional <code> <link linkend="crc">crc</link> </code> attribute
allows a verification of the data. The optional <code> <link
linkend="xml_lang">xml:lang</link> </code> attribute is used to
specify the content language of the <code>&lt;alt-trans></code>.
The optional <code> <link linkend="xml_space">xml:space</link
> </code> attribute is used to specify how white-spaces are to
be treated within the <code>&lt;alt-trans></code>. The optional <code
> <link linkend="datatype">datatype</link> </code> attribute
specifies the data type of the content of the <code>&lt;alt-trans></code
>; e.g. "<code>winres</code>" for Windows resources. The optional
 <code> <link linkend="restype">restype</link> </code>, <code
> <link linkend="resname">resname</link> </code>, <code> 
 <link linkend="extradata">extradata</link> </code>, <code> <link
linkend="help-id">help-id</link> </code>, <code> <link
linkend="menu">menu</link> </code>, <code> <link
linkend="menu-option">menu-option</link> </code>, <code> <link
linkend="menu-name">menu-name</link> </code>, <code> <link
linkend="coord">coord</link> </code>, <code> <link linkend="font"
>font</link> </code>, <code> <link linkend="css-style">css-style</link
> </code>, <code> <link linkend="style">style</link> </code
>, <code> <link linkend="exstyle">exstyle</link> </code>, and <code
> <link linkend="extype">extype</link> </code> attributes describe
the resource contained within the <code>&lt;alt-trans></code>. The
optional <code> <link linkend="origin">origin</link> </code
> attribute specifies where the alternate translation comes from;
e.g. a previous version of the product. The <code> <link
linkend="tool">tool</link> </code> and <code> <link linkend="ts"
>ts</link> </code> attributes were DEPRECATED in XLIFF 1.1. Multiple <link
linkend="target"> <code>&lt;target></code> 
 </link> elements within a single <code>&lt;alt-trans></code
> are DEPRECATED in XLIFF 1.2. A list of values for the <code> 
 <link linkend="datatype">datatype</link> </code> and <code> 
 <link linkend="restype">restype</link> </code> attributes are
provided by this specification.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="mid"> <code>mid</code> </link
>, <link linkend="match-quality"> <code>match-quality</code
> </link>, <code> <link linkend="tool">tool</link
> </code>, <code> <link linkend="tool-id">tool-id</link> </code
> , <link linkend="crc"> <code>crc</code> 
 </link>, <link linkend="xml_lang"> <code
>xml:lang</code> </link>, <link linkend="datatype"
> <code>datatype</code> </link> , <link
linkend="xml_space"> <code>xml:space</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, <link linkend="restype"> 
 <code>restype</code> </link>, <link linkend="resname"
> <code>resname</code> </link>, <link
linkend="extradata"> <code>extradata</code> 
 </link>, <link linkend="help-id"> <code
>help-id</code> </link> , <link linkend="menu"> 
 <code>menu</code> </link>, <link
linkend="menu-option"> <code>menu-option</code> 
 </link>, <link linkend="menu-name"> 
 <code>menu-name</code> </link>, <link linkend="coord"
> <code>coord</code> </link>, <link
linkend="font"> <code>font</code> 
 </link>, <link linkend="css-style"> <code>css-style</code
> </link>, <link linkend="style"> 
 <code>style</code> </link>, <link linkend="exstyle"
> <code>exstyle</code> </link>, <link
linkend="extype"> <code>extype</code> 
 </link>, <link linkend="origin"> <code>origin</code
> </link>, <link linkend="phase-name"> 
 <code>phase-name</code> </link> , <link
linkend="alttranstype"> <code>alttranstype</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Zero or one <link linkend="source"> <code
>&lt;source></code> </link> element, followed by
 Zero or one <link linkend="seg-source"> <code
>&lt;seg-source></code> </link> element, followed
by One <link linkend="target"> <code>&lt;target></code
> </link> element, followed by Zero, one or more <link
linkend="context-group"> <code>&lt;context-group></code
> </link>, <link linkend="prop-group"> 
 <code>&lt;prop-group></code> </link>, <link
linkend="note"> <code>&lt;note></code> 
 </link> elements, in any order, followed by Zero, one or
more non-XLIFF elements.</para>
<para>All child elements of <code>&lt;alt-trans></code> pertain
to their sibling <code> <link linkend="target">&lt;target></link
> </code> element. While for backward compatibility reasons no
order is enforced for the elements before the non-XLIFF elements,
the recommended order is the one in which they are listed here.
 Although not enforced, it is recommended to adopt the convention
 that more recent <code>&lt;alt-trans></code> elements appear before
older ones in order to define the order that changes are introduced.</para>
<para id="bin-unit"> &lt;bin-unit></para>
<para> <emphasis>Binary unit</emphasis> - The <code>&lt;bin-unit></code
> element contains a binary object that may or may not be translatable.
The required <code> <link linkend="id">id</link> </code> attribute
is used to uniquely identify the <code>&lt;bin-unit></code> within
all <link linkend="trans-unit">&lt;trans-unit></link> and &lt;bin-unit>
 elements within the same <link linkend="file">&lt;file></link>.
The required <code> <link linkend="mime-type">mime-type</link
> </code> attribute specifies the data type of the binary object
based on <link linkend="refRFC1341">RFC 1341</link>. The optional <code
> <link linkend="approved">approved</link> </code> attribute
indicates whether the translation has been approved by a reviewer.
The optional <code> <link linkend="translate">translate</link
> </code> attribute indicates whether the <code> <link
linkend="bin-unit">&lt;bin-unit></link> </code> is to be translated.
The optional <code> <link linkend="reformat">reformat</link> 
 </code> attribute specifies whether and which attributes can be
modified for the <code> <link linkend="bin-target">&lt;bin-target></link
> </code> element of the <code>&lt;bin-unit></code>. The optional <code
> <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1. The optional <code> <link linkend="phase-name"
>phase-name</link> </code> attribute references the phase that
the <code>&lt;bin-unit></code> is in. The optional <code> <link
linkend="restype">restype</link> </code> and <code> <link
linkend="resname">resname</link> </code> attributes describe the
resource contained within the <code>&lt;bin-unit></code>. A list
of values for the <code> <link linkend="restype">restype</link
> </code> attribute is provided by this specification.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>, <link linkend="mime-type"> <code>mime-type</code
> </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="approved"> <code>approved</code> 
 </link>, <link linkend="translate"> <code
>translate</code> </link>, <link linkend="reformat"
> <code>reformat</code> </link>, <link
linkend="ts"> <code>ts</code> </link
>, <link linkend="phase-name"> <code>phase-name</code
> </link>, <link linkend="restype"> 
 <code>restype</code> </link>, <link linkend="resname"
> <code>resname</code> </link>, non-XLIFF
attributes</para>
<para>Contents:</para>
<para>One<link linkend="bin-source"> <code>&lt;bin-source></code
> </link> element, followed by Zero or one <link
linkend="bin-target"> <code>&lt;bin-target></code
> </link> element, followed by Zero, one or more <link
linkend="context-group"> <code>&lt;context-group></code
> </link>, <link linkend="count-group"> 
 <code>&lt;count-group></code> </link>, <link
linkend="prop-group"> <code>&lt;prop-group></code
> </link>, <link linkend="note"> <code
>&lt;note></code> </link>, <link linkend="trans-unit"
> <code>&lt;trans-unit></code> </link
> elements, in any order, followed by Zero, one or more non-XLIFF
elements.</para>
<para>All child elements of <code>&lt;bin-unit></code> pertain to
their sibling <code> <link linkend="bin-source">&lt;bin-source></link
> </code> element. While for backward compatibility reasons no
order is enforced for the elements before the non-XLIFF elements,
the recommended order is the one in which they are listed here.</para>
<para id="bin-source"> &lt;bin-source></para>
<para> <emphasis>Binary source</emphasis> -The <code>&lt;bin-source></code
> element is the container for the binary source data. The optional <code
> <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="ts"> <code>ts</code> </link
>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>One of <link linkend="internal-file"> <code
>&lt;internal-file></code> </link> or <link
linkend="external-file"> <code>&lt;external-file></code
> </link>.</para>
<para id="bin-target"> &lt;bin-target></para>
<para> <emphasis>Binary target</emphasis> -The <code>&lt;bin-target></code
> element is the container for the translated version of the binary
data. The optional <code> <link linkend="mime-type">mime-type</link
> </code> attribute specifies the data type of the binary object
based on <link linkend="refRFC1341">RFC 1341</link>. The optional <code
> <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1. The optional <code> <link linkend="state">state</link
> </code> and <code> <link linkend="state-qualifier">state-qualifier</link
> </code> attributes indicate in which state the <code>&lt;bin-target></code
> is. The optional <code> <link linkend="phase-name">phase-name</link
> </code> attribute references the phase that the <code>&lt;bin-target></code
> is in. The optional <code> <link linkend="restype">restype</link
> </code> and <code> <link linkend="resname">resname</link> 
 </code> attributes describe the resource contained within the <code
>&lt;bin-target></code>. A list of values for the <code> <link
linkend="restype">restype</link> </code>, <code> <link
linkend="state">state</link> </code>, and <code> <link
linkend="state-qualifier">state-qualifier</link> </code> attributes
are provided by this specification.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="mime-type"> <code>mime-type</code
> </link>, <link linkend="ts"> <code>ts</code
> </link>, <link linkend="state"> 
 <code>state</code> </link>, <link linkend="phase-name"
> <code>phase-name</code> </link
> , <link linkend="restype"> <code>restype</code
> </link>, <link linkend="resname"> 
 <code>resname</code> </link>, <link
linkend="state-qualifier"> <code>state-qualifier</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>One of <link linkend="internal-file"> <code
>&lt;internal-file></code> </link> or <link
linkend="external-file"> <code>&lt;external-file></code
> </link>.</para>
<para id="seg-source"> &lt;seg-source></para>
<para> <emphasis>Source text</emphasis> - The <code>&lt;seg-source></code
> element is used to maintain a working copy of the <code> <link
linkend="source">&lt;source></link> </code> element, where markup
such as segmentation can be introduced without affecting the actual
 <code> <link linkend="source">&lt;source></link> </code> element
content. The content of the <code>&lt;seg-source></code> is generally
the translatable text, typically divided into segments through the
use of <code> <link linkend="mrk">&lt;mrk</link> <link
linkend="mtype">mtype</link>="seg"></code> elements. See the <link
linkend="Struct_Segmentation">Segmentation</link> section for more
information. As with the <code> <link linkend="source">&lt;source></link
> </code> element, the optional <code> <link linkend="xml_lang"
>xml:lang</link> </code> attribute is used to specify the content
language of the <code>&lt;seg-source></code>; this should always
match <code> <link linkend="source-language">source-language</link
> </code> as a child of <code> <link linkend="trans-unit"
>&lt;trans-unit></link> </code> but can vary as a child of <code
> <link linkend="alt-trans">&lt;alt-trans></link> </code>. The
optional <code> <link linkend="ts">ts</link> </code> attribute
was DEPRECATED in XLIFF 1.1.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="xml_lang"> <code>xml:lang</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link>, <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link> , <link
linkend="ept"> <code>&lt;ept></code> 
 </link>, <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link> , <link linkend="mrk"> 
 <code>&lt;mrk></code> </link>, in any
order.</para>
</section>
<section>
<title id="Specs_Elem_Inline">Inline Elements</title>
<para>The inline elements are the elements that can appear inside
the <link linkend="source"> <code>&lt;source></code
> </link> and <code> <link linkend="target">&lt;target></link
> </code> elements. They enclose or replace any formatting or
control code that is not text, but resides within the text unit.</para>
<para id="g"> &lt;g></para>
<para> <emphasis>Generic group placeholder</emphasis> - The <code
>&lt;g></code> element is used to replace any inline code of the
original document that has a beginning and an end, does not overlap
other paired inline codes, and can be moved within its parent structural
element. The required <code> <link linkend="id">id</link> </code
> attribute is used to reference the replaced code in the skeleton
file. The optional <link linkend="ctype"> <code
>ctype</code> </link> attribute allows you to specify
what kind of attribute the placeholder represents; e.g. "bold".
The optional <code> <link linkend="ts">ts</link> </code> attribute
was DEPRECATED in XLIFF 1.1. The optional <code> <link
linkend="clone">clone</link> </code> attribute indicates whether
this <code>&lt;g></code> element may be duplicated. The optional
 <code> <link linkend="xid">xid</link> </code> attribute references
a <code> <link linkend="trans-unit">&lt;trans-unit></link> </code
> or <code> <link linkend="bin-unit">&lt;bin-unit></link> </code
>, through its <code> <link linkend="id">id</link> </code> attribute
value, which can contain any translatable text from the replaced
code. A list of values for the <code> <link linkend="ctype"
>ctype</link> </code> attribute is available. The optional <link
linkend="equiv-text">equiv-text</link> attribute specifies text
to substitute in place of the inline tag. A <code>&lt;g></code> element
can contain another <code>&lt;g></code> element.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code> 
 </link>, <link linkend="clone"> <code
>clone</code> </link>, <code> <link linkend="xid"
>xid</link> </code>, <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> , <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link>, <link
linkend="ept"> <code>&lt;ept></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link>, <link linkend="mrk"> 
 <code>&lt;mrk></code> </link> , in any
order.</para>
<para id="x"> &lt;x/></para>
<para> <emphasis>Generic placeholder</emphasis> - The <code>&lt;x/></code
> element is used to replace any code of the original document.
The required <code> <link linkend="id">id</link> </code> attribute
is used to reference the replaced code in the skeleton file. The
optional <link linkend="ctype"> <code>ctype</code
> </link> attribute allows you to specify what kind
of attribute the placeholder represents; e.g. "bold". The optional
 <code> <link linkend="ts">ts</link> </code> attribute was
DEPRECATED in XLIFF 1.1. The optional <code> <link linkend="clone"
>clone</link> </code> attribute indicates whether this <code>&lt;x/></code
> element may be duplicated. The optional <code> <link
linkend="xid">xid</link> </code> attribute references a <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code> or <code
> <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute value,
which can contain any translatable text from the replaced code.
A list of values for the <code> <link linkend="ctype">ctype</link
> </code> attribute is provided by this specification. The optional <link
linkend="equiv-text">equiv-text</link> attribute specifies text to
 substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code> 
 </link>, <link linkend="clone"> <code
>clone</code> </link>, <code> <link linkend="xid"
>xid</link> </code>., <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Empty.</para>
<para id="bx"> &lt;bx/></para>
<para> <emphasis>Begin paired placeholder</emphasis> - The <code
>&lt;bx/></code> element is used to replace a beginning paired code
of the original document. It should be used for paired codes that
do not follow XML well-formedness rules (i.e. no overlapping elements).
If the paired codes follow that rule, it is strongly recommended
that the <link linkend="g"> <code>&lt;g></code> 
 </link> element is used because it simplifies processing.
The <code>&lt;bx/></code> element should be followed by a matching <link
linkend="ex"> <code>&lt;ex/></code> 
 </link> element. These paired elements are related via their <code
> <link linkend="rid">rid</link> </code> attributes. If the <code
> <link linkend="rid">rid</link> </code> attribute is not
present (in a 1.0 document for example), the attribute <code> <link
linkend="id">id</link> </code> is used to match both tags. The required
 <code> <link linkend="id">id</link> </code> attribute is used
to reference the replaced code in the skeleton file. The optional <link
linkend="ctype"> <code>ctype</code> 
 </link> attribute allows you to specify what kind of attribute
the placeholder represents; e.g. "bold". The optional <code> 
 <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1. The optional <code> <link linkend="clone">clone</link
> </code> attribute indicates whether this <code>&lt;bx/></code
> element may be duplicated. The optional <code> <link
linkend="xid">xid</link> </code> attribute references a <code> 
 <link linkend="trans-unit">&lt;trans-unit></link> </code> or <code
> <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute value,
which can contain any translatable text from the replaced code.
A list of values for the <code> <link linkend="ctype">ctype</link
> </code> attribute is provided by this specification. The optional <link
linkend="equiv-text">equiv-text</link> attribute specifies text to
 substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="rid"> <code>rid</code> </link
>, <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, <link linkend="clone"> 
 <code>clone</code> </link>, <code> <link
linkend="xid">xid</link> </code>., <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF
 attributes</para>
<para>Contents:</para>
<para>Empty.</para>
<para id="ex"> &lt;ex/></para>
<para> <emphasis>End paired placeholder</emphasis> - The <code
>&lt;ex/></code> element is used to replace an ending paired code
of the original document. It should be used for paired codes that
do not follow XML well-formedness rules (i.e. no overlapping elements).
If the paired codes follow that rule, it is strongly recommended
that the <link linkend="g"> <code>&lt;g></code> 
 </link> element is used because it simplifies processing.
The <code>&lt;ex/></code> element should be preceded by a matching <link
linkend="bx"> <code>&lt;bx/></code> 
 </link> element. These paired elements are related via their <code
> <link linkend="rid">rid</link> </code> attributes. If the <code
> <link linkend="rid">rid</link> </code> attribute is not
present (in a 1.0 document for example), the attribute <code> <link
linkend="id">id</link> </code> is used to match both tags. The required
 <code> <link linkend="id">id</link> </code> attribute is used
to reference the replaced code in the skeleton file. The optional <code
> <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1. The optional <code> <link linkend="xid">xid</link
> </code> attribute references a <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> or <code> 
 <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute
value, which can contain any translatable text from the replaced
code. The optional <link linkend="equiv-text">equiv-text</link> attribute
specifies text to substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="rid"> <code>rid</code> </link
>, <link linkend="ts"> <code>ts</code> 
 </link>, <code> <link linkend="xid">xid</link> </code
>., <link linkend="equiv-text"> <code>equiv-text</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Empty.</para>
<para id="ph"> &lt;ph></para>
<para> <emphasis>Placeholder</emphasis> - The <code>&lt;ph></code
> element is used to delimit a sequence of native stand-alone codes
 in the translation unit. The required <code> <link linkend="id"
>id</link> </code> attribute is used to identify the <code>&lt;ph></code
> inline code. The optional <link linkend="ctype"> 
 <code>ctype</code> </link> attribute allows you
to specify what kind of attribute the placeholder represents; e.g.
 "bold". The optional <code> <link linkend="ts">ts</link> </code
> attribute was DEPRECATED in XLIFF 1.1. The optional <code> 
 <link linkend="crc">crc</link> </code> attribute allows a verification
of the data. The optional <code> <link linkend="assoc">assoc</link
> </code> attribute specifies whether this placeholder code is
associated with the text prior or after. The optional <code> 
 <link linkend="xid">xid</link> </code> attribute references a <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code> or <code
> <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute value,
which can contain any translatable text from the replaced code.
A list of values for the <code> <link linkend="ctype">ctype</link
> </code> attribute is provided by this specification. The optional <link
linkend="equiv-text">equiv-text</link> attribute specifies text to
 substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code> 
 </link>, <link linkend="crc"> <code
>crc</code> </link>, <link linkend="assoc"> 
 <code>assoc</code> </link>, <code> <link
linkend="xid">xid</link> </code> ., <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF
 attributes</para>
<para>Contents:</para>
<para>Code data, Zero, one or more <link linkend="sub"> 
 <code>&lt;sub></code> </link> elements.</para>
<para id="bpt">&lt;bpt></para>
<para> <emphasis>Begin paired tag</emphasis> - The <code>&lt;bpt></code
> element is used to delimit the beginning of a paired sequence
of native codes. Each <code>&lt;bpt></code> has a corresponding <link
linkend="ept"> <code>&lt;ept></code> 
 </link> element within the translation unit. These paired elements
are related via their <code> <link linkend="rid">rid</link> 
 </code> attributes. If the <code> <link linkend="rid">rid</link
> </code> attribute is not present (in a 1.0 document for example),
the attribute <code> <link linkend="id">id</link> </code> is
used to match both tags. The required <code> <link linkend="id"
>id</link> </code> attribute is used to identify the <code>&lt;bpt></code
> inline code. The optional <link linkend="ctype"> 
 <code>ctype</code> </link> attribute allows you
to specify what kind of attribute the code represents; e.g. "bold".
The optional <code> <link linkend="ts">ts</link> </code> attribute
was DEPRECATED in XLIFF 1.1. The optional <code> <link linkend="crc"
>crc</link> </code> attribute allows a verification of the data.
The optional <code> <link linkend="xid">xid</link> </code> attribute
 references a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> or <code> <link linkend="bin-unit">&lt;bin-unit></link
> </code>, through its <code> <link linkend="id">id</link> 
 </code> attribute value, which can contain any translatable text
from the inline code. A list of values for the <code> <link
linkend="ctype">ctype</link> </code> attribute is provided by 
this specification. The optional <link linkend="equiv-text">equiv-text</link
> attribute specifies text to substitute in place of the inline
tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="rid"> <code>rid</code> </link
>, <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, <link linkend="crc"> <code
>crc</code> </link>, <code> <link linkend="xid"
>xid</link> </code>., <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Code data, Zero, one or more <link linkend="sub"> 
 <code>&lt;sub></code> </link> elements.</para>
<para id="ept">&lt;ept></para>
<para> <emphasis>End paired tag</emphasis> - The <code>&lt;ept></code
> element is used to delimit the end of a paired sequence of native
codes. Each <code>&lt;ept></code> has a corresponding <link
linkend="bpt"> <code>&lt;bpt></code> 
 </link> element within the translation unit. These paired elements
are related via their <code> <link linkend="rid">rid</link> 
 </code> attributes. If the <code> <link linkend="rid">rid</link
> </code> attribute is not present (in a 1.0 document for example),
the attribute <code> <link linkend="id">id</link> </code> is
used to match both tags. The required <code> <link linkend="id"
>id</link> </code> attribute is used to identify the <code>&lt;ept></code
> inline code. The optional <code> <link linkend="ts">ts</link
> </code> attribute was DEPRECATED in XLIFF 1.1. The optional <code
> <link linkend="crc">crc</link> </code> attribute allows a
 verification of the data. The optional <code> <link linkend="xid"
>xid</link> </code> attribute references a <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> or <code> 
 <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute value,
which can contain any translatable text from the inline code. The
optional <link linkend="equiv-text">equiv-text</link> attribute specifies
text to substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>.</para>
<para>Optional attributes:</para>
<para> <link linkend="rid"> <code>rid</code> </link
>, <link linkend="ts"> <code>ts</code> 
 </link>, <link linkend="crc"> <code>crc</code
> </link>, <code> <link linkend="xid">xid</link
> </code>., <link linkend="equiv-text"> <code
>equiv-text</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Code data, Zero, one or more <link linkend="sub"> 
 <code>&lt;sub></code> </link> elements.</para>
<para id="it">&lt;it></para>
<para> <emphasis>Isolated tag</emphasis> - The <code>&lt;it></code
> element is used to delimit a beginning/ending sequence of native
 codes that does not have its corresponding ending/beginning within
 the translation unit. The required <code> <link linkend="id"
>id</link> </code> attribute is used to identify the <code>&lt;it></code
> inline code. The required <code> <link linkend="pos">pos</link
> </code> attribute specifies whether this is the begin or end
code. The optional <link linkend="ctype"> <code
>ctype</code> </link> attribute allows you to specify
what kind of attribute the code represents; e.g. "bold". The optional <code
> <link linkend="ts">ts</link> </code> attribute was DEPRECATED
in XLIFF 1.1. The optional <code> <link linkend="crc">crc</link
> </code> attribute allows a verification of the data. The optional <code
> <link linkend="xid">xid</link> </code> attribute references
a <code> <link linkend="trans-unit">&lt;trans-unit></link> </code
> or <code> <link linkend="bin-unit">&lt;bin-unit></link> </code
>, through its <code> <link linkend="id">id</link> </code> attribute
value, which can contain any translatable text from the inline code.
A list of values for the <code> <link linkend="ctype">ctype</link
> </code> attribute is provided by this specification. The optional <link
linkend="equiv-text">equiv-text</link> attribute specifies text to
 substitute in place of the inline tag.</para>
<para>Required attributes:</para>
<para> <link linkend="id"> <code>id</code> </link
>, <code> <link linkend="pos">pos</link> </code>.</para>
<para>Optional attributes:</para>
<para> <link linkend="rid"> <code>rid</code> </link
>, <link linkend="ctype"> <code>ctype</code> 
 </link>, <link linkend="ts"> <code>ts</code
> </link>, <link linkend="crc"> <code
>crc</code> </link>, <code> <link linkend="xid"
>xid</link> </code>., <link linkend="equiv-text"> 
 <code>equiv-text</code> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Code data, Zero, one or more <link linkend="sub"> 
 <code>&lt;sub></code> </link> elements.</para>
<para id="sub">&lt;sub></para>
<para> <emphasis>Sub-flow</emphasis> - The <code>&lt;sub></code
> element is used to delimit sub-flow text inside a sequence of
 native code, for example: the definition of a footnote or the text
 of a <code>title</code> attribute in a HTML <code>&lt;a></code> 
 element. The optional <code> <link linkend="datatype">datatype</link
> </code> attribute specifies the data type of the content of
the <code>&lt;sub></code>; e.g. "html". The optional <link
linkend="ctype"> <code>ctype</code> 
 </link> attribute allows you to specify what kind of attribute
the code represents. The optional <code> <link linkend="xid"
>xid</link> </code> attribute references a <code> <link
linkend="trans-unit">&lt;trans-unit></link> </code> or <code> 
 <link linkend="bin-unit">&lt;bin-unit></link> </code>, through
its <code> <link linkend="id">id</link> </code> attribute value,
which can contain any translatable text from the inline code. Lists
of values for the <link linkend="ctype"> <code>ctype</code
> </link> and <code> <link linkend="datatype">datatype</link
> </code> attributes are provided by this specification.</para>
<para>Required attributes:</para>
<para>None.</para>
<para>Optional attributes:</para>
<para> <link linkend="datatype"> <code>datatype</code> 
 </link>, <link linkend="ctype"> <code>ctype</code
> </link>, <code> <link linkend="xid">xid</link
> </code> .</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> , <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link>, <link
linkend="ept"> <code>&lt;ept></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link>, <link linkend="mrk"> 
 <code>&lt;mrk></code> </link> , in any
order.</para>
</section>
<section>
<title id="Specs_Elem_Delim">Delimiter Element</title>
<para>XLIFF defines an additional element to support various types
of text processing. This element is usually not generated by the
extraction module and is ignored most of the time during merging,
but it can be very powerful with tools such as Machine Translation,
glossary handling, quality assurance, etc.</para>
<para id="mrk"> &lt;mrk></para>
<para> <emphasis>Marker</emphasis> - The <code>&lt;mrk></code> 
 element delimits a section of text that has special meaning, such
 as a terminological unit, a proper name, an item that should not
be modified, etc. It can be used for various processing tasks. For
 example: to indicate to a Machine Translation tool proper names
 that should not be translated; for terminology verification; to
 mark suspect expressions after a grammar checking. The <code>&lt;mrk></code
> element is usually not generated by the extraction tool and it
is not part of the tags used to merge the XLIFF file back into its
original format. The required <code> <link linkend="mtype">mtype</link
> </code> attribute specifies what is being delimited; e.g. "abbrev"
for an abbreviation. The optional <code> <link linkend="ts"
>ts</link> </code> attribute was DEPRECATED in XLIFF 1.1. The
optional <code> <link linkend="comment">comment</link> </code
> attribute allow a free-form comment to be entered. A list of values
for the <code> <link linkend="mtype">mtype</link> </code> attribute
is provided by this specification. The <code>&lt;mrk></code> element
can be used to delimit segments as described in the <link
linkend="Struct_Segmentation">Segmentation</link> section.</para>
<para>Required attributes:s</para>
<para> <link linkend="mtype"> <code>mtype</code> 
 </link>.</para>
<para>Optional attributes:</para>
<para> <link linkend="mid"> <code>mid</code> </link
>, <link linkend="ts"> <code>ts</code> 
 </link>, <link linkend="comment"> <code>comment</code
> </link>, non-XLIFF attributes</para>
<para>Contents:</para>
<para>Text, Zero, one or more of the following elements: <link
linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> , <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link>, <link
linkend="ept"> <code>&lt;ept></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link>, <link linkend="mrk"> 
 <code>&lt;mrk></code> </link> , in any
order.</para>
</section>
</section>
<section>
<title id="Specs_Attr">Attributes</title>
<para>This section lists the various attributes used in the XLIFF
elements. An attribute is never specified more than once for each
element. Along with some of the attributes is the list of their
possible values. </para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <link linkend="Specs_Attr">XLIFF attributes</link> </entry>
<entry> <link linkend="alttranstype"> 
 <code>alttranstype</code> </link>, <code
> <link linkend="annotates">annotates</link> </code>, <link
linkend="approved"> <code>approved</code
> </link>, <link linkend="assoc"> 
 <code>assoc</code> </link
>, <link linkend="build-num"> <code>build-num</code
> </link>, <link linkend="ctype"> 
 <code>ctype</code> </link
>, <link linkend="category"> <code>category</code
> </link>, <link linkend="charclass"> 
 <code>charclass</code> 
 </link>, <link linkend="comment"> <code
>comment</code> </link>, <link
linkend="company-name"> <code>company-name</code
> </link>, <link linkend="contact-email"> 
 <code>contact-email</code> 
 </link> , <link linkend="contact-name"> 
 <code>contact-name</code> </link
> , <link linkend="contact-phone"> <code
>contact-phone</code> </link> , <code> <link
linkend="context-type">context-type</link> </code> , <link
linkend="coord"> <code>coord</code> 
 </link>, <link linkend="count-type"> 
 <code>count-type</code> 
 </link>, <link linkend="crc"> <code>crc</code
> </link>, <link linkend="css-style"> 
 <code>css-style</code> 
 </link>, <link linkend="datatype"> <code
>datatype</code> </link>, <link linkend="date"
> <code>date</code> 
 </link>, <link linkend="exstyle"> <code
>exstyle</code> </link>, <link
linkend="equiv-text"> <code>equiv-text</code
> </link>, <link linkend="equiv-trans"> 
 <code>equiv-trans</code> 
 </link>,<link linkend="extradata"> <code>extradata</code
> </link>, <link linkend="extype"> <code
>extype</code> </link>, <link linkend="font"
> <code>font</code> 
 </link>, <link linkend="form"> <code
>form</code> </link>, <link linkend="from"
> <code>from</code> 
 </link> , <link linkend="help-id"> 
 <code>help-id</code> </link>, <link
linkend="href"> <code>href</code> 
 </link>, <link linkend="id"> 
 <code>id</code> </link>, <link
linkend="job-id"> <code>job-id</code> 
 </link> , <link linkend="match-mandatory"> 
 <code>match-mandatory</code> 
 </link>, <link linkend="match-quality"> 
 <code>match-quality</code> </link
> , <link linkend="maxheight"> <code>maxheight</code
> </link>, <link linkend="maxbytes"> 
 <code>maxbytes</code> 
 </link>, <link linkend="maxwidth"> <code
>maxwidth</code> </link>, <link linkend="menu"
> <code>menu</code> 
 </link>, <link linkend="menu-name"> 
 <code>menu-name</code> </link>, <link
linkend="menu-option"> <code>menu-option</code
> </link>, <link linkend="mid"> 
 <code>mid</code> </link>, <link
linkend="merged-trans"> <code>merged-trans</code
> </link>, <link linkend="mime-type"> 
 <code>mime-type</code> 
 </link>, <link linkend="minheight"> 
 <code>minheight</code> </link>, <link
linkend="minbytes"> <code>minbytes</code
> </link>, <link linkend="minwidth"> 
 <code>minwidth</code> 
 </link>, <link linkend="mtype"> <code
>mtype</code> </link>, <link linkend="name"
> <code>name</code> 
 </link>, <link linkend="original"> 
 <code>original</code> </link>, <link
linkend="phase-name"> <code>phase-name</code
> </link>, <link linkend="pos"> 
 <code>pos</code> </link>, <link
linkend="priority"> <code>priority</code
> </link>, <link linkend="process-name"> 
 <code>process-name</code> 
 </link>, <link linkend="product-name"> 
 <code>product-name</code> </link
>, <link linkend="product-version"> <code
>product-version</code> </link>, <link
linkend="prop-type"> <code>prop-type</code
> </link>, <code> <link linkend="purpose"
>purpose</link> </code>, <link linkend="reformat"> 
 <code>reformat</code> </link
>, <link linkend="resname"> <code>resname</code
> </link>, <link linkend="restype"> 
 <code>restype</code> </link
>, <link linkend="rid"> <code>rid</code
> </link> , <code> <link linkend="size-unit"
>size-unit</link> </code>, <link linkend="source-language"> 
 <code>source-language</code> 
 </link> , <link linkend="state"> 
 <code>state</code> </link>, <code> <link
linkend="state-qualifier">state-qualifier</link> </code>, <link
linkend="style"> <code>style</code> 
 </link>, <link linkend="tool"> 
 <code>tool</code> </link>, <code
> <link linkend="tool-company">tool-company</link> </code>, <code
> <link linkend="tool-id">tool-id</link> </code>, <code> <link
linkend="tool-name">tool-name</link> </code>, <code> <link
linkend="tool-version">tool-version</link> </code>, <link
linkend="target-language"> <code>target-language</code
> </link> , <link linkend="translate"> 
 <code>translate</code> 
 </link>, <link linkend="ts"> <code
>ts</code> </link>, <link linkend="uid"> 
 <code>uid</code> 
 </link>, <link linkend="unit"> <code>unit</code
> </link> , <link linkend="version"> 
 <code>version</code> 
 </link>, <code> <link linkend="xid">xid</link> </code>.</entry>
</row>
<row>
<entry> <link linkend="Specs_Attr_Xml">XML namespace attributes</link
> </entry>
<entry> <link linkend="xml_lang"> <code
>xml:lang</code> </link>, <link
linkend="xml_space"> <code>xml:space</code
> </link>.</entry>
</row>
</tbody>
</tgroup>
</table>
<section>
<title id="Specs_Attr_Xliff">XLIFF Attributes</title>
<para id="alttranstype"> alttranstype</para>
<para> <emphasis>Resource type</emphasis> - Indicates the type of
 translation within the containing alt-trans element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>proposal</code> </entry>
<entry>Represents a translation proposal from a translation memory
or other resource.</entry>
</row>
<row>
<entry> <code>previous-version</code> </entry>
<entry>Represents a previous version of the target element.</entry>
</row>
<row>
<entry> <code>rejected</code> </entry>
<entry>Represents a rejected version of the target element.</entry>
</row>
<row>
<entry> <code>reference</code> </entry>
<entry>Represents a translation to be used for reference purposes
only, for example from a related product or a different language.</entry>
</row>
<row>
<entry> <code>accepted</code> </entry>
<entry>Represents a proposed translation that was used for the translation
of the trans-unit, possibly modified.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para> <code>proposal</code>.</para>
<para>Used in:</para>
<para> <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> </para>
<para id="annotates">annotates</para>
<para> <emphasis>Annotates</emphasis> - Indicates if a <code> 
 <link linkend="note">&lt;note></link> </code> element pertains
to the <code> <link linkend="source">&lt;source></link> </code
> or the <code> <link linkend="target">&lt;target></link> </code
>, or neither in particular.</para>
<para>Value description:</para>
<para> <code>source</code>, <code>target</code>, or <code>general</code
>.</para>
<para>Default value:</para>
<para> <code>general</code>.</para>
<para>Used in:</para>
<para> <code> <link linkend="note">&lt;note></link> </code
>.</para>
<para id="approved">approved</para>
<para> <emphasis>Approved</emphasis> - Indicates whether a translation
 is final or has passed its final review.</para>
<para>Value description:</para>
<para>Boolean: <code>yes</code> or <code>no</code>.</para>
<para>Default value:</para>
<para> <code>no</code>.</para>
<para>Used in:</para>
<para> <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="bin-unit"> <code
>&lt;bin-unit></code> </link>.</para>
<para id="assoc">assoc</para>
<para> <emphasis>Association</emphasis> - Indicates the association
of a <link linkend="ph"> <code>&lt;ph></code> 
 </link> with the text prior or after the inline element.</para>
<para>Value description:</para>
<para> <code>preceding</code> (the element is associated with
the text preceding the element), <code>following</code> (the element
is associated with the text following the element), and <code>both</code
> (the element is associated with the text on both sides).</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="ph"> <code>&lt;ph></code> </link
>.</para>
<para id="build-num">build-num</para>
<para> <emphasis>Build number</emphasis> - The build number of the
 version of the product or application the localizable material is
 for. For example: <code>build-num="12"</code> for the 12th build
of the new version of a product.</para>
<para>Value description:</para>
<para>Alpha-numeric.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="category">category</para>
<para> <emphasis>Category</emphasis> - This provides information
on the subject of what is being translated. For example: <code
>category="medical"</code> for files from a medical related product.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="charclass">charclass</para>
<para> <emphasis>Character class</emphasis> - This indicates that
a translation is restricted to a subset of characters (i.e. ASCII
 only, Katakana only, uppercase only, etc.). A blank value indicates
 there is no limitation.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link>,</code
> <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="clone">clone</para>
<para> <emphasis>Clone</emphasis> - This indicates that a copy of
the given inline element can be made and placed multiple times in
the <code> <link linkend="target">&lt;target></link> </code
>. This is useful for codes such as bold which may require duplication
after localization of a segment.</para>
<para>Value description:</para>
<para>Boolean: <code>yes</code> or <code>no</code>.</para>
<para>Default value:</para>
<para> <code>yes</code>.</para>
<para>Used in:</para>
<para> <link linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> .</para>
<para id="comment">comment</para>
<para> <emphasis>Comment</emphasis> - A comment in a tag.</para>
<para>Value description:</para>
<para>Alpha-numeric.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="mrk"> <code>&lt;mrk></code> 
 </link>.</para>
<para id="company-name"> company-name</para>
<para> <emphasis>Company name</emphasis> - The name of the company
 that has performed a task.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="contact-email"> contact-email</para>
<para> <emphasis>Contact email</emphasis> - The contact email of
the <code> <link linkend="contact-name">contact-name</link> 
 </code> person.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="contact-name"> contact-name</para>
<para> <emphasis>Contact name</emphasis> - The name of the person
that has performed a task in a phase.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="contact-phone"> contact-phone</para>
<para> <emphasis>Contact phone</emphasis> - The phone number of
the <code> <link linkend="contact-name">contact-name</link> 
 </code> person.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="context-type"> context-type</para>
<para> <emphasis>Context type</emphasis> - The <code>context-type</code
> attribute specifies the context and the type of resource or style
of the data of a given element. For example, to define if it is
a label, or a menu item in the case of resource-type data, or the
style in the case of document-related data.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>database</code> </entry>
<entry>Indicates a database content.</entry>
</row>
<row>
<entry> <code>element</code> </entry>
<entry>Indicates the content of an element within an XML document.</entry>
</row>
<row>
<entry> <code>elementtitle</code> </entry>
<entry>Indicates the name of an element within an XML document.</entry>
</row>
<row>
<entry> <code>linenumber</code> </entry>
<entry>Indicates the line number from the sourcefile (see context-type="sourcefile")
where the &lt;source> is found.</entry>
</row>
<row>
<entry> <code>numparams</code> </entry>
<entry>Indicates a the number of parameters contained within the &lt;source>.</entry>
</row>
<row>
<entry> <code>paramnotes</code> </entry>
<entry>Indicates notes pertaining to the parameters in the &lt;source>.</entry>
</row>
<row>
<entry> <code>record</code> </entry>
<entry>Indicates the content of a record within a database.</entry>
</row>
<row>
<entry> <code>recordtitle</code> </entry>
<entry>Indicates the name of a record within a database.</entry>
</row>
<row>
<entry> <code>sourcefile</code> </entry>
<entry>Indicates the original source file in the case that multiple
files are merged to form the original file from which the XLIFF file
is created. This differs from the original &lt;file> attribute in
that this sourcefile is one of many that make up that file.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="context"> <code>&lt;context></code
> </link>.</para>
<para id="coord">coord</para>
<para> <emphasis>Coordinates</emphasis> - The <code>coord</code
> attribute specifies the x, y, cx and cy coordinates of the text
for a given element. The cx and cy values must represent the width
and the height (as in Windows resources). The extraction and merging
 tools must make the right conversion if the original format uses
a top-left/bottom-right coordinate system.</para>
<para>Value description:</para>
<para>Four decimal (possibly negative) values, in the order: x,
y, cx and cy, separated by semi-colons. Null values may be entered
as "<code>#</code>"; (e.g. <code>coord="#;#;183;272"</code>).</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para>
<para id="count-type">count-type</para>
<para> <emphasis>Count type</emphasis> - The <code>count-type</code
> attribute specifies the purpose of the <code> <link
linkend="count">&lt;count></link> </code> element. For example:
 <code>count-type="total"</code> for the total count of words in
the current scope.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>num-usages</code> </entry>
<entry>Indicates the count units are items that are used X times in
a certain context; example: this is a reusable text unit which is
used 42 times in other texts.</entry>
</row>
<row>
<entry> <code>repetition</code> </entry>
<entry>Indicates the count units are translation units existing already
in the same document.</entry>
</row>
<row>
<entry> <code>total</code> </entry>
<entry>Indicates a total count.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>In addition, the <code>count-type</code> attribute can take
any value defined for <code> <link linkend="datatype">datatype</link
> </code>, <code> <link linkend="restype">restype</link> </code
>, or <code> <link linkend="state">state</link> </code>.</para>
<para>Default value:</para>
<para>None.</para>
<para>Used in:</para>
<para> <link linkend="count"> <code>&lt;count></code> 
 </link>.</para>
<para id="crc">crc</para>
<para> <emphasis>Cyclic redundancy checking</emphasis> - A private
 value used to verify data as it is returned to the producer. The
 generation and verification of this number is tool-specific.</para>
<para>Value description:</para>
<para>Number (possibly not decimal).</para>
<para>Default value:</para>
<para>None.</para>
<para>Used in:</para>
<para> <link linkend="internal-file"> <code>&lt;internal-file></code
> </link> , <link linkend="external-file"> 
 <code>&lt;external-file></code> </link>, <link
linkend="context-group"> <code>&lt;context-group></code
> </link>, <link linkend="context"> 
 <code>&lt;context></code> </link>, <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>, <link linkend="bpt"> <code
>&lt;bpt></code> </link>, <link linkend="ept"> 
 <code>&lt;ept></code> </link>, <link
linkend="it"> <code>&lt;it></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>.</para>
<para id="css-style">css-style</para>
<para> <emphasis>Cascading style-sheet style</emphasis> - The <code
>css-style</code> attribute allows any valid <link linkend="refCSS"
>CSS statement</link> to be specified.</para>
<para>Value description:</para>
<para>Text, the value is subject to CSS syntax rules.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para>
<para id="ctype">ctype</para>
<para> <emphasis>Content type</emphasis> - The <code>ctype</code
> attribute specifies the type of code that is represented by the
 inline element; e.g. ctype="bold" means that the code represents
a bolding code.</para>
<para>Value description for the <code>ctype</code> attribute of
the <link linkend="x"> <code>&lt;x/></code> 
 </link> and <code> <link linkend="ph">&lt;ph></link
> </code> elements:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>image</code> </entry>
<entry>Indicates a inline image.</entry>
</row>
<row>
<entry> <code>pb</code> </entry>
<entry>Indicates a page break.</entry>
</row>
<row>
<entry> <code>lb</code> </entry>
<entry>Indicates a line break.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Value description for the <code>ctype</code> attribute of
other elements:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>bold</code> </entry>
<entry>Indicates a run of bolded text.</entry>
</row>
<row>
<entry> <code>italic</code> </entry>
<entry>Indicates a run of text in italics.</entry>
</row>
<row>
<entry> <code>underlined</code> </entry>
<entry>Indicates a run of underlined text.</entry>
</row>
<row>
<entry> <code>link</code> </entry>
<entry>Indicates a run of hyper-text.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> , <link linkend="bpt"> <code
>&lt;bpt></code> </link>, <link linkend="sub"> 
 <code>&lt;sub></code> </link>, <link
linkend="it"> <code>&lt;it></code> 
 </link> , <code> <link linkend="ph">&lt;ph></link> </code
>.</para>
<para id="datatype">datatype</para>
<para> <emphasis>Data type</emphasis> - The <code>datatype</code
> attribute specifies the kind of text contained in the element.
 Depending on that type, you may apply different processes to the
 data. For example: <code>datatype="winres"</code> specifies that
the content is Windows resources which would allow using the Win32
API in rendering the content.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>asp</code> </entry>
<entry>Indicates Active Server Page data.</entry>
</row>
<row>
<entry> <code>c</code> </entry>
<entry>Indicates C source file data.</entry>
</row>
<row>
<entry> <code>cdf</code> </entry>
<entry>Indicates Channel Definition Format (CDF) data.</entry>
</row>
<row>
<entry> <code>cfm</code> </entry>
<entry>Indicates ColdFusion data.</entry>
</row>
<row>
<entry> <code>cpp</code> </entry>
<entry>Indicates C++ source file data.</entry>
</row>
<row>
<entry> <code>csharp</code> </entry>
<entry>Indicates C-Sharp data.</entry>
</row>
<row>
<entry> <code>cstring</code> </entry>
<entry>Indicates strings from C, ASM, and driver files data.</entry>
</row>
<row>
<entry> <code>csv</code> </entry>
<entry>Indicates comma-separated values data.</entry>
</row>
<row>
<entry> <code>database</code> </entry>
<entry>Indicates database data.</entry>
</row>
<row>
<entry> <code>documentfooter</code> </entry>
<entry>Indicates portions of document that follows data and contains
metadata.</entry>
</row>
<row>
<entry> <code>documentheader</code> </entry>
<entry>Indicates portions of document that precedes data and contains
metadata.</entry>
</row>
<row>
<entry> <code>filedialog</code> </entry>
<entry>Indicates data from standard UI file operations dialogs (e.g.,
Open, Save, Save As, Export, Import).</entry>
</row>
<row>
<entry> <code>form</code> </entry>
<entry>Indicates standard user input screen data.</entry>
</row>
<row>
<entry> <code>html</code> </entry>
<entry>Indicates HyperText Markup Language (HTML) data - document
instance.</entry>
</row>
<row>
<entry> <code>htmlbody</code> </entry>
<entry>Indicates content within an HTML document's &lt;body> element.</entry>
</row>
<row>
<entry> <code>ini</code> </entry>
<entry>Indicates Windows INI file data.</entry>
</row>
<row>
<entry> <code>interleaf</code> </entry>
<entry>Indicates Interleaf data.</entry>
</row>
<row>
<entry> <code>javaclass</code> </entry>
<entry>Indicates Java source file data (extension '.java').</entry>
</row>
<row>
<entry> <code>javapropertyresourcebundle</code> </entry>
<entry>Indicates Java property resource bundle data.</entry>
</row>
<row>
<entry> <code>javalistresourcebundle</code> </entry>
<entry>Indicates Java list resource bundle data.</entry>
</row>
<row>
<entry> <code>javascript</code> </entry>
<entry>Indicates JavaScript source file data.</entry>
</row>
<row>
<entry> <code>jscript</code> </entry>
<entry>Indicates JScript source file data.</entry>
</row>
<row>
<entry> <code>layout</code> </entry>
<entry>Indicates information relating to formatting.</entry>
</row>
<row>
<entry> <code>lisp</code> </entry>
<entry>Indicates LISP source file data.</entry>
</row>
<row>
<entry> <code>margin</code> </entry>
<entry>Indicates information relating to margin formats.</entry>
</row>
<row>
<entry> <code>menufile</code> </entry>
<entry>Indicates a file containing menu.</entry>
</row>
<row>
<entry> <code>messagefile</code> </entry>
<entry>Indicates numerically identified string table.</entry>
</row>
<row>
<entry> <code>mif</code> </entry>
<entry>Indicates Maker Interchange Format (MIF) data.</entry>
</row>
<row>
<entry> <code>mimetype</code> </entry>
<entry>Indicates that the datatype attribute value is a MIME Type
value and is defined in the mime-type attribute.</entry>
</row>
<row>
<entry> <code>mo</code> </entry>
<entry>Indicates GNU Machine Object data.</entry>
</row>
<row>
<entry> <code>msglib</code> </entry>
<entry>Indicates Message Librarian strings created by Novell's Message
Librarian Tool.</entry>
</row>
<row>
<entry> <code>pagefooter</code> </entry>
<entry>Indicates information to be displayed at the bottom of each
page of a document.</entry>
</row>
<row>
<entry> <code>pageheader</code> </entry>
<entry>Indicates information to be displayed at the top of each page
of a document.</entry>
</row>
<row>
<entry> <code>parameters</code> </entry>
<entry>Indicates a list of property values (e.g., settings within
INI files or preferences dialog).</entry>
</row>
<row>
<entry> <code>pascal</code> </entry>
<entry>Indicates Pascal source file data.</entry>
</row>
<row>
<entry> <code>php</code> </entry>
<entry>Indicates Hypertext Preprocessor data.</entry>
</row>
<row>
<entry> <code>plaintext</code> </entry>
<entry>Indicates plain text file (no formatting other than, possibly,
wrapping).</entry>
</row>
<row>
<entry> <code>po</code> </entry>
<entry>Indicates GNU Portable Object file.</entry>
</row>
<row>
<entry> <code>report</code> </entry>
<entry>Indicates dynamically generated user defined document. e.g.
Oracle Report, Crystal Report, etc.</entry>
</row>
<row>
<entry> <code>resources</code> </entry>
<entry>Indicates Windows .NET binary resources.</entry>
</row>
<row>
<entry> <code>resx</code> </entry>
<entry>Indicates Windows .NET Resources.</entry>
</row>
<row>
<entry> <code>rtf</code> </entry>
<entry>Indicates Rich Text Format (RTF) data.</entry>
</row>
<row>
<entry> <code>sgml</code> </entry>
<entry>Indicates Standard Generalized Markup Language (SGML) data
- document instance.</entry>
</row>
<row>
<entry> <code>sgmldtd</code> </entry>
<entry>Indicates Standard Generalized Markup Language (SGML) data
- Document Type Definition (DTD).</entry>
</row>
<row>
<entry> <code>svg</code> </entry>
<entry>Indicates Scalable Vector Graphic (SVG) data.</entry>
</row>
<row>
<entry> <code>vbscript</code> </entry>
<entry>Indicates VisualBasic Script source file.</entry>
</row>
<row>
<entry> <code>warning</code> </entry>
<entry>Indicates warning message.</entry>
</row>
<row>
<entry> <code>winres</code> </entry>
<entry>Indicates Windows (Win32) resources (i.e. resources extracted
from an RC script, a message file, or a compiled file).</entry>
</row>
<row>
<entry> <code>xhtml</code> </entry>
<entry>Indicates Extensible HyperText Markup Language (XHTML) data
- document instance.</entry>
</row>
<row>
<entry> <code>xml</code> </entry>
<entry>Indicates Extensible Markup Language (XML) data - document
instance.</entry>
</row>
<row>
<entry> <code>xmldtd</code> </entry>
<entry>Indicates Extensible Markup Language (XML) data - Document
Type Definition (DTD).</entry>
</row>
<row>
<entry> <code>xsl</code> </entry>
<entry>Indicates Extensible Stylesheet Language (XSL) data.</entry>
</row>
<row>
<entry> <code>xul</code> </entry>
<entry>Indicates XUL elements.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Empty string.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="group"> <code>&lt;group></code
> </link>, <link linkend="trans-unit"> 
 <code>&lt;trans-unit></code> </link>, <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>, <link linkend="sub"> <code
>&lt;sub></code> </link>.</para>
<para id="date">date</para>
<para> <emphasis>Date</emphasis> - The <code>date</code> attribute
 indicates when a given element was created or modified.</para>
<para>Value description:</para>
<para>Date in [<link linkend="refISO8601">ISO 8601</link>] Format.
 The recommended pattern to use is: <code>CCYY-MM-DDThh:mm:ssZ</code
> Where: <code>CCYY</code> is the year (4 digits), <code>MM</code
> is the month (2 digits), <code>DD</code> is the day (2 digits),
 <code>hh</code> is the hours (2 digits), <code>mm</code> is the
 minutes (2 digits), <code>ss</code> is the second (2 digits), and
 <code>Z</code> indicates the time is UTC time. For example:</para>
<programlisting>
 <emphasis>date="2002-01-25T21:06:00Z"</emphasis>
is January 25, 2002 at 9:06pm GMT
is January 25, 2002 at 2:06pm US Mountain Time
is January 26, 2002 at 6:06am Japan time
</programlisting>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>,<link linkend="phase"> <code>&lt;phase></code> </link
>.</para>
<para id="equiv-text">equiv-text</para>
<para> <emphasis>equiv-text</emphasis> - Indicates the equivalent
text to substitute in place of an inline tag. It is useful for inserting
 whitespace or other content in place of markup to facilitate consistent
word counting. The equiv-text attribute is also useful for ensuring
consistent round trip conversion between native resource formats
and XLIFF content, for example the resource string "<code>F&amp;ile</code
>" converts to the following XLIFF: "<code>F&lt;x id='1' ctype='x-akey'
 equiv-text=''/>ile</code>" to preserve the underlying translatable
content.</para>
<para>Value description:</para>
<para>Text</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="g"> <code>&lt;g></code> </link
>, <link linkend="x"> <code>&lt;x/></code> 
 </link>, <link linkend="bx"> <code>&lt;bx/></code
> </link> , <link linkend="ex"> <code
>&lt;ex/></code> </link>, <link linkend="bpt"> 
 <code>&lt;bpt></code> </link>, <link
linkend="ept"> <code>&lt;ept></code> 
 </link> , <link linkend="ph"> <code>&lt;ph></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link>.</para>
<para id="equiv-trans"> equiv-trans</para>
<para> <emphasis>equiv-trans</emphasis> - Indicates if the target
 language translation is a direct equivalent of the source text.</para>
<para>Value description:</para>
<para> <code>yes</code>, or <code>no</code>.</para>
<para>Default value:</para>
<para> <code>yes</code>.</para>
<para>Used in:</para>
<para> <code> <link linkend="target">&lt;target></link> </code
> </para>
<para id="exstyle">exstyle</para>
<para> <emphasis>Extended style</emphasis> - The <code>exstyle</code
> attribute stores the extended style of a control. For example,
in Windows resources it corresponds to the EXSTYLE statement.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para>
<para id="extradata">extradata</para>
<para> <emphasis>Extra data</emphasis> - The <code>extradata</code
> attribute stores the extra data properties of an item.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="extype">extype</para>
<para> <emphasis>Extended type</emphasis> -The <code>extype</code
> attribute stores the extra type properties of an item.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="font">font</para>
<para> <emphasis>Font</emphasis> - The <code>font</code> attribute
 specifies the font name, size, and weight of the text for a given
 element. The font attribute would generally be used for resource-type
data: change of font in document-type data can be marked with the <link
linkend="g"> <code>&lt;g></code> </link
> element.</para>
<para>Value description:</para>
<para>Name of the font, its size, its weight, its style and its
encoding separated by semi-colons. Only the name of the font is
required.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para>
<para id="form">form</para>
<para> <emphasis>Format</emphasis> - Describes the type of format
used in an <link linkend="internal-file"> <code
>&lt;internal-file></code> </link> element. For example: <code
>form="text"</code> indicates a plain text format internal file.</para>
<para>Value description:</para>
<para>The value can be either <code>text</code> (for plain text
data), <code>base64</code> (for data coded in base64 format), or
one of values available from the [<link linkend="refRFC1341">RFC 
 1341</link>] document: the MIME specification.</para>
<para>Default value:</para>
<para> <code>text</code>.</para>
<para>Used in:</para>
<para> <link linkend="internal-file"> <code>&lt;internal-file></code
> </link> .</para>
<para id="from">from</para>
<para> <emphasis>From</emphasis> - Indicates the author of a <code
> <link linkend="note">&lt;note></link> </code> element. For
example: <code>from="reviewer"</code> indicates a note from a 
reviewer.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="note"> <code>&lt;note></code> 
 </link>.</para>
<para id="help-id">help-id</para>
<para> <emphasis>Help ID</emphasis> -The <code>help-id</code> 
attribute stores the help identifier of an item. For example, in 
 Windows resources it corresponds to the Help ID parameter of a 
control.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="href">href</para>
<para> <emphasis>Hypertext reference</emphasis> - The location of
the file or the URL for an <link linkend="external-file"> 
 <code>&lt;external-file></code> </link
> element. For example: <code>href="file:///C:/MyFolder/MyProject/MyFile.htm"</code
> indicates a file on a local drive.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="external-file"> <code>&lt;external-file></code
> </link> .</para>
<para id="id">id</para>
<para> <emphasis>Identifier</emphasis> - The <code>id</code> attribute
 is used in many elements as a reference to the original corresponding
code data or format for the given element. The value of the <code
>id</code> element is determined by the tool creating the XLIFF
document. It may or may not be a resource identifier. The identifier
of a resource should, at least, be stored in the <code> <link
linkend="resname">resname</link> </code> attribute.</para>
<para>For example:</para>
<programlisting>
&lt;trans-unit <emphasis>id="34"</emphasis> resname="IDD_ABOUT_DLG" restype="dialog"
coord="0;0;235;100" font="MS Sans Serif;8" style="0x0932239">

&lt;source>About Dialog&lt;/source>
&lt;/trans-unit>
</programlisting>
<programlisting>
&lt;trans-unit <emphasis>id="IDD_ABOUT_DLG"</emphasis> resname="IDD_ABOUT_DLG"
 restype="dialog" coord="0;0;235;100" font="MS Sans Serif;8"
 style="0x0932239">
&lt;source>About Dialog&lt;/source>

&lt;/trans-unit>
</programlisting>
<para>Value description:</para>
<para>Text. Note that, while allowed, spaces are usually not used
in identifiers.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="bin-unit"
> <code>&lt;bin-unit></code> </link
>, <link linkend="g"> <code>&lt;g></code> 
 </link>, <link linkend="x"> <code>&lt;x/></code
> </link>, <link linkend="bx"> <code
>&lt;bx/></code> </link>, <link linkend="ex"> 
 <code>&lt;ex/></code> </link>, <link
linkend="bpt"> <code>&lt;bpt></code> 
 </link>, <link linkend="ept"> <code>&lt;ept></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link>, <link linkend="ph"> 
 <code>&lt;ph></code> </link> .</para>
<para id="job-id">job-id</para>
<para> <emphasis>Job ID</emphasis> - The identifier given to the
 localization job. This is determined by the entity creating the
 phase element at the time of processing the file.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="match-mandatory"> match-mandatory</para>
<para> <emphasis>Match mandatory</emphasis> -Indicates that any
 <code> <link linkend="alt-trans">&lt;alt-trans></link> </code
> element of the parent <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code> must have the same <link linkend="context"> 
 <code>&lt;context></code> </link> as the <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code>.</para>
<para>Value description:</para>
<para>Boolean: <code>yes</code> or <code>no</code>.</para>
<para>Default value:</para>
<para> <code>no</code>.</para>
<para>Used in:</para>
<para> <link linkend="context"> <code>&lt;context></code
> </link>.</para>
<para id="match-quality"> match-quality</para>
<para> <emphasis>Match quality</emphasis> - The match quality of
the <code> <link linkend="alt-trans">&lt;alt-trans></link> 
 </code> element is tool specific and can be a score expressed in
percentage or an arbitrary value (e.g. <code>match-quality="high"</code
>).</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> .</para>
<para id="maxheight">maxheight</para>
<para> <emphasis>Maximum height</emphasis> - The maximum height
for the <code> <link linkend="target">&lt;target></link> </code
> of a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>. This could be interpreted as lines, pixels, or any
other relevant unit. The unit is determined by the <link
linkend="size-unit"> <code>size-unit</code> 
 </link> attribute, which defaults to <code>pixel</code
>.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="maxbytes">maxbytes</para>
<para> <emphasis>Maximum bytes</emphasis> - The maximum number of
 bytes for the <code> <link linkend="target">&lt;target></link
> </code> of a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>. The verification of whether the relevant text respects
this requirement must be done using the encoding and line-break
type of the final target environment.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="maxwidth">maxwidth</para>
<para> <emphasis>Maximum width</emphasis> - The maximum width for
the <code> <link linkend="target">&lt;target></link> </code
> of a <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>. This could be interpreted as lines, pixels,
or any other relevant unit. The unit is determined by the <link
linkend="size-unit"> <code>size-unit</code> 
 </link> attribute, which defaults to <code>pixel</code
>.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="menu">menu</para>
<para> <emphasis>Menu</emphasis> - The <code>menu</code> attribute
 stores the menu property of an item.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="menu-name">menu-name</para>
<para> <emphasis>Menu name</emphasis> - The <code>menu-name</code
> attribute stores the menu name of a control.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="menu-option"> menu-option</para>
<para> <emphasis>Menu option</emphasis> - The <code>menu-option</code
> attribute stores the option data of a control.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
>.</para>
<para id="mid">mid</para>
<para> <emphasis>Marker ID</emphasis> - Identifier for an <link
linkend="mrk"> <code>&lt;mrk></code> 
 </link> element. When used with in combination with <code> 
 <link linkend="mtype">mtype</link>="seg"</code> the value of this
 attribute is used to reference segments between the <code> <link
linkend="seg-source">&lt;seg-source></link> </code> and <link
linkend="target"> <code>&lt;target></code> 
 </link> of a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>. When used in <code> <link linkend="alt-trans">&lt;alt-trans></link
> </code> this attribute indicates that the entire <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> element references
a particular <code>&lt;mrk <link linkend="mtype">mtype</link> 
="seg"></code> segment in the <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> (and <code> <link linkend="target"
>&lt;target></link> </code>) element. See the <link
linkend="Struct_Segmentation">Segmentation</link> section for further
 details.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="mrk"> <code>&lt;mrk></code> 
 </link>, <code> <link linkend="alt-trans">&lt;alt-trans></link
> </code> </para>
<para id="merged-trans"> merged-trans</para>
<para> <emphasis>merged-trans</emphasis> - Indicates if the group
 element contains merged <code>trans-unit</code> elements.</para>
<para>Value description:</para>
<para> <code>yes</code>, or <code>no</code>.</para>
<para>Default value:</para>
<para> <code>no</code>.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
> </para>
<para id="mime-type">mime-type</para>
<para> <emphasis>Mime type</emphasis> -Indicates the type of a binary
 object. These roughly correspond to the content-type of <link
linkend="refRFC1341">RFC 1341</link> , the MIME specification; e.g.
 <code>mime-type="image/jpeg"</code> indicates the binary object
is an image file of JPEG format. This is important in determining
how to edit the binary object.</para>
<para>Value description:</para>
<para>Text. A list of preferred values is available from the [<link
linkend="refRFC1341">RFC 1341</link>] document: the MIME specification.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link>, <link linkend="bin-target"> <code
>&lt;bin-target></code> </link>.</para>
<para id="minheight">minheight</para>
<para> <emphasis>Minimum height</emphasis> - The minimum height
for the <code> <link linkend="target">&lt;target></link> </code
> of a <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>. This could be interpreted as lines, pixels,
or any other relevant unit. The unit is determined by the <link
linkend="size-unit"> <code>size-unit</code> 
 </link> attribute, which defaults to <code>pixel</code
>.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="minbytes">minbytes</para>
<para> <emphasis>Minimum bytes</emphasis> - The minimum number of
 bytes for the <code> <link linkend="target">&lt;target></link
> </code> of a <code> <link linkend="trans-unit">&lt;trans-unit></link
> </code>. The verification of whether the relevant text respects
this requirement must be done using the encoding and line-break
type of the final target environment.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="minwidth">minwidth</para>
<para> <emphasis>Minimum width</emphasis> - The minimum width for
the <code> <link linkend="target">&lt;target></link> </code
> of a <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>. This could be interpreted as lines, pixels,
or any other relevant unit. The unit is determined by the <link
linkend="size-unit"> <code>size-unit</code> 
 </link> attribute, which defaults to <code>pixel</code
>.</para>
<para>Value description:</para>
<para>Number.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>.</para>
<para id="mtype">mtype</para>
<para> <emphasis>Marker type</emphasis> -The <code>mtype</code> 
 attribute specifies what a <link linkend="mrk"> 
 <code>&lt;mrk></code> </link> element is defining
within the content of a <code> <link linkend="source">&lt;source></link
> </code> or <code> <link linkend="target">&lt;target></link
> </code> element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>abbrev</code> </entry>
<entry>Indicates the marked text is an abbreviation.</entry>
</row>
<row>
<entry> <code>abbreviated-form</code> </entry>
<entry>ISO-12620 2.1.8: A term resulting from the omission of any
part of the full term while designating the same concept.</entry>
</row>
<row>
<entry> <code>abbreviation</code> </entry>
<entry>ISO-12620 2.1.8.1: An abbreviated form of a simple term resulting
from the omission of some of its letters (e.g. 'adj.' for 'adjective').</entry>
</row>
<row>
<entry> <code>acronym</code> </entry>
<entry>ISO-12620 2.1.8.4: An abbreviated form of a term made up of
letters from the full form of a multiword term strung together into
a sequence pronounced only syllabically (e.g. 'radar' for 'radio detecting
and ranging').</entry>
</row>
<row>
<entry> <code>appellation</code> </entry>
<entry>ISO-12620: A proper-name term, such as the name of an agency
or other proper entity.</entry>
</row>
<row>
<entry> <code>collocation</code> </entry>
<entry>ISO-12620 2.1.18.1: A recurrent word combination characterized
by cohesion in that the components of the collocation must co-occur
within an utterance or series of utterances, even though they do not
necessarily have to maintain immediate proximity to one another.</entry>
</row>
<row>
<entry> <code>common-name</code> </entry>
<entry>ISO-12620 2.1.5: A synonym for an international scientific
term that is used in general discourse in a given language.</entry>
</row>
<row>
<entry> <code>datetime</code> </entry>
<entry>Indicates the marked text is a date and/or time.</entry>
</row>
<row>
<entry> <code>equation</code> </entry>
<entry>ISO-12620 2.1.15: An expression used to represent a concept
based on a statement that two mathematical expressions are, for instance,
equal as identified by the equal sign (=), or assigned to one another
by a similar sign.</entry>
</row>
<row>
<entry> <code>expanded-form</code> </entry>
<entry>ISO-12620 2.1.7: The complete representation of a term for
which there is an abbreviated form.</entry>
</row>
<row>
<entry> <code>formula</code> </entry>
<entry>ISO-12620 2.1.14: Figures, symbols or the like used to express
a concept briefly, such as a mathematical or chemical formula.</entry>
</row>
<row>
<entry> <code>head-term</code> </entry>
<entry>ISO-12620 2.1.1: The concept designation that has been chosen
to head a terminological record.</entry>
</row>
<row>
<entry> <code>initialism</code> </entry>
<entry>ISO-12620 2.1.8.3: An abbreviated form of a term consisting
of some of the initial letters of the words making up a multiword
term or the term elements making up a compound term when these letters
are pronounced individually (e.g. 'BSE' for 'bovine spongiform encephalopathy').</entry>
</row>
<row>
<entry> <code>international-scientific-term</code> </entry>
<entry>ISO-12620 2.1.4: A term that is part of an international scientific
nomenclature as adopted by an appropriate scientific body.</entry>
</row>
<row>
<entry> <code>internationalism</code> </entry>
<entry>ISO-12620 2.1.6: A term that has the same or nearly identical
orthographic or phonemic form in many languages.</entry>
</row>
<row>
<entry> <code>logical-expression</code> </entry>
<entry>ISO-12620 2.1.16: An expression used to represent a concept
based on mathematical or logical relations, such as statements of
inequality, set relationships, Boolean operations, and the like.</entry>
</row>
<row>
<entry> <code>materials-management-unit</code> </entry>
<entry>ISO-12620 2.1.17: A unit to track object.</entry>
</row>
<row>
<entry> <code>name</code> </entry>
<entry>Indicates the marked text is a name.</entry>
</row>
<row>
<entry> <code>near-synonym</code> </entry>
<entry>ISO-12620 2.1.3: A term that represents the same or a very
similar concept as another term in the same language, but for which
interchangeability is limited to some contexts and inapplicable in
others.</entry>
</row>
<row>
<entry> <code>part-number</code> </entry>
<entry>ISO-12620 2.1.17.2: A unique alphanumeric designation assigned
to an object in a manufacturing system.</entry>
</row>
<row>
<entry> <code>phrase</code> </entry>
<entry>Indicates the marked text is a phrase.</entry>
</row>
<row>
<entry> <code>phraseological-unit</code> </entry>
<entry>ISO-12620 2.1.18: Any group of two or more words that form
a unit, the meaning of which frequently cannot be deduced based on
the combined sense of the words making up the phrase.</entry>
</row>
<row>
<entry> <code>protected</code> </entry>
<entry>Indicates the marked text should not be translated.</entry>
</row>
<row>
<entry> <code>romanized-form</code> </entry>
<entry>ISO-12620 2.1.12: A form of a term resulting from an operation
whereby non-Latin writing systems are converted to the Latin alphabet.</entry>
</row>
<row>
<entry> <code>seg</code> </entry>
<entry>Indicates that the marked text represents a segment.</entry>
</row>
<row>
<entry> <code>set-phrase</code> </entry>
<entry>ISO-12620 2.1.18.2: A fixed, lexicalized phrase.</entry>
</row>
<row>
<entry> <code>short-form</code> </entry>
<entry>ISO-12620 2.1.8.2: A variant of a multiword term that includes
fewer words than the full form of the term (e.g. 'Group of Twenty-four'
for 'Intergovernmental Group of Twenty-four on International Monetary
Affairs').</entry>
</row>
<row>
<entry> <code>sku</code> </entry>
<entry>ISO-12620 2.1.17.1: Stock keeping unit, an inventory item identified
by a unique alphanumeric designation assigned to an object in an inventory
control system.</entry>
</row>
<row>
<entry> <code>standard-text</code> </entry>
<entry>ISO-12620 2.1.19: A fixed chunk of recurring text.</entry>
</row>
<row>
<entry> <code>symbol</code> </entry>
<entry>ISO-12620 2.1.13: A designation of a concept by letters, numerals,
pictograms or any combination thereof.</entry>
</row>
<row>
<entry> <code>synonym</code> </entry>
<entry>ISO-12620 2.1.2: Any term that represents the same or a very
similar concept as the main entry term in a term entry.</entry>
</row>
<row>
<entry> <code>synonymous-phrase</code> </entry>
<entry>ISO-12620 2.1.18.3: Phraseological unit in a language that
expresses the same semantic content as another phrase in that same
language.</entry>
</row>
<row>
<entry> <code>term</code> </entry>
<entry>Indicates the marked text is a term.</entry>
</row>
<row>
<entry> <code>transcribed-form</code> </entry>
<entry>ISO-12620 2.1.11: A form of a term resulting from an operation
whereby the characters of one writing system are represented by characters
from another writing system, taking into account the pronunciation
of the characters converted.</entry>
</row>
<row>
<entry> <code>transliterated-form</code> </entry>
<entry>ISO-12620 2.1.10: A form of a term resulting from an operation
whereby the characters of an alphabetic writing system are represented
by characters from another alphabetic writing system.</entry>
</row>
<row>
<entry> <code>truncated-term</code> </entry>
<entry>ISO-12620 2.1.8.5: An abbreviated form of a term resulting
from the omission of one or more term elements or syllables (e.g.
'flu' for 'influenza').</entry>
</row>
<row>
<entry> <code>variant</code> </entry>
<entry>ISO-12620 2.1.9: One of the alternate forms of a term.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="mrk"> <code>&lt;mrk></code> 
 </link>.</para>
<para id="name">name</para>
<para> <emphasis>Name</emphasis> - The <code>name</code> attribute
 specifies the user-defined name of a named group element. This is
 used for identification purposes only and is not referenced with
 the file, unless by a processing instruction.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="prop-group"> <code>&lt;prop-group></code
> </link>, <link linkend="context-group"> 
 <code>&lt;context-group></code> </link>, <link
linkend="count-group"> <code>&lt;count-group></code
> </link>.</para>
<para id="origin">origin</para>
<para> <emphasis>Translation Match Origin</emphasis> - The <code
>origin</code> attribute specifies where a translation match came
from; for example, from a previous version of the same product,
a different product, a shared translation memory, etc.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> .</para>
<para id="original">original</para>
<para> <emphasis>Original file</emphasis> - The original attribute
 specifies the name of the original file from which the contents
of a <link linkend="file">&lt;file></link> element has been extracted.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="phase-name">phase-name</para>
<para> <emphasis>Phase Name</emphasis> - The <code>phase-name</code
> attribute provides a unique name for a <link linkend="phase"> 
 <code>&lt;phase></code> </link> element.
It is used in other elements in the file to refer to the given <link
linkend="phase"> <code>&lt;phase></code> 
 </link> element.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="count">&lt;count></link>,</code
> <link linkend="phase"> <code>&lt;phase></code> 
 </link>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="target"> 
 <code>&lt;target></code> </link>, <link
linkend="bin-unit"> <code>&lt;bin-unit></code> 
 </link>, <link linkend="bin-target"> 
 <code>&lt;bin-target></code> </link>, <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> .</para>
<para id="pos">pos</para>
<para> <emphasis>Position</emphasis> - Indicates whether an isolated
 tag <code> <link linkend="it">&lt;it></link> </code> is a
beginning or an ending tag.</para>
<para>Value description:</para>
<para> <code>open</code> or <code>close</code>.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="it"> <code>&lt;it></code> </link
>.</para>
<para id="priority">priority</para>
<para> <emphasis>Priority</emphasis> - The priority of a <link
linkend="note">&lt;note></link> element.</para>
<para>Value description:</para>
<para>A number between 1 and 10, 1 being the highest priority.</para>
<para>Default value:</para>
<para>1</para>
<para>Used in:</para>
<para> <link linkend="note"> <code>&lt;note></code> 
 </link>.</para>
<para id="process-name"> process-name</para>
<para> <emphasis>Process name</emphasis> - The name specifying the
 type of process a given <code> <link linkend="phase">&lt;phase></link
> </code> corresponds to (e.g. Translation, Proofreading, Sizing,
etc.).</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="phase"> <code>&lt;phase></code> 
 </link>.</para>
<para id="product-name"> product-name</para>
<para> <emphasis>Product name</emphasis> - The name of the product
 which uses this file.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="product-version"> product-version</para>
<para> <emphasis>Product version</emphasis> - The version of the
 product which uses this file.</para>
<para>Value description:</para>
<para>Alpha-numeric.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="prop-type">prop-type</para>
<para> <emphasis>Property type</emphasis> - The <code>prop-type</code
> attribute specifies the type of a <code> <link linkend="prop"
>&lt;prop></link> </code> element.</para>
<para>Important: Because the <code> <link linkend="prop">&lt;prop></link
> </code> element was DEPRECATED in version 1.1 and this attribute
is only a member of that element, this attribute is also deprecated.
Instead, use attributes defined in a namespace different from XLIFF.
See the <link linkend="Struct_Extension">Extensibility</link> section
for more information.</para>
<para>Value description:</para>
<para>Text. No value defined by the standard.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="prop"> <code>&lt;prop></code> 
 </link>.</para>
<para id="purpose">purpose</para>
<para> <emphasis>Purpose</emphasis> - The <code>purpose</code> 
 attribute specifies the purpose of a <code> <link
linkend="context-group">&lt;context-group></link> </code> element.
For example: <code>purpose="information"</code> indicates the 
content is informational only and not used for specific processing.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>information</code> </entry>
<entry>Indicates that the context is informational in nature, specifying
for example, how a term should be translated. Thus, should be displayed
to anyone editing the XLIFF document.</entry>
</row>
<row>
<entry> <code>location</code> </entry>
<entry>Indicates that the context-group is used to specify where the
term was found in the translatable source. Thus, it is not displayed.</entry>
</row>
<row>
<entry> <code>match</code> </entry>
<entry>Indicates that the context information should be used during
translation memory lookups. Thus, it is not displayed.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Combinations of these values can be used. For example, <code
>purpose="location match x-validate"</code> provides both location
(<code>location</code>) and TM matching (<code>match</code>) contextual
information, as well as some user-defined data (<code>x-validate</code
> ).</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="context-group">&lt;context-group></link
> </code> .</para>
<para id="reformat">reformat</para>
<para> <emphasis>Reformat</emphasis> - Indicates whether some 
properties (size, font, etc.) of the target can be formatted differently
from the source.</para>
<para>Value description (stand-alone):</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>yes</code> </entry>
<entry>This value indicates that all properties can be reformatted.
This value must be used alone.</entry>
</row>
<row>
<entry> <code>no</code> </entry>
<entry>This value indicates that no properties should be reformatted.
This value must be used alone.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>Value description (enumerated):</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>coord</code> </entry>
<entry>This value indicates that all information in the coord attribute
can be modified.</entry>
</row>
<row>
<entry> <code>coord-x</code> </entry>
<entry>This value indicates that the x information in the coord attribute
can be modified.</entry>
</row>
<row>
<entry> <code>coord-y</code> </entry>
<entry>This value indicates that the y information in the coord attribute
can be modified.</entry>
</row>
<row>
<entry> <code>coord-cx</code> </entry>
<entry>This value indicates that the cx information in the coord attribute
can be modified.</entry>
</row>
<row>
<entry> <code>coord-cy</code> </entry>
<entry>This value indicates that the cy information in the coord attribute
can be modified.</entry>
</row>
<row>
<entry> <code>font</code> </entry>
<entry>This value indicates that all the information in the font attribute
can be modified.</entry>
</row>
<row>
<entry> <code>font-name</code> </entry>
<entry>This value indicates that the name information in the font
attribute can be modified.</entry>
</row>
<row>
<entry> <code>font-size</code> </entry>
<entry>This value indicates that the size information in the font
attribute can be modified.</entry>
</row>
<row>
<entry> <code>font-weight</code> </entry>
<entry>This value indicates that the weight information in the font
attribute can be modified.</entry>
</row>
<row>
<entry> <code>css-style</code> </entry>
<entry>This value indicates that the information in the css-style
attribute can be modified.</entry>
</row>
<row>
<entry> <code>style</code> </entry>
<entry>This value indicates that the information in the style attribute
can be modified.</entry>
</row>
<row>
<entry> <code>ex-style</code> </entry>
<entry>This value indicates that the information in the exstyle attribute
can be modified.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Except for the values <code>yes</code> and <code>no</code
>, the other values can be used in combination, separated by a space.
For example:</para>
<programlisting>
reformat="yes"
</programlisting>
<para>All properties can be reformatted.</para>
<programlisting>
reformat="no"
</programlisting>
<para>No properties should be reformatted.</para>
<programlisting>
reformat="font-name coord-x coord-y"
</programlisting>
<para>Only the name part of the font attribute, the x part of the
coord attribute and the y part of the coord attribute can be modified.</para>
<para>Default value:</para>
<para> <code>yes</code>.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>,<link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link>.</para>
<para id="resname">resname</para>
<para> <emphasis>Resource name</emphasis> - Resource name or identifier
of a item. For example: the key in the key/value pair in a Java
properties file, the ID of a string in a Windows string table, the
index value of an entry in a database table, etc.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code>.</link
> <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="alt-trans"> <code
>&lt;alt-trans></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link>, <link linkend="bin-target"> 
 <code>&lt;bin-target></code> </link>.</para>
<para id="restype">restype</para>
<para> <emphasis>Resource type</emphasis> - Indicates the resource
 type of the container element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>auto3state</code> </entry>
<entry>Indicates a Windows RC AUTO3STATE control.</entry>
</row>
<row>
<entry> <code>autocheckbox</code> </entry>
<entry>Indicates a Windows RC AUTOCHECKBOX control.</entry>
</row>
<row>
<entry> <code>autoradiobutton</code> </entry>
<entry>Indicates a Windows RC AUTORADIOBUTTON control.</entry>
</row>
<row>
<entry> <code>bedit</code> </entry>
<entry>Indicates a Windows RC BEDIT control.</entry>
</row>
<row>
<entry> <code>bitmap</code> </entry>
<entry>Indicates a bitmap, for example a BITMAP resource in Windows.</entry>
</row>
<row>
<entry> <code>button</code> </entry>
<entry>Indicates a button object, for example a BUTTON control Windows.</entry>
</row>
<row>
<entry> <code>caption</code> </entry>
<entry>Indicates a caption, such as the caption of a dialog box.</entry>
</row>
<row>
<entry> <code>cell</code> </entry>
<entry>Indicates the cell in a table, for example the content of the
&lt;td> element in HTML.</entry>
</row>
<row>
<entry> <code>checkbox</code> </entry>
<entry>Indicates check box object, for example a CHECKBOX control
in Windows.</entry>
</row>
<row>
<entry> <code>checkboxmenuitem</code> </entry>
<entry>Indicates a menu item with an associated checkbox.</entry>
</row>
<row>
<entry> <code>checkedlistbox</code> </entry>
<entry>Indicates a list box, but with a check-box for each item.</entry>
</row>
<row>
<entry> <code>colorchooser</code> </entry>
<entry>Indicates a color selection dialog.</entry>
</row>
<row>
<entry> <code>combobox</code> </entry>
<entry>Indicates a combination of edit box and listbox object, for
example a COMBOBOX control in Windows.</entry>
</row>
<row>
<entry> <code>comboboxexitem</code> </entry>
<entry>Indicates an initialization entry of an extended combobox DLGINIT
resource block. (code 0x1234).</entry>
</row>
<row>
<entry> <code>comboboxitem</code> </entry>
<entry>Indicates an initialization entry of a combobox DLGINIT resource
block (code 0x0403).</entry>
</row>
<row>
<entry> <code>component</code> </entry>
<entry>Indicates a UI base class element that cannot be represented
by any other element.</entry>
</row>
<row>
<entry> <code>contextmenu</code> </entry>
<entry>Indicates a context menu.</entry>
</row>
<row>
<entry> <code>ctext</code> </entry>
<entry>Indicates a Windows RC CTEXT control.</entry>
</row>
<row>
<entry> <code>cursor</code> </entry>
<entry>Indicates a cursor, for example a CURSOR resource in Windows.</entry>
</row>
<row>
<entry> <code>datetimepicker</code> </entry>
<entry>Indicates a date/time picker.</entry>
</row>
<row>
<entry> <code>defpushbutton</code> </entry>
<entry>Indicates a Windows RC DEFPUSHBUTTON control.</entry>
</row>
<row>
<entry> <code>dialog</code> </entry>
<entry>Indicates a dialog box.</entry>
</row>
<row>
<entry> <code>dlginit</code> </entry>
<entry>Indicates a Windows RC DLGINIT resource block.</entry>
</row>
<row>
<entry> <code>edit</code> </entry>
<entry>Indicates an edit box object, for example an EDIT control in
Windows.</entry>
</row>
<row>
<entry> <code>file</code> </entry>
<entry>Indicates a filename.</entry>
</row>
<row>
<entry> <code>filechooser</code> </entry>
<entry>Indicates a file dialog.</entry>
</row>
<row>
<entry> <code>fn</code> </entry>
<entry>Indicates a footnote.</entry>
</row>
<row>
<entry> <code>font</code> </entry>
<entry>Indicates a font name.</entry>
</row>
<row>
<entry> <code>footer</code> </entry>
<entry>Indicates a footer.</entry>
</row>
<row>
<entry> <code>frame</code> </entry>
<entry>Indicates a frame object.</entry>
</row>
<row>
<entry> <code>grid</code> </entry>
<entry>Indicates a XUL grid element.</entry>
</row>
<row>
<entry> <code>groupbox</code> </entry>
<entry>Indicates a groupbox object, for example a GROUPBOX control
in Windows.</entry>
</row>
<row>
<entry> <code>header</code> </entry>
<entry>Indicates a header item.</entry>
</row>
<row>
<entry> <code>heading</code> </entry>
<entry>Indicates a heading, such has the content of &lt;h1>, &lt;h2>,
etc. in HTML.</entry>
</row>
<row>
<entry> <code>hedit</code> </entry>
<entry>Indicates a Windows RC HEDIT control.</entry>
</row>
<row>
<entry> <code>hscrollbar</code> </entry>
<entry>Indicates a horizontal scrollbar.</entry>
</row>
<row>
<entry> <code>icon</code> </entry>
<entry>Indicates an icon, for example an ICON resource in Windows.</entry>
</row>
<row>
<entry> <code>iedit</code> </entry>
<entry>Indicates a Windows RC IEDIT control.</entry>
</row>
<row>
<entry> <code>keywords</code> </entry>
<entry>Indicates keyword list, such as the content of the Keywords
meta-data in HTML, or a K footnote in WinHelp RTF.</entry>
</row>
<row>
<entry> <code>label</code> </entry>
<entry>Indicates a label object.</entry>
</row>
<row>
<entry> <code>linklabel</code> </entry>
<entry>Indicates a label that is also a HTML link (not necessarily
a URL).</entry>
</row>
<row>
<entry> <code>list</code> </entry>
<entry>Indicates a list (a group of list-items, for example an &lt;ol>
or &lt;ul> element in HTML).</entry>
</row>
<row>
<entry> <code>listbox</code> </entry>
<entry>Indicates a listbox object, for example an LISTBOX control
in Windows.</entry>
</row>
<row>
<entry> <code>listitem</code> </entry>
<entry>Indicates an list item (an entry in a list).</entry>
</row>
<row>
<entry> <code>ltext</code> </entry>
<entry>Indicates a Windows RC LTEXT control.</entry>
</row>
<row>
<entry> <code>menu</code> </entry>
<entry>Indicates a menu (a group of menu-items).</entry>
</row>
<row>
<entry> <code>menubar</code> </entry>
<entry>Indicates a toolbar containing one or more tope level menus.</entry>
</row>
<row>
<entry> <code>menuitem</code> </entry>
<entry>Indicates a menu item (an entry in a menu).</entry>
</row>
<row>
<entry> <code>menuseparator</code> </entry>
<entry>Indicates a XUL menuseparator element.</entry>
</row>
<row>
<entry> <code>message</code> </entry>
<entry>Indicates a message, for example an entry in a MESSAGETABLE
resource in Windows.</entry>
</row>
<row>
<entry> <code>monthcalendar</code> </entry>
<entry>Indicates a calendar control.</entry>
</row>
<row>
<entry> <code>numericupdown</code> </entry>
<entry>Indicates an edit box beside a spin control.</entry>
</row>
<row>
<entry> <code>panel</code> </entry>
<entry>Indicates a catch all for rectangular areas.</entry>
</row>
<row>
<entry> <code>popupmenu</code> </entry>
<entry>Indicates a standalone menu not necessarily associated with
a menubar.</entry>
</row>
<row>
<entry> <code>pushbox</code> </entry>
<entry>Indicates a pushbox object, for example a PUSHBOX control in
Windows.</entry>
</row>
<row>
<entry> <code>pushbutton</code> </entry>
<entry>Indicates a Windows RC PUSHBUTTON control.</entry>
</row>
<row>
<entry> <code>radio</code> </entry>
<entry>Indicates a radio button object.</entry>
</row>
<row>
<entry> <code>radiobuttonmenuitem</code> </entry>
<entry>Indicates a menuitem with associated radio button.</entry>
</row>
<row>
<entry> <code>rcdata</code> </entry>
<entry>Indicates raw data resources for an application.</entry>
</row>
<row>
<entry> <code>row</code> </entry>
<entry>Indicates a row in a table.</entry>
</row>
<row>
<entry> <code>rtext</code> </entry>
<entry>Indicates a Windows RC RTEXT control.</entry>
</row>
<row>
<entry> <code>scrollpane</code> </entry>
<entry>Indicates a user navigable container used to show a portion
of a document.</entry>
</row>
<row>
<entry> <code>separator</code> </entry>
<entry>Indicates a generic divider object (e.g. menu group separator).</entry>
</row>
<row>
<entry> <code>shortcut</code> </entry>
<entry>Windows accelerators, shortcuts in resource or property files.</entry>
</row>
<row>
<entry> <code>spinner</code> </entry>
<entry>Indicates a UI control to indicate process activity but not
progress.</entry>
</row>
<row>
<entry> <code>splitter</code> </entry>
<entry>Indicates a splitter bar.</entry>
</row>
<row>
<entry> <code>state3</code> </entry>
<entry>Indicates a Windows RC STATE3 control.</entry>
</row>
<row>
<entry> <code>statusbar</code> </entry>
<entry>Indicates a window for providing feedback to the users, like
'read-only', etc.</entry>
</row>
<row>
<entry> <code>string</code> </entry>
<entry>Indicates a string, for example an entry in a STRINGTABLE resource
in Windows.</entry>
</row>
<row>
<entry> <code>tabcontrol</code> </entry>
<entry>Indicates a layers of controls with a tab to select layers.</entry>
</row>
<row>
<entry> <code>table</code> </entry>
<entry>Indicates a display and edits regular two-dimensional tables
of cells.</entry>
</row>
<row>
<entry> <code>textbox</code> </entry>
<entry>Indicates a XUL textbox element.</entry>
</row>
<row>
<entry> <code>togglebutton</code> </entry>
<entry>Indicates a UI button that can be toggled to on or off state.</entry>
</row>
<row>
<entry> <code>toolbar</code> </entry>
<entry>Indicates an array of controls, usually buttons.</entry>
</row>
<row>
<entry> <code>tooltip</code> </entry>
<entry>Indicates a pop up tool tip text.</entry>
</row>
<row>
<entry> <code>trackbar</code> </entry>
<entry>Indicates a bar with a pointer indicating a position within
a certain range.</entry>
</row>
<row>
<entry> <code>tree</code> </entry>
<entry>Indicates a control that displays a set of hierarchical data.</entry>
</row>
<row>
<entry> <code>uri</code> </entry>
<entry>Indicates a URI (URN or URL).</entry>
</row>
<row>
<entry> <code>userbutton</code> </entry>
<entry>Indicates a Windows RC USERBUTTON control.</entry>
</row>
<row>
<entry> <code>usercontrol</code> </entry>
<entry>Indicates a user-defined control like CONTROL control in Windows.</entry>
</row>
<row>
<entry> <code>var</code> </entry>
<entry>Indicates the text of a variable.</entry>
</row>
<row>
<entry> <code>versioninfo</code> </entry>
<entry>Indicates version information about a resource like VERSIONINFO
in Windows.</entry>
</row>
<row>
<entry> <code>vscrollbar</code> </entry>
<entry>Indicates a vertical scrollbar.</entry>
</row>
<row>
<entry> <code>window</code> </entry>
<entry>Indicates a graphical window.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group"> <code>&lt;group></code> 
 </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link>, <link linkend="target"
> <code>&lt;target></code> </link
>, <link linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>, <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link>, <link
linkend="bin-target"> <code>&lt;bin-target></code
> </link>.</para>
<para id="rid">rid</para>
<para> <emphasis>Reference identifier</emphasis> - The <code>rid</code
> attribute is used to link paired inline elements. The <code>rid</code
> attribute of a begin-paired-code element should have the same
value as the close-paired-code element. For example: <code>&lt;bx
id="1" rid="1"/> ... &lt;ex id="3" rid="1"/></code> indicates 
these elements are paired. If the <code>rid</code> attribute is not
 present (in a 1.0 document for example), the attribute <code> 
 <link linkend="id">id</link> </code> is used to match both tags.
For example: <code>&lt;bpt id='5'>xx&lt;/bpt> ... &lt;ept id='5'>xx&lt;/ept></code
>.</para>
<para>Value description:</para>
<para>Alpha-numeric without spaces.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="bpt"> <code>&lt;bpt></code> 
 </link>, <link linkend="ept"> <code>&lt;ept></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link> , <link linkend="bx"> 
 <code>&lt;bx/></code> </link>, <link
linkend="ex"> <code>&lt;ex/></code> 
 </link>.</para>
<para id="size-unit">size-unit</para>
<para> <emphasis>Unit of size attributes</emphasis> - The <code
>size-unit</code> attribute specifies the units of measure used
in the <code> <link linkend="maxheight">maxheight</link> </code
>, <code> <link linkend="minheight">minheight</link> </code
>, <code> <link linkend="maxwidth">maxwidth</link> </code>,
and <code> <link linkend="minwidth">minwidth</link> </code> attributes.
The <code>size-unit</code> attribute is not related to the <code
> <link linkend="coord">coord</link> </code> attribute.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>byte</code> </entry>
<entry>Indicates a size in 8-bit bytes.</entry>
</row>
<row>
<entry> <code>char</code> </entry>
<entry>Indicates a size in Unicode characters.</entry>
</row>
<row>
<entry> <code>col</code> </entry>
<entry>Indicates a size in columns. Used for HTML text area.</entry>
</row>
<row>
<entry> <code>cm</code> </entry>
<entry>Indicates a size in centimeters.</entry>
</row>
<row>
<entry> <code>dlgunit</code> </entry>
<entry>Indicates a size in dialog units, as defined in Windows resources.</entry>
</row>
<row>
<entry> <code>em</code> </entry>
<entry>Indicates a size in 'font-size' units (as defined in CSS).</entry>
</row>
<row>
<entry> <code>ex</code> </entry>
<entry>Indicates a size in 'x-height' units (as defined in CSS).</entry>
</row>
<row>
<entry> <code>glyph</code> </entry>
<entry>Indicates a size in glyphs. A glyph is considered to be one
or more combined Unicode characters that represent a single displayable
text character. Sometimes referred to as a 'grapheme cluster'</entry>
</row>
<row>
<entry> <code>in</code> </entry>
<entry>Indicates a size in inches.</entry>
</row>
<row>
<entry> <code>mm</code> </entry>
<entry>Indicates a size in millimeters.</entry>
</row>
<row>
<entry> <code>percent</code> </entry>
<entry>Indicates a size in percentage.</entry>
</row>
<row>
<entry> <code>pixel</code> </entry>
<entry>Indicates a size in pixels.</entry>
</row>
<row>
<entry> <code>point</code> </entry>
<entry>Indicates a size in point.</entry>
</row>
<row>
<entry> <code>row</code> </entry>
<entry>Indicates a size in rows. Used for HTML text area.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>pixel.</para>
<para>Used in:</para>
<para> <link linkend="group">&lt;group></link>, <link
linkend="trans-unit">&lt;trans-unit></link>.</para>
<para id="source-language"> source-language</para>
<para> <emphasis>Source language</emphasis> - The language for the
 <code> <link linkend="source">&lt;source></link> </code> elements
in the given <code> <link linkend="file">&lt;file></link> </code
> element.</para>
<para>Value description:</para>
<para>A language code as described in the [<link linkend="refRFC4646"
>RFC 4646</link>], the successor to [RFC 3066]. The values for this
attribute follow the same rules as the values for <code> <link
linkend="xml_lang">xml:lang</link> </code>. Unlike the other XLIFF
attributes, the values for <code> <link linkend="xml_lang">xml:lang</link
> </code> are not case-sensitive. For more information see <ulink
url="http://www.w3.org/TR/REC-xml#sec-lang-tag";>the section on <code
>xml:lang</code> in the XML specification</ulink>, and the <ulink
url="http://www.w3.org/XML/xml-V10-2e-errata#E11";>erratum E11</ulink
> (which replaces RFC 1766 by RFC 3066).</para>
<para>The source language can be also specified by <code> <link
linkend="xml_lang">xml:lang</link> </code> in each <code> <link
linkend="source">&lt;source></link> </code> element. The values
of <code>source-language</code> and <code> <link linkend="xml_lang"
>xml:lang</link> </code> in <code> <link linkend="source">&lt;source></link
> </code> can be different only in an <code> <link
linkend="alt-trans">&lt;alt-trans></link> </code> element.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="state">state</para>
<para> <emphasis>State</emphasis> - The status of a particular 
 translation in a <code> <link linkend="target">&lt;target></link
> </code> or <code> <link linkend="bin-target">&lt;bin-target></link
> </code> element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>final</code> </entry>
<entry>Indicates the terminating state.</entry>
</row>
<row>
<entry> <code>needs-adaptation</code> </entry>
<entry>Indicates only non-textual information needs adaptation.</entry>
</row>
<row>
<entry> <code>needs-l10n</code> </entry>
<entry>Indicates both text and non-textual information needs adaptation.</entry>
</row>
<row>
<entry> <code>needs-review-adaptation</code> </entry>
<entry>Indicates only non-textual information needs review.</entry>
</row>
<row>
<entry> <code>needs-review-l10n</code> </entry>
<entry>Indicates both text and non-textual information needs review.</entry>
</row>
<row>
<entry> <code>needs-review-translation</code> </entry>
<entry>Indicates that only the text of the item needs to be reviewed.</entry>
</row>
<row>
<entry> <code>needs-translation</code> </entry>
<entry>Indicates that the item needs to be translated.</entry>
</row>
<row>
<entry> <code>new</code> </entry>
<entry>Indicates that the item is new. For example, translation units
that were not in a previous version of the document.</entry>
</row>
<row>
<entry> <code>signed-off</code> </entry>
<entry>Indicates that changes are reviewed and approved.</entry>
</row>
<row>
<entry> <code>translated</code> </entry>
<entry>Indicates that the item has been translated.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="target">&lt;target></link>, <link
linkend="bin-target">&lt;bin-target></link>.</para>
<para id="state-qualifier"> state-qualifier</para>
<para> <emphasis>State-qualifier</emphasis> - Describes the state
of a particular translation in a <code> <link linkend="target"
>&lt;target></link> </code> or <code> <link linkend="bin-target"
>&lt;bin-target></link> </code> element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>exact-match</code> </entry>
<entry>Indicates an exact match. An exact match occurs when a source
text of a segment is exactly the same as the source text of a segment
that was translated previously.</entry>
</row>
<row>
<entry> <code>fuzzy-match</code> </entry>
<entry>Indicates a fuzzy match. A fuzzy match occurs when a source
text of a segment is very similar to the source text of a segment
that was translated previously (e.g. when the difference is casing,
a few changed words, white-space discripancy, etc.).</entry>
</row>
<row>
<entry> <code>id-match</code> </entry>
<entry>Indicates a match based on matching IDs (in addition to matching
text).</entry>
</row>
<row>
<entry> <code>leveraged-glossary</code> </entry>
<entry>Indicates a translation derived from a glossary.</entry>
</row>
<row>
<entry> <code>leveraged-inherited</code> </entry>
<entry>Indicates a translation derived from existing translation.</entry>
</row>
<row>
<entry> <code>leveraged-mt</code> </entry>
<entry>Indicates a translation derived from machine translation.</entry>
</row>
<row>
<entry> <code>leveraged-repository</code> </entry>
<entry>Indicates a translation derived from a translation repository.</entry>
</row>
<row>
<entry> <code>leveraged-tm</code> </entry>
<entry>Indicates a translation derived from a translation memory.</entry>
</row>
<row>
<entry> <code>mt-suggestion</code> </entry>
<entry>Indicates the translation is suggested by machine translation.</entry>
</row>
<row>
<entry> <code>rejected-grammar</code> </entry>
<entry>Indicates that the item has been rejected because of incorrect
grammar.</entry>
</row>
<row>
<entry> <code>rejected-inaccurate</code> </entry>
<entry>Indicates that the item has been rejected because it is incorrect.</entry>
</row>
<row>
<entry> <code>rejected-length</code> </entry>
<entry>Indicates that the item has been rejected because it is too
long or too short.</entry>
</row>
<row>
<entry> <code>rejected-spelling</code> </entry>
<entry>Indicates that the item has been rejected because of incorrect
spelling.</entry>
</row>
<row>
<entry> <code>tm-suggestion</code> </entry>
<entry>Indicates the translation is suggested by translation memory.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="target">&lt;target></link>, <link
linkend="bin-target">&lt;bin-target></link>.</para>
<para id="style">style</para>
<para> <emphasis>Style</emphasis> - The resource style of a control.
 For example, in Windows resources it corresponds to the STYLE 
statement.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="group">&lt;group></link>, <link
linkend="trans-unit">&lt;trans-unit></link>, <link linkend="target"
>&lt;target></link>, <link linkend="alt-trans">&lt;alt-trans></link
>.</para>
<para id="target-language"> target-language</para>
<para> <emphasis>Target language</emphasis> - The language for the
 <code> <link linkend="target">&lt;target></link> </code> elements
in the given <code> <link linkend="file">&lt;file></link> </code
> element.</para>
<para>Value description:</para>
<para>A language code as described in the [<link linkend="refRFC4646"
>RFC 4646</link>], the successor to [RFC 3066]. The values for this
attribute follow the same rules as the values for <code> <link
linkend="xml_lang">xml:lang</link> </code>. Unlike the other XLIFF
attributes, the values for <code> <link linkend="xml_lang">xml:lang</link
> </code> are not case-sensitive. For more information see <ulink
url="http://www.w3.org/TR/REC-xml#sec-lang-tag";>the section on <code
>xml:lang</code> in the XML specification</ulink>, and the <ulink
url="http://www.w3.org/XML/xml-V10-2e-errata#E11";>erratum E11</ulink
> (which replaces RFC 1766 by RFC 3066).</para>
<para>The target language can be also specified by <code> <link
linkend="xml_lang">xml:lang</link> </code> in each <code> <link
linkend="target">&lt;target></link> </code> element. The values
of <code>target-language</code> and <code> <link linkend="xml_lang"
>xml:lang</link> </code> in <code> <link linkend="target">&lt;target></link
> </code> can be different only when in an <link linkend="alt-trans"
> <code>&lt;alt-trans></code> </link
> element.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>.</para>
<para id="tool_elem">tool</para>
<para> <emphasis>Creation tool</emphasis> - The <code>tool</code
> attribute is used to specify the signature and version of the
tool that created or modified the document.</para>
<para>Important: The <code>tool</code> attribute was DEPRECATED
in version 1.1. Instead, use the <code> <link linkend="tool_elem"
>&lt;tool></link> </code> element and a <link linkend="tool-id"
>tool-id</link> attribute.</para>
<para>Value description:</para>
<para>Text</para>
<para>Default value:</para>
<para>manual.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="phase"> <code>&lt;phase></code
> </link>, <link linkend="alt-trans"> 
 <code>&lt;alt-trans></code> </link>.</para>
<para id="tool-company"> tool-company</para>
<para> <emphasis>Tool company</emphasis> - The <code>tool-company</code
> attribute specifies the company from which a tool originates.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="tool_elem">&lt;tool></link> </code
>.</para>
<para id="tool-id">tool-id</para>
<para> <emphasis>Tool identifier</emphasis> - The <code>tool-id</code
> attribute allows unique identification of a <link linkend="tool_elem"
> <code>&lt;tool></code> </link> element.
It is also used in other elements in the file to refer to the given <link
linkend="tool_elem"> <code>&lt;tool></code> 
 </link> element.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="phase"> <code>&lt;phase></code
> </link>, <link linkend="alt-trans"> 
 <code>&lt;alt-trans></code> </link>, <code> 
 <link linkend="tool_elem">&lt;tool></link> </code>.</para>
<para id="tool-name"> tool-name</para>
<para> <emphasis>Tool name</emphasis> - The <code>tool-name</code
> attribute specifies the name of a given tool.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <code> <link linkend="tool_elem">&lt;tool></link> </code
>.</para>
<para id="tool-version"> tool-version</para>
<para> <emphasis>Tool version</emphasis> - The <code>tool-version</code
> attribute specifies the version of a given tool.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="tool_elem">&lt;tool></link>.</para>
<para id="translate">translate</para>
<para> <emphasis>Translate</emphasis> - The <code>translate</code
> attribute indicates whether or not the text referred to should
be translated.</para>
<para>Value description:</para>
<para>Boolean: <code>yes</code> or <code>no</code>.</para>
<para>Default value:</para>
<para>yes.</para>
<para>Used in:</para>
<para> <code> <link linkend="group">&lt;group></link> </code
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link>.</para>
<para id="ts">ts</para>
<para> <emphasis>Tool-specific data</emphasis> - The <code>ts</code
> attribute allows you to include short data understood by a specific
 toolset. You can also use the <link linkend="prop"> 
 <code>&lt;prop></code> </link> element to define
large properties at the element level.</para>
<para>Important: The <code>ts</code> attribute was DEPRECATED in
version 1.1. Instead, use attributes defined in a namespace different
from XLIFF. See the <link linkend="Struct_Extension">Extensibility</link
> section for more information.</para>
<para>Value description:</para>
<para>Text. No value defined by the standard.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="group"> <code>&lt;group></code
> </link>, <link linkend="trans-unit"> 
 <code>&lt;trans-unit></code> </link>, <link
linkend="source"> <code>&lt;source></code> 
 </link>, <link linkend="target"> <code
>&lt;target></code> </link>, <link linkend="bin-unit"
> <code>&lt;bin-unit></code> </link
>, <link linkend="bin-source"> <code>&lt;bin-source></code
> </link>, <link linkend="bin-target"> 
 <code>&lt;bin-target></code> </link>, <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>, <link linkend="mrk"> <code
>&lt;mrk></code> </link>, <link linkend="g"> 
 <code>&lt;g></code> </link>, <link linkend="x"
> <code>&lt;x/></code> </link>, <link
linkend="bx"> <code>&lt;bx/></code> 
 </link>, <link linkend="ex"> <code>&lt;ex/></code
> </link> , <link linkend="bpt"> <code
>&lt;bpt></code> </link>, <link linkend="ept"> 
 <code>&lt;ept></code> </link>, <link
linkend="ph"> <code>&lt;ph></code> 
 </link> , <link linkend="it"> <code>&lt;it></code
> </link>.</para>
<para id="uid">uid</para>
<para> <emphasis>Unique ID</emphasis> - The <code>uid</code> attribute
 is used to provide a unique ID to identify the skeleton file.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="external-file"> <code>&lt;external-file></code
> </link> .</para>
<para id="unit">unit</para>
<para> <emphasis>Unit</emphasis> - The <code>unit</code> attribute
 specifies the units counted in a <link linkend="count"> 
 <code>&lt;count></code> </link> element.</para>
<para>Value description:</para>
<para>The pre-defined values are defined in the table below.</para>
<table>
<title></title>
<tgroup cols="2">
<colspec colname="col1"/>
<colspec colname="col2"/>
<tbody>
<row>
<entry> <emphasis>Value</emphasis> </entry>
<entry>Description</entry>
</row>
<row>
<entry> <code>word</code> </entry>
<entry>Refers to words.</entry>
</row>
<row>
<entry> <code>page</code> </entry>
<entry>Refers to pages.</entry>
</row>
<row>
<entry> <code>trans-unit</code> </entry>
<entry>Refers to &lt;trans-unit> elements.</entry>
</row>
<row>
<entry> <code>bin-unit</code> </entry>
<entry>Refers to &lt;bin-unit> elements.</entry>
</row>
<row>
<entry> <code>glyph</code> </entry>
<entry>Refers to glyphs.</entry>
</row>
<row>
<entry> <code>item</code> </entry>
<entry>Refers to &lt;trans-unit> and/or &lt;bin-unit> elements.</entry>
</row>
<row>
<entry> <code>instance</code> </entry>
<entry>Refers to the occurrences of instances defined by the count-type
value.</entry>
</row>
<row>
<entry> <code>character</code> </entry>
<entry>Refers to characters.</entry>
</row>
<row>
<entry> <code>line</code> </entry>
<entry>Refers to lines.</entry>
</row>
<row>
<entry> <code>sentence</code> </entry>
<entry>Refers to sentences.</entry>
</row>
<row>
<entry> <code>paragraph</code> </entry>
<entry>Refers to paragraphs.</entry>
</row>
<row>
<entry> <code>segment</code> </entry>
<entry>Refers to segments.</entry>
</row>
<row>
<entry> <code>placeable</code> </entry>
<entry>Refers to placeables (inline elements).</entry>
</row>
</tbody>
</tgroup>
</table>
<para>In addition, user-defined values can be used with this attribute.
A user-defined value must start with an "<code>x-</code>" prefix.</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="count"> <code>&lt;count></code> 
 </link>.</para>
<para id="version">version</para>
<para> <emphasis>XLIFF version</emphasis> - The <code>version</code
> attribute is used to specify the format version of the XLIFF 
 document. This corresponds to the version number of the XLIFF specification
that is being adhered to.</para>
<para>Value description:</para>
<para>Text.</para>
<para>Default value:</para>
<para> <code>1.2</code> </para>
<para>Used in:</para>
<para> <link linkend="xliff"> <code>&lt;xliff></code> 
 </link>.</para>
<para id="xid">xid</para>
<para> <emphasis>Extern Reference identifier</emphasis> - The <code
>xid</code> attribute is used to link an inline element to a different <code
> <link linkend="trans-unit">&lt;trans-unit></link> </code> 
 or <code> <link linkend="bin-unit">&lt;bin-unit></link> </code
> element. For example, to link the text within a code to a corresponding
 translation unit.</para>
<para>Value description:</para>
<para>The value of the referenced <code> <link linkend="id">id</link
> </code> .</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="bpt"> <code>&lt;bpt></code> 
 </link>, <link linkend="ept"> <code>&lt;ept></code
> </link>, <link linkend="it"> <code
>&lt;it></code> </link> , <code> <link linkend="ph"
>&lt;ph></link> </code>, <code> <link linkend="g">&lt;g></link
> </code>, <code> <link linkend="x">&lt;x/></link> </code
>, <link linkend="bx"> <code>&lt;bx/></code> 
 </link>, <link linkend="ex"> <code>&lt;ex/></code
> </link>, <code> <link linkend="sub">&lt;sub></link
> </code> .</para>
</section>
<section>
<title id="Specs_Attr_Xml">XML Namespace Attributes</title>
<para id="xml_lang"> xml:lang</para>
<para> <emphasis>Language</emphasis> - The <code>xml:lang</code
> attribute specifies the language variant of the text of a given
 element. For example: <code>xml:lang="fr-FR"</code> indicates
the French language as spoken in France.</para>
<para>Value description:</para>
<para>A language code as described in the [<link linkend="refRFC4646"
>RFC 4646</link>], the successor to [RFC 3066]. This declared value
is considered to apply to all elements within the content of the
element where it is specified, unless overridden with another instance
of the <code>xml:lang</code> attribute. Unlike the other XLIFF attributes,
the values for <code>xml:lang</code> are not case-sensitive. For
more information see <ulink
url="http://www.w3.org/TR/REC-xml#sec-lang-tag";>the section on <code
>xml:lang</code> in the XML specification</ulink>, and the <ulink
url="http://www.w3.org/XML/xml-V10-2e-errata#E11";>erratum E11</ulink
> (which replaces RFC 1766 by RFC 3066).</para>
<para>Default value:</para>
<para>Undefined.</para>
<para>Used in:</para>
<para> <link linkend="xliff"> <code>&lt;xliff></code> 
 </link>, <link linkend="note"> <code>&lt;note></code
> </link>, <link linkend="prop"> <code
>&lt;prop></code> </link>, <link linkend="source"> 
 <code>&lt;source></code> </link>, <link
linkend="target"> <code>&lt;target></code> 
 </link>, <link linkend="alt-trans"> <code
>&lt;alt-trans></code> </link>.</para>
<para id="xml_space">xml:space</para>
<para> <emphasis>White spaces</emphasis> - The <code>xml:space</code
> attribute specifies how white spaces (ASCII spaces, tabs and 
 line-breaks) should be treated.</para>
<para>Value description:</para>
<para> <code>default</code> or <code>preserve</code>. The value <code
>default</code> signals that an application's default white-space
processing modes are acceptable for this element; the value <code
>preserve</code> indicates the intent that applications preserve
all the white space. This declared intent is considered to apply
to all elements within the content of the element where it is specified,
unless overridden with another instance of the <code>xml:space</code
> attribute.</para>
<para>For more information <ulink
url="http://www.w3.org/TR/REC-xml#sec-white-space";>see the section
 on <code>xml:space</code> in the XML specification</ulink>.</para>
<para>Default value:</para>
<para> <code>default</code>.</para>
<para>Used in:</para>
<para> <link linkend="file"> <code>&lt;file></code> 
 </link>, <link linkend="group"> <code>&lt;group></code
> </link>, <link linkend="trans-unit"> 
 <code>&lt;trans-unit></code> </link>, <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para>
</section>
</section>
</section>
<section>
<title>Conformance</title>
<para>The last section contains the conformance clauses/statements.</para>
</section>
<appendix>
<title id="AppTree">XLIFF Tree Structure</title>
<para>The following figure shows the possible structure as a tree.
Each element is followed by notation indicating its possible occurrence
according to the corresponding legend.</para>
<programlisting>
(legend: 1 = one
 + = one or more
 ? = zero or one
 * = zero, one or more)

<link linkend="xliff">&lt;xliff></link>1
| |
| +--- [Extension Point]
| |
+--- <link linkend="file">&lt;file></link>+
 |
 +--- <link linkend="header">&lt;header></link>?
 | |
 | +--- <link linkend="skl">&lt;skl></link>?
 | | |
 | | +--- (<link linkend="internal-file">&lt;internal-file></link
> | <link linkend="external-file">&lt;external-file></link>)1
 | |
 | +--- <link linkend="phase-group">&lt;phase-group></link>?
 | | |
 | | +--- <link linkend="phase">&lt;phase></link>+
 | | |
 | | +--- <link linkend="note">&lt;note></link>*
 | |
 | +--- <link linkend="glossary">&lt;glossary></link>*
 | | |
 | | +--- (<link linkend="internal-file">&lt;internal-file></link
> | <link linkend="external-file">&lt;external-file></link>)1
 | |
 | +--- <link linkend="reference">&lt;reference></link>*
 | | |
 | | +--- (<link linkend="internal-file">&lt;internal-file></link
> | <link linkend="external-file">&lt;external-file></link>)1
 | |
 | +--- <link linkend="count-group">&lt;count-group></link>*
 | | |
 | | +--- <link linkend="count">&lt;count></link>*
 | |
 | +--- <link linkend="tool_elem">&lt;tool></link>*
 | | |
 | | +--- [Extension Point]
 | |
 | +--- <link linkend="prop-group">&lt;prop-group></link>*
 | | |
 | | +--- <link linkend="prop">&lt;prop></link>*
 | |
 | +--- [Extension Point]
 | |
 | +--- <link linkend="note">&lt;note></link>*
 |
 +--- <link linkend="body">&lt;body></link>1
 |
 +--- <link linkend="group">&lt;group></link>*
 | |
 | +--- <link linkend="context-group">&lt;context-group></link>*
 | | |
 | | +--- <link linkend="context">&lt;context></link>+
 | |
 | +--- <link linkend="context-group">&lt;count-group></link>*
 | | |
 | | +--- <link linkend="count">&lt;count></link>*
 | |
 | +--- <link linkend="prop-group">&lt;prop-group></link>*
 | | |
 | | +--- <link linkend="prop">&lt;prop></link>*
 | |
 | +--- [Extension Point]
 | |
 | +--- <link linkend="note">&lt;note></link>*
 | |
 | +--- At least one of: (<link linkend="group">&lt;group></link>* <link
linkend="trans-unit">&lt;trans-unit></link>* <link linkend="bin-unit"
>&lt;bin-unit></link>*)
 |
 +--- <link linkend="trans-unit">&lt;trans-unit></link>*
 | |
 | +--- <link linkend="source">&lt;source></link>1
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | |
 | +--- <link linkend="target">&lt;target></link>?
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | |
 | +--- <link linkend="context-group">&lt;context-group></link>*
 | | |
 | | +--- <link linkend="context">&lt;context></link>+
 | |
 | +--- <link linkend="count-group">&lt;count-group></link>*
 | | |
 | | +--- <link linkend="count">&lt;count></link>*
 | |
 | +--- <link linkend="prop-group">&lt;prop-group></link>*
 | | |
 | | +--- <link linkend="prop">&lt;prop></link>*
 | |
 | +--- <link linkend="seg-source">&lt;seg-source></link>?
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | |
 | +--- [Extension Point]
 | |
 | +--- <link linkend="note">&lt;note></link>*
 | |
 | +--- <link linkend="alt-trans">&lt;alt-trans></link>*
 | |
 | +--- <link linkend="context-group">&lt;context-group></link>*
 | | |
 | | +--- <link linkend="context">&lt;context></link>+
 | |
 | +--- <link linkend="source">&lt;source></link>?
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | | | +--- <link linkend="target">&lt;target></link>+
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | |
 | +--- <link linkend="prop-group">&lt;prop-group></link>*
 | | |
 | | +--- <link linkend="prop">&lt;prop></link>*
 | |
 | +--- <link linkend="seg-source">&lt;seg-source></link>?
 | | |
 | | +--- [<link linkend="InLineElemDiagram">Inline Elements</link
>]
 | |
 | +--- [Extension Point]
 | |
 | +---- <link linkend="note">&lt;note></link>*
 |
 +--- <link linkend="bin-unit">&lt;bin-unit></link>*
 |
 +--- <link linkend="bin-source">&lt;bin-source></link>1 &amp; <link
linkend="bin-target">&lt;bin-target></link>?
 | |
 | +--- (<link linkend="internal-file">&lt;internal-file></link> | <link
linkend="external-file">&lt;external-file></link>)1
 |
 +--- <link linkend="context-group">&lt;context-group></link>*
 | |
 | +--- <link linkend="context">&lt;context></link>+
 |
 +--- <link linkend="count-group">&lt;count-group></link>*
 | |
 | +--- <link linkend="count">&lt;count></link>*
 |
 +--- <link linkend="prop-group">&lt;prop-group></link>*
 | |
 | +--- <link linkend="prop">&lt;prop></link>*
 |
 +--- [Extension Point]
 |
 +--- <link linkend="note">&lt;note></link>*
 |
 +--- <code id="InLineElemDiagram"></code>&lt;trans-unit>*

Struct_Extension_Elements



Inline Elements:

---+--- <link linkend="ph">&lt;ph></link>*
 | |
 | +--- <link linkend="sub">&lt;sub></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="it">&lt;it></link>*
 | |
 | +--- <link linkend="sub">&lt;sub></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="bpt">&lt;bpt></link>*
 | |
 | +--- <link linkend="sub">&lt;sub></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="ept">&lt;ept></link>*
 | |
 | +--- <link linkend="sub">&lt;sub></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="x">&lt;g></link>*<link linkend="bx"></link> | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="x">&lt;x/></link>*<link linkend="bx"></link> | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="bx">&lt;bx/></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="ex">&lt;ex/></link>*
 | |
 | +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]
 |
 +--- <link linkend="mrk">&lt;mrk></link>*
 |
 +--- [<link linkend="InLineElemDiagram">Inline Elements</link>]


</programlisting>
</appendix>
<appendix>
<title id="AppDTD">Schema</title>
<itemizedlist>
<listitem><para> The XML schema for XLIFF is available as strict
or transitional: </para>
<itemizedlist>
<listitem><para>Strict: <ulink
url="http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core-1.2-strict.xsd";
> xliff-core-1.2-strict.xsd</ulink> </para></listitem>
<listitem><para>Transitional: <ulink
url="http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core-1.2-transitional.xsd";
> xliff-core-1.2-transitional.xsd</ulink> </para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</appendix>
<appendix role="non-normative">
<title id="AppChanges">Changes Since Previous Version (Non-Normative)</title>
<para>The changes in this version relative to the previous version
are as follows:</para>
<itemizedlist>
<listitem><para>Revised version number from 1.1 to 1.2.</para>
</listitem>
<listitem><para>A new section (2.7) describing the <link
linkend="Struct_Nonequiv">Non Equivalent Translation</link> concept
 including relevant examples.</para></listitem>
<listitem><para>A new section (2.8) describing the <link
linkend="Struct_Grouping">Merged-translations</link> concept including
 relevant examples.</para></listitem>
<listitem><para>A new section (2.9) describing the <link
linkend="Struct_Segmentation">Segmentation</link> concept including
 relevant examples.</para></listitem>
<listitem><para>Add the documentation concerning the <link
linkend="equiv-trans"> <code>equiv-trans</code> 
 </link> attribute regarding <link linkend="trans-unit"
> <code>&lt;trans-unit></code> </link
> elements</para></listitem>
<listitem><para>Add the documentation concerning the <link
linkend="merged-trans"> <code>merged-trans</code
> </link> attribute for <link linkend="group"> 
 <code>&lt;group></code> </link> elements
to section 3.2 (Elements).</para></listitem>
<listitem><para>Add the <link linkend="seg-source"> 
 <code>&lt;seg-source></code> </link> element as
optional in the <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link> and <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> content models, at the same level as <code
> <link linkend="source">&lt;source></link> </code> .</para>
</listitem>
<listitem><para>Create a new value "seg" for the <link linkend="mtype"
> <code>mtype</code> </link> attribute
of the <link linkend="mrk"> <code>&lt;mrk></code
> </link> element.</para></listitem>
<listitem><para>Add <link linkend="mid"> <code>mid</code
> </link> as an optional attribute for the <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> element.</para></listitem>
<listitem><para>Updated <link linkend="AppCommittee">Technical Committee</link
> section to reflect membership status as of 10 Oct 2005.</para>
</listitem>
<listitem><para>Updated document <link linkend="AppDTD">link and name
of XSD</link>, and removed all references to DTD.</para></listitem>
<listitem><para>Updated <link linkend="AppTree">tree structure</link
> with new elements.</para></listitem>
<listitem><para>Fixed typo in <link linkend="phase"> 
 <code>&lt;phase></code> </link> section, changing
 "optional phase-name" to "required phase-name", as reported
in this comment email -> <ulink
url="http://lists.oasis-open.org/archives/xliff-comment/200509/msg00001.html";
> http://lists.oasis-open.org/archives/xliff-comment/200509/msg00001.html</ulink
> </para></listitem>
<listitem><para>Fixed additional typos as submitted via comment email
from Yves Savourel on 2 November 2005 (email not visible in 
archive).</para></listitem>
<listitem><para>Changed name attribute for <link linkend="context-group"
> <code>&lt;context-group></code> 
 </link> from required to optional, and modified description.</para>
</listitem>
<listitem><para>Added extension point at <link linkend="xliff"> 
 <code>&lt;xliff></code> </link> </para>
</listitem>
<listitem><para>Added <link linkend="alttranstype"> 
 <code>alttranstype</code> </link> attribute to <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para></listitem>
<listitem><para>Deprecated the use of multiple <link linkend="target"
> <code>&lt;target></code> </link
> elements in a single <link linkend="alt-trans"> 
 <code>&lt;alt-trans></code> </link>.</para>
</listitem>
<listitem><para>Deprecated the <link linkend="restype"> 
 <code>restype</code> </link> attribute in <link
linkend="target"> <code>&lt;target></code> 
 </link> element. </para></listitem>
<listitem><para>Introduced <link linkend="phase-name"> 
 <code>phase-name</code> </link> attribute in <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link>.</para></listitem>
<listitem><para>Introduced convention for more recent <link
linkend="alt-trans"> <code>&lt;alt-trans></code
> </link> elements to appear before older ones.</para>
</listitem>
<listitem><para>Fixed typo in section 2.4 Inline Elements, "act has
 placeholders" -> "act as placeholders" </para></listitem>
<listitem><para>Fixed a number of problems with anchors and hyperlinks.</para>
</listitem>
<listitem><para>Added explanation for deprecating the <link
linkend="restype"> <code>restype</code> 
 </link> attribute in <link linkend="target"> 
 <code>&lt;target></code> </link> element.</para>
</listitem>
<listitem><para>Corrected missing <code> <link
linkend="state-qualifier">state-qualifier</link> </code> attribute
in <link linkend="bin-target"> <code>&lt;bin-target></code
> </link> element. </para></listitem>
<listitem><para>In <link linkend="group">&lt;group></link> element
rewrote: "One or more <link linkend="group"> <code
>&lt;group></code> </link>, <link linkend="trans-unit"
> <code>&lt;trans-unit></code> </link
>, <link linkend="bin-unit"> <code>&lt;bin-unit></code
> </link> elements, in any order." to align with
the schema definition: "Zero, one or more <link linkend="group"
> <code>&lt;group></code> </link
>, <link linkend="trans-unit"> <code>&lt;trans-unit></code
> </link>, <link linkend="bin-unit"> 
 <code>&lt;bin-unit></code> </link> elements, in
 any order."</para></listitem>
<listitem><para>Corrected broken link to <link linkend="alt-trans"
>&lt;alt-trans></link> from <link linkend="phase-name">phase-name</link
>. </para></listitem>
<listitem><para>Added <link linkend="xliff"> <code
>&lt;xliff></code> </link> and <link linkend="seg-source"
> <code>&lt;seg-source></code> </link
> to <link linkend="Struct_Extension_Elements">Adding Elements</link
> section.</para></listitem>
<listitem><para>Clarified <link linkend="group"> <code>&lt;group></code
> </link>, <link linkend="trans-unit"> <code
>&lt;trans-unit></code> </link> and <link
linkend="bin-unit"> <code>&lt;bin-unit></code> </link
> to explicitly specify <link linkend="id"> <code
>id</code> </link> attribute is unique.</para>
</listitem>
<listitem><para>Added guidelines for TMX interchange to inline tag
discussion in <link linkend="Specs_Elem_Inline">Inline Elements</link
> section. </para></listitem>
<listitem><para>Small. change to inline tags section to - "use <link
linkend="bpt"> <code>&lt;bpt></code> 
 </link> and <link linkend="ept"> <code>&lt;ept></code
> </link> instead of <link linkend="g"> 
 <code>&lt;g></code> </link> and <link linkend="ph"
> <code>&lt;ph></code> </link> tags
instead of <link linkend="x"> <code>&lt;x/></code
> </link>" , and added <link linkend="equiv-text"> 
 <code>equiv-text</code> </link> attribute
 description and appended to all inline tags.</para></listitem>
<listitem><para>Numerous minor corrections: including: <code> <link
linkend="xliff">&lt;xliff></link> </code> and <code> <link
linkend="seg-source">&lt;seg-source></link> </code> to section 
 2.5.4., added <link linkend="alttranstype"> <code
>alttranstype</code> </link> and <link linkend="reformat"
> <code>reformat</code> </link>, added <link
linkend="equiv-trans"> <code>equiv-trans</code> </link
> to <link linkend="target"> <code>&lt;target></code> 
 </link>, added <link linkend="merged-trans"> <code>merged-trans</code
> </link> to <code> <link linkend="group">&lt;group></link
> </code>, and added anchor for <code> <link
linkend="seg-source">&lt;seg-source></link> </code> in <code
> <link linkend="alt-trans">&lt;alt-trans></link>.</code> </para>
</listitem>
<listitem><para>Revised <link linkend="Struct_Segmentation">Segmentation</link
> section to describe representation of spaces in <link
linkend="seg-source"> <code>&lt;seg-source></code
> </link>.</para></listitem>
<listitem><para>Added text "non-XLIFF attributes" to all element 
 definitions that support optional non-XLIFF attributes.</para>
</listitem>
<listitem><para>Added text to <code> <link linkend="xliff">&lt;xliff></link
> </code> indicating it supports non-XLIFF elements. </para>
</listitem>
<listitem><para>Modified "uniquely identifies ... within file" to
 "uniquely identifies ... within &lt;file> element" in <code
> <link linkend="phase">&lt;phase></link>, <link
linkend="context-group">&lt;context-group></link> and <link
linkend="tool_elem">&lt;tool></link> .</code> </para></listitem>
<listitem><para>Updated date of [XML Names] reference to latest 
 revision. </para></listitem>
<listitem><para>Removed SRX specification version numbers, and edited
text in <link linkend="Struct_Segmentation">Segmentation</link
> section. </para></listitem>
<listitem><para>Updated RFC3066 to <link linkend="refRFC4646">[RFC4066]</link
>. </para></listitem>
<listitem><para>Edited contents of <code> <link linkend="seg-source"
>&lt;seg-source></link> </code> to be same as <code> <link
linkend="source">&lt;source></link> </code> as per schema.</para>
</listitem>
<listitem><para>Corrected typo "merged-trans element" to "merged-trans
attribute".</para></listitem>
<listitem><para>Corrected typos as pointed out by <ulink
url="http://lists.oasis-open.org/archives/xliff-comment/200610/msg00001.html";
> Asgeir in an email</ulink> to the comments list , <ulink
url="http://lists.oasis-open.org/archives/xliff-comment/200610/msg00000.html";
> including removing from section 2.5.3</ulink> the <link
linkend="priority">priority</link> attribute erroneously included
in the list of extensible attributes.</para></listitem>
<listitem><para>Added note to section 2.5.4 indicating that non-XLIFF
content will not be validated beyond ensuring it is well-formed.</para>
</listitem>
<listitem><para>Fixed typo in section 3.1 where sample XLIFF XML declaration
 was erroneously located in the preceding paragraph.</para></listitem>
<listitem><para>Corrected <link linkend="alt-trans">&lt;alt-trans></link
> contents section so number of <link linkend="target"> 
 <code>&lt;target></code> </link> elements
is one (multiple <link linkend="target"> <code>&lt;target></code
> </link>s in <link linkend="alt-trans">&lt;alt-trans></link
> deprecated in 1.2)</para></listitem>
<listitem><para>Corrected section 2.9 segmentation sample for an 
 alt-trans. </para></listitem>
<listitem><para>Clarified validation rules for strict and transitional
 variants in <link linkend="Intro_Flavors">section 1.1</link>. </para>
</listitem>
</itemizedlist>
</appendix>
<appendix role="non-normative">
<title id="AppNaming">Naming Guidelines (Non-Normative)</title>
<para>The following naming guidelines were used in writing this
specification.</para>
<section>
<title id="AppNaming_ElemAttr">Elements and Attributes</title>
<para>The following guidelines were used for element and attribute
naming.</para>
<orderedlist>
<listitem><para>Standard English letters.</para></listitem>
<listitem><para>Lower case only.</para></listitem>
<listitem><para>Hyphen is the preferred mean for creating composite
 names.</para></listitem>
<listitem><para>Industry standard terminology should be followed where
 possible.</para></listitem>
</orderedlist>
</section>
<section>
<title id="AppNaming_AttrValues">Attribute Values</title>
<para>Attribute values are case sensitive. It is recommended that
lower-case values are used. The specification recommends a number
of values for some attributes, these are all lower-case.</para>
<para>Where multiple attribute values are to be used in an XLIFF
document, two approaches are used: For enumerated attributes (such
as the <code> <link linkend="purpose">purpose</link> </code> 
attribute of <code> <link linkend="context-group">&lt;context-group></link
> </code>) the separator must be a space. For other textual attributes
based on string, the specification recommends the use of the semi-colon
as a separator for values. For example, multiple contacts may be
listed for a <code> <link linkend="file">&lt;file></link> </code
> with the attribute written thusly: <code>contact-name="Frank 
 Sinatra;Sammy Davis Jnr;Dean Martin"</code> .</para>
</section>
<section>
<title id="AppNaming_PI">Processing Instructions</title>
<para>XLIFF reserves processing instructions that begin with "<code
>xliff-</code>".</para>
</section>
<section>
<title id="AppNaming_Ext">XLIFF File Extension</title>
<para>XLIFF documents use the <code>.xlf</code> extension. No other
extension is recommended by the specification.</para>
</section>
</appendix>
<appendix role="non-normative">
<title id="AppCommittee">Acknowledgements</title>
<para>The XLIFF Technical Committee at OASIS is composed of the following
members:</para>
<itemizedlist spacing="compact">
<listitem><para>Anastasiou, Dr. Dimitra, Localisation Research Centre</para>
</listitem>
<listitem><para>Filip, Dr. David, Localisation Research Centre</para>
</listitem>
<listitem><para>Lommel, Mr. Arle, Localization Industry Standards
Assoc.</para></listitem>
<listitem><para>Morado Vazquez, Lucia, Localisation Research Centre</para>
</listitem>
<listitem><para>Raya, Mr. Rodolfo (Secretary), Maxprograms</para>
</listitem>
<listitem><para>Reynolds, Peter, Polish Association of Translation
Agencies</para></listitem>
<listitem><para>Savourel, Mr. Yves, ENLASO Corporation</para></listitem>
<listitem><para>Schnabel, Bryan, Tektronix</para></listitem>
<listitem><para>Swift, Mr. Andrew, SDL International</para></listitem>
</itemizedlist>
</appendix>
<appendix>
<title id="SectionReferences">References</title>
<section>
<title id="ref-normative">Normative</title>
<para id="refCSS">[CSS]</para>
<para> <ulink url="http://www.w3.org/Style/CSS/#specs";>CSS Specifications</ulink
>. W3C (World Wide Web Consortium).</para>
<para id="refIANACharsets">[IANA Charsets]</para>
<para> <ulink url="http://www.iana.org/assignments/character-sets";
> <emphasis>IANA Names for Character Sets</emphasis
> </ulink>. IANA (Internet Assigned Numbers Authority),
Aug 2001</para>
<para id="refISO639">[ISO 639]</para>
<para> <ulink
url="http://lcweb.loc.gov/standards/iso639-2/langhome.html";> 
 <emphasis>Codes for the Representation of Names of Languages</emphasis
> </ulink>. ISO (International Standards Organization),
Nov 2001.</para>
<para id="refISO3166">[ISO 3166]</para>
<para> <ulink
url="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html";
> <emphasis>Codes for the representation of names of
countries and their subdivisions</emphasis> </ulink
>. ISO (International Organization for Standardization), Jun 2000.</para>
<para id="refISO8601">[ISO 8601]</para>
<para> <ulink url="http://www.w3.org/TR/1998/NOTE-datetime-19980827";
> <emphasis>Representation of dates and times</emphasis
> </ulink>. ISO (International Organization for Standardization),
Dec 2000.</para>
<para id="refRFC1341">[RFC 1341]</para>
<para> <ulink url="http://www.ietf.org/rfc/rfc1341.txt";> 
 <emphasis>Multipurpose Internet Mail Extensions</emphasis
> </ulink>. IETF (Internet Engineering Task Force), 
Jun 1992.</para>
<para id="refRFC4646">[RFC 4646]</para>
<para> <ulink url="http://www.ietf.org/rfc/rfc4646.txt";> 
 <emphasis>RFC 4646 Tags for the Identification of Languages</emphasis
> </ulink>. IETF (Internet Engineering Task Force),
Sep 2006.</para>
<para id="refXML">[XML 1.0]</para>
<para> <emphasis> <ulink
url="http://www.w3.org/TR/REC-xml";>Extensible Markup Language 
(XML) 1.0</ulink> </emphasis> . W3C (World Wide Web
Consortium).</para>
<para id="refXMLNames">[XML Names]</para>
<para> <emphasis> <ulink
url="http://www.w3.org/TR/REC-xml-names/";>Namespaces in XML</ulink
> </emphasis> . W3C (World Wide Web Consortium),
August 16, 2006.</para>
</section>
<section>
<title id="ref-non-normative">Non-Normative</title>
<para id="refISO">[ISO]</para>
<para> <ulink url="http://www.iso.org/";> <emphasis
>International Organization for Standardization</emphasis> 
 </ulink> Web site.</para>
<para id="refLISA">[LISA]</para>
<para> <emphasis> <ulink url="http://www.lisa.org/";
>Localisation Industry Standards Association</ulink> 
 </emphasis> Web site.</para>
<para id="refOASIS">[OASIS]</para>
<para> <ulink url="http://www.oasis-open.org/";> <emphasis
>Organization for the Advancement of Structured Information Standards</emphasis
> </ulink> Web site.</para>
<para id="refOpenTag">[OpenTag 1.2]</para>
<para> <ulink url="http://www.opentag.com/otspecs.htm";> 
 <emphasis>OpenTag Format Specifications</emphasis> 
 </ulink>. ILE (International Language Engineering), Nov 1998.</para>
<para id="refTMX">[TMX]</para>
<para> <ulink url="http://www.lisa.org/standards/tmx/";> 
 <emphasis>Translation Memory eXchange (TMX)</emphasis> 
 </ulink>. LISA (Localisation Industry Standards association).</para>
<para id="refSRX">[SRX]</para>
<para> <ulink url="http://www.lisa.org/standards/srx/";> 
 <emphasis>Segmentation Rules eXchange (SRX)</emphasis> 
 </ulink>. LISA (Localisation Industry Standards association).</para>
<para id="refUnicode">[Unicode]</para>
<para> <ulink url="http://www.unicode.org/";> <emphasis
>Unicode Consortium</emphasis> </ulink> Web site.</para>
<para id="refW3C">[W3C]</para>
<para> <ulink url="http://www.w3c.org/";> <emphasis
>World Wide Web Consortium</emphasis> </ulink> Web
site.</para>
</section>
</appendix>
<toc></toc>
</article>
<?nospell-end?>