<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>TBX — Translate Toolkit 1.9.0 documentation</title>
<link rel="stylesheet" href="../_static/basic.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="../_static/bootstrap.css" type="text/css" />
<link rel="stylesheet" href="../_static/bootstrap-sphinx.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '1.9.0',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script type="text/javascript" src="../_static/bootstrap.js"></script>
<script type="text/javascript" src="../_static/bootstrap-sphinx.js"></script>
<link rel="top" title="Translate Toolkit 1.9.0 documentation" href="../index.html" />
<link rel="up" title="Translation Related File Formats" href="index.html" />
<link rel="next" title="Universal Terminology eXchange (UTX)" href="utx.html" />
<link rel="prev" title="Qt Phrase Book (.qph)" href="qt_phrase_book.html" />
</head>
<body>
<div id="navbar" class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container-fluid">
<a class="brand" href="../index.html">Translate Toolkit</a>
<span class="navbar-text pull-left"><b>1.9.0</b></span>
<ul class="nav">
<li class="divider-vertical"></li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Site <b class="caret"></b></a>
<ul class="dropdown-menu globaltoc"><ul class="simple">
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../features.html">Features</a></li>
<li class="toctree-l1"><a class="reference internal" href="../installation.html">Installation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html">Converters</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html#tools">Tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../commands/index.html#scripts">Scripts</a></li>
<li class="toctree-l1"><a class="reference internal" href="../guides/index.html">Use Cases</a></li>
<li class="toctree-l1"><a class="reference internal" href="index.html">Supported formats</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html">Translate Styleguide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../styleguide.html#documentation">Documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/building.html">Building</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/contributing.html">Contributing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../development/developers.html">Translate Toolkit Developers Guide</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../api/index.html">API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../changelog.html">Important Changes</a></li>
<li class="toctree-l1"><a class="reference internal" href="../history.html">History of the Translate Toolkit</a></li>
<li class="toctree-l1"><a class="reference internal" href="../license.html">License</a></li>
</ul>
</ul>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Page <b class="caret"></b></a>
<ul class="dropdown-menu localtoc"><ul>
<li><a class="reference internal" href="#">TBX</a><ul>
<li><a class="reference internal" href="#references">References</a></li>
<li><a class="reference internal" href="#standard-conformance">Standard conformance</a><ul>
<li><a class="reference internal" href="#done">Done</a></li>
<li><a class="reference internal" href="#todo">Todo</a></li>
</ul>
</li>
<li><a class="reference internal" href="#implementation-notes-for-missing-features">Implementation notes for missing features</a><ul>
<li><a class="reference internal" href="#synonyms">Synonyms</a></li>
<li><a class="reference internal" href="#definition">Definition</a></li>
<li><a class="reference internal" href="#context">Context</a></li>
<li><a class="reference internal" href="#parts-of-speech">Parts of speech</a></li>
<li><a class="reference internal" href="#cross-reference">Cross reference</a></li>
<li><a class="reference internal" href="#abbreviations">Abbreviations</a></li>
</ul>
</li>
<li><a class="reference internal" href="#tbx-cheat-sheet">TBX cheat sheet</a></li>
</ul>
</li>
<li><a class="reference internal" href="#tbx-requirements-by-galician-translation-team-proxecto-trasno">TBX requirements by Galician translation team (Proxecto Trasno)</a><ul>
<li><a class="reference internal" href="#features-priorization">Features priorization</a></li>
<li><a class="reference internal" href="#example-for-galician-tbx-requirements">Example for galician TBX requirements</a></li>
</ul>
</li>
</ul>
</ul>
</li>
<li><a href="qt_phrase_book.html"
title="previous chapter">« Qt Phrase Book (.qph)</a></li>
<li><a href="utx.html"
title="next chapter">Universal Terminology eXchange (UTX) »</a></li>
</ul>
<form class="navbar-search pull-right" action="../search.html" method="get">
<input type="text" name="q" placeholder="Search" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</ul>
</div>
</div>
</div>
</div>
<div class="container content">
<div class="section" id="tbx">
<span id="id1"></span><h1>TBX<a class="headerlink" href="#tbx" title="Permalink to this headline">¶</a></h1>
<p>TBX is the LISA standard for terminology and term exchange.</p>
<p>For information on more file formats, see <a class="reference internal" href="conformance.html"><em>Standards conformance</em></a>.</p>
<div class="section" id="references">
<span id="tbx-references"></span><h2>References<a class="headerlink" href="#references" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li><a class="reference external" href="http://www.lisa.org/Term-Base-eXchange.32.0.html">Standard home page</a></li>
<li><a class="reference external" href="http://www.lisa.org/TBX-Specification.33.0.html">Specification</a></li>
<li><a class="reference external" href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45797">ISO 30042</a>
– TBX is an approved ISO standard</li>
</ul>
<p>You might also be interested in reading about <a class="reference external" href="http://www.lisa.org/TBX-Basic.926.0.html">TBX-Basic</a> – a simpler, reduced version of
TBX with most of the useful features included.</p>
</div>
<div class="section" id="standard-conformance">
<span id="tbx-standard-conformance"></span><h2>Standard conformance<a class="headerlink" href="#standard-conformance" title="Permalink to this headline">¶</a></h2>
<div class="section" id="done">
<span id="tbx-done"></span><h3>Done<a class="headerlink" href="#done" title="Permalink to this headline">¶</a></h3>
<ul class="simple">
<li>Basic file creation</li>
<li>Creating a bilingual list from CSV with <a class="reference internal" href="../commands/csv2tbx.html"><em>csv2tbx</em></a></li>
<li>Using <tig> tags, not ntig</li>
</ul>
</div>
<div class="section" id="todo">
<span id="tbx-todo"></span><h3>Todo<a class="headerlink" href="#todo" title="Permalink to this headline">¶</a></h3>
<ul class="simple">
<li>id attributes for termEntry tags</li>
<li>ntig, read and write</li>
<li>multiple languages</li>
<li>synonyms</li>
<li>cross references</li>
<li>abbreviations</li>
<li>definitions</li>
<li>context</li>
<li>parts of speech</li>
</ul>
</div>
</div>
<div class="section" id="implementation-notes-for-missing-features">
<span id="tbx-implementation-notes-for-missing-features"></span><h2>Implementation notes for missing features<a class="headerlink" href="#implementation-notes-for-missing-features" title="Permalink to this headline">¶</a></h2>
<p>Note here:</p>
<ul class="simple">
<li>NLS – South African National Language Services – Multilingual Maths
Dictionary</li>
</ul>
<div class="section" id="synonyms">
<span id="tbx-synonyms"></span><h3>Synonyms<a class="headerlink" href="#synonyms" title="Permalink to this headline">¶</a></h3>
<p>NLS: Extra listing</p>
<p>TBX:</p>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"termNote"</span><span class="nt">></span>synonym<span class="nt"></termNote></span>
</pre></div>
</div>
<p>according to this TBX documentation. In another place:</p>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"termType"</span><span class="nt">></span>synonym<span class="nt"></termNote></span>
</pre></div>
</div>
<p>inside a <termGrp>, following <term></p>
</div>
<div class="section" id="definition">
<span id="tbx-definition"></span><h3>Definition<a class="headerlink" href="#definition" title="Permalink to this headline">¶</a></h3>
<p>NLS: term {definition/contextual information}</p>
<p>TBX:</p>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><descripGrp></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>The longish definition of the term<span class="nt"></descrip></span>
<span class="nt"></descripGrp></span>
</pre></div>
</div>
<p>inside langSet <descript> can probably be used directly under langSet</p>
</div>
<div class="section" id="context">
<span id="tbx-context"></span><h3>Context<a class="headerlink" href="#context" title="Permalink to this headline">¶</a></h3>
<p>NLS: term {definition/contextual information} (see above)</p>
<p>TBX:</p>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"context"</span><span class="nt">></span>A usually somewhat longer contextual sentence.<span class="nt"></descrip></span>
</pre></div>
</div>
<p>inside <ntig></p>
</div>
<div class="section" id="parts-of-speech">
<span id="tbx-parts-of-speech"></span><h3>Parts of speech<a class="headerlink" href="#parts-of-speech" title="Permalink to this headline">¶</a></h3>
<p>NLS: term v. (or adj, or n.)</p>
<p>TBX:</p>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"partOfSpeech"</span> <span class="nt">></span>noun<span class="nt"></termNote></span>
</pre></div>
</div>
<p>following <term></p>
</div>
<div class="section" id="cross-reference">
<span id="tbx-cross-reference"></span><h3>Cross reference<a class="headerlink" href="#cross-reference" title="Permalink to this headline">¶</a></h3>
<p>NLS: alternate term -> real lemma</p>
<p>TBX: <ref> TODO</p>
</div>
<div class="section" id="abbreviations">
<span id="tbx-abbreviations"></span><h3>Abbreviations<a class="headerlink" href="#abbreviations" title="Permalink to this headline">¶</a></h3>
<p>NLS: same as alternate term: a.m. -> before noon</p>
<p>TBX: TODO</p>
</div>
</div>
<div class="section" id="tbx-cheat-sheet">
<span id="tbx-tbx-cheat-sheet"></span><h2>TBX cheat sheet<a class="headerlink" href="#tbx-cheat-sheet" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>source word in English</li>
<li>definition in English</li>
<li>translation of source word to XX</li>
<li>definition in XX</li>
<li>comment</li>
<li>syntactic group</li>
<li>one or more tags</li>
<li>a reference number</li>
</ul>
<div class="highlight-xml"><div class="highlight"><pre><span class="nt"><termEntry</span> <span class="na">id=</span><span class="s">"4324 (8)"</span><span class="nt">></span>
<span class="nt"><note></span>tag1, tag2, tag3 (7) -
(Actually not clear what the best mapping to TBX is in this case.)<span class="nt"></note></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"en"</span><span class="nt">></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>sound (1)<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"partOfSpeech"</span><span class="nt">></span>noun (6)<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><descripGrp></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>Something you can hear (2) -
definition with an associated external source)<span class="nt"></descrip></span>
<span class="nt"><xref</span> <span class="na">type=</span><span class="s">"xSource"</span> <span class="na">target=</span><span class="s">"http://www.something.org/?id=234"</span><span class="nt">></span>Glossmaster<span class="nt"></xref></span>
<span class="nt"></descripGrp></span>
<span class="nt"><note></span>Any random note about the term. (5)
(Actually there are ways of storing pretty specific stuff in specific spaces,
but while it seems the comment could be a more verbose definition, examples,
usage notes or anything else, we'll use this generic way.)
<span class="nt"></note></span>
<span class="nt"></langSet></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"af"</span><span class="nt">></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>klank (3)<span class="nt"></term></span>
<span class="nt"></tig></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>Iets wat jy kan hoor (4) -
definition without an external source)<span class="nt"></descrip></span>
<span class="nt"><note></span>A note in the target language (5).<span class="nt"></note></span>
<span class="nt"></langSet></span>
<span class="nt"></termEntry></span>
</pre></div>
</div>
<p>Note that the <xref> tags are optional (as are just about everything except
termEntry, langSet and tig). They allow to link to an external source. An
internal source can also be specified, or the definition can be specified
without a source as shown for the term “klank”.</p>
</div>
</div>
<div class="section" id="tbx-requirements-by-galician-translation-team-proxecto-trasno">
<span id="tbx-tbx-requirements-by-galician-translation-team-proxecto-trasno"></span><h1>TBX requirements by Galician translation team (Proxecto Trasno)<a class="headerlink" href="#tbx-requirements-by-galician-translation-team-proxecto-trasno" title="Permalink to this headline">¶</a></h1>
<p>Here you have a list of <a class="reference external" href="http://www.certima.net/glosima/?28-xustificacion-das-escollas-de">TBX requirements</a> needed by
the <a class="reference external" href="http://www.trasno.net">Galician translation team (Proxecto Trasno)</a>. Its
translation to english is below. You can see a terminology management system
software specification draft in
<a class="reference external" href="http://translate.sourceforge.net/wiki/developers/terminology_management_system">http://translate.sourceforge.net/wiki/developers/terminology_management_system</a></p>
<p>A very important feature is to allow the exporting using pretty printing (like
in the first example below) since the exported glossaries should be able to be
read both by humans and software.</p>
<p>Before the example you can see a list priorizing the features from more
interesting and needed to less interesting and needed.</p>
<p>The chosen TBX tags are determined by the needs of our terminology management
system (the galician translation team one). That terminology management system
needs several glossaries, each glossary has several concepts, and each concept
can have several definitions (only one definition per language in a given
concept), and also can have several translations for each concept (several
translations per language in a given concept). The concepts will also have
associated some links to get more information (several links per language in a
given concept). Also is needed to have defined several languages.</p>
<p>Now we have a list of all the needed entities lets go with the list of
attributes for each of that entities:</p>
<p>Each glossary has a name and a description.</p>
<p>Each concept has an unique id, a subject field (which is another concept in the
same glossary), it can have several concepts that people may wish to see (lets
call it related concepts), and it can also have a parent concept (broader
concept).</p>
<p>Each link has a type (image, Wikipedia page,...), the address of the link, and
a tiny description.</p>
<p>Each definition has a definition text.</p>
<p>We want to save the ISO 639 code of each language.</p>
<p>Each translation can have a translation text, it has an unique id, the part of
speech, the grammatical genre (if applicable), the grammatical number (if
applicable), a field that indicates if the translation is an abbreviation or an
acronym, an explaining note, examples of use (created by the people that make
the terminology), links to examples of real use (a corpus or translation
database), a field that indicates if the translation is completed or if it is
still incomplete (completion status), and we also need to save the translation
administrative status (if it is a recommedend translation, a not recommended
one, or if it is a forbidden translation) and the reason why the translation
has the actual administrative status (a simple text string) that only applies
when the administrative status is other than “recommended”.</p>
<p>Once listed the needs we proceeded with reading the TBX ISO 300042 standard in
search of the elements that support these needs, and we found at least one tag
(or attribute) for every need, except for only a few that doesn’t have. We
should comment that TBX stores the information grouping it by concepts, and
within each concept part of the information is stored at the beginning of the
concept and other part of that information (the language-dependant information)
is splited between the different languages, and within every language section
it is splited another time between the translations of that language. This way
it has a three level structure: concept level, language level and translation
level (also called term level).</p>
<p>Next we list the needs and the tag chosen for that need, indicating the level
in which the tag goes:</p>
<ul class="simple">
<li><strong>Glossary name:</strong> if we match glossary with TBX file, then the glossary name
is the TBX file title, the label <title>. It goes on the file header.</li>
<li><strong>Glossary description:</strong> if we match glossary with TBX file then we can use
a <p> tag inside <sourceDesc> tag. It goes on the file header.</li>
<li><strong>Concept:</strong> the <termEntry> tag from TBX standard represents a concept. This
tag encloses the concept level.</li>
<li><strong>Concept identifier:</strong> the <termEntry> tag has an attribute named “id”.</li>
<li><strong>Concept subject field:</strong> the TBX standard defines the <descrip> tag with
“subjectField” in its “type” attribute to represent the concept subject field
(<strong>*<descrip type=”subjectField”>subject field name</descrip>*</strong>). Since
there is no way to refer to another concept we should use some of the
translations of the subject field concept (the concept that is the subject
field of the current concept) to put inside the subject field tag. It goes in
concept level. <strong>The lack of a way in TBX standard to refer to another
concept within the same glossary as subject field to make self-contained
glossaries is a real lack or we haven’t identified the way to do this using
TBX??</strong></li>
<li><strong>Related concepts:</strong> the TBX standard suggest the use of the tag <strong>*<ref
type=”crossReference” target=”cid23”>some text...</ref>*</strong> where “cid23” is
the value of the related concept id, and “some text...” is one of the related
concept translations (the first english recommended one, for example). It
goes on concept level.</li>
<li><strong>Broader concept:</strong> TBX defines the use of the tag <descrip> with the value
“broaderConceptGeneric” in its “type” attribute and a text between its
opening and closing tags. Also it allows the use of the “target” attribute to
refer to the broader concept. It goes on concept level. Example <strong>*<descrip
type=”broaderConceptGeneric” target=”cid23”>broader concept
name</descrip>*</strong></li>
<li><strong>Link:</strong> according to TBX standard the tag that defines external links to
outside the current file is the <xref> tag. This tag has the following
structure: <strong>*<xref type=”xGraphic” target=”sports/cricket/bat.jpg”>cricket
bat</xref>*</strong> where “type” is the link type, “target” is the link address and
the text between the opening and closing tags is a short description. It goes
on language level.</li>
<li><strong>Link type:</strong> the <xref> tag has an attribute named “type” that defines the
link type. This attribute can have the values “xGraphic” if it is an image,
“externalCrossReference” if it is a link to an external resource (for example
a link to Wikipedia). It can have other values, but for now they are
considered not important.</li>
<li><strong>Link address:</strong> the <xref> tag has an attribute named “target” which is the
link address.</li>
<li><strong>Link description:</strong> the link description can go between the opening and
closing tags</li>
<li><strong>Definition:</strong> to save the definitions it should be used the <descrip> tag
with the value “definition” in its “type” attribute. It goes on the language
level. Example: <strong>*<descrip type=”definition”>alternate name for a
person...</descrip>*</strong> can be the definition for “nickname”.</li>
<li><strong>Definition text:</strong> the definition text goes between the opening and closing
<descrip> tags.</li>
<li><strong>Language:</strong> in TBX the <langSet> tag represents a language, but no language
list is stored inside the TBX file. So if there is a <langSet> tag for a
given language somewhere inside the TBX file, then this particular language
is defined in that TBX file. Inside each concept only can exist one <langSet>
per language, but a given language can have a <langSet> in each <termEntry>.
It is essential that at least one <langSet> tag is present in every
<termEntry> tag. The <langSet> tag encloses the language level. It goes on
concept level.</li>
<li><strong>Language code:</strong> the <langSet> tag has an attribute named “xml:lang” which
stores some ISO 639 code value. Example: <strong>*<langSet xml:lang=”gl”>*</strong></li>
<li><strong>Translation:</strong> the TBX standard defines two different tags to enclose the
translation level: <tig> and <ntig>. The <tig> tag provides all the needed
functionalities, like also the <ntig> tag does, but the <ntig> also has a lot
of undesired and unnecessary functionalities that complicate the TBX file
structure in an unnecessary way making its size grow and making dificult to a
person read the file with a text editor. Besides the TBX-Basic standard only
uses the <tig> tag. So we decided to only use the <tig> tag.</li>
<li><strong>Translation text:</strong> the translation text goes between the opening and
closing of the <term> tag that goes on the translation level (under the <tig>
tag). Example: <strong>*<term>nickname</term>*</strong></li>
<li><strong>Translation identifier:</strong> the <tig> tag has an attribute named “id” in
which we put the identifier. Example: <strong>*<tig id=”tid59”>...</tig>*</strong></li>
<li><strong>Part of speech:</strong> for storing the part of speech TBX suggests the use of
the <termNote> tag indicating in the “type” attribute the value
“partOfSpeech”. The TBX standard doesn’t defines a part of speech values list
(like noun, verb...), but the TBX-Basic standard (a simplified subset of TBX)
defines a short list of part of speech values which we can reuse and that can
be completed if necessary. It goes on translation level. Example:
<strong>*<termNote type=”partOfSpeech”>noun</termNote>*</strong></li>
<li><strong>Grammatical gender:</strong> TBX specifies that the grammatical gender should be
specified using the <termNote> tag indicating the value “grammaticalGender”
in the “type” attribute. Like in the previous point, TBX doesn’t define a
gender list so we will have to use the defined in TBX-Basic. It goes on the
translation level. Example: <strong>*<termNote
type=”grammaticalGender”>masculine</termNote>*</strong></li>
<li><strong>Grammatical number:</strong> TBX says that for saving the grammatical number it
should be used a <termNote> tag with the value “grammaticalNumber” in its
“type” attribute. For the grammatical number we are going to use the list
defined in TBX-Basic. The grammatical should only be put when not putting it
could lead to misunderstanding. It goes on the translation level. Example:
<strong>*<termNote type=”grammaticalNumber”>plural</termNote>*</strong></li>
<li><strong>Acronym:</strong> to indicate that a translation is an acronym we can use the
<termNote> tag with the “termType” value on its attribute “type” and the text
“acronym” between its opening and closing tags. It goes on the translation
level. Example: <strong>*<termNote type=”termType”>acronym</termNote>*</strong></li>
<li><strong>Abbreviation:</strong> Like in the previous point but putting now “abbreviation”
between the opening and the closing tags. It goes on the translation level.</li>
<li><strong>Translation explaining note:</strong> for the notes TBX defines the use of the
<termNote> tag with the value “usageNote” on its “type” attribute with the
explanatory note text between its opening and closing tags. It goes on the
translation level. Example: <strong>*<termNote type=”usageNote”>Don’t abuse of that
translation...</termNote>*</strong></li>
<li><strong>Example of use:</strong> for the examples of use made ad hoc we are going to use
the <descrip> tag with the value “context” on its “type” attribute and the
example text between its opening and closing tags. It goes on the translation
level. We are not going to use <descrip type=”sampleSentence”> since it
doesn’t appear both in TBX and in TBX-Basic, and also we are not going to use
<descrip type=”example”> since in it is not mandatory to include the
translation text in the example. Example: <strong>*<descrip type=”context”>example
text</descrip>*</strong></li>
<li><strong>Link to real use example:</strong> it is used for references to corpus
(translations databases, like open-tran.eu). TBX says that such references
should be indicated using the <xref> tag with the value “corpusTrace” on its
“type” attribute. It goes on the translation level. Example: <strong>*<xref
type=”corpusTrace” target=”http:*en.gl.open-tran.eu/suggest/window”>Window on
open-tran.eu</xref></strong>//</li>
<li><strong>Completion status:</strong> we are going to use the <termNote> tag with the value
“processStatus” in its “type” attribute and the text “provisionallyProcessed”
between its opening and closing tags to indicate that not all the translation
information is not approved or that some of that information are not included
on the system yet. In case being completed this tag shouldn’t appear, despite
TBX defines the values “unprocessed” and “finalized”. It goes on the
translation level. Example: <strong>*<termNote
type=”processStatus”>provisionallyProcessed</termNote>*</strong></li>
<li><strong>Administrative status:</strong> to indicate the administrative status of the
translation we are going to do the way TBX specifies and not how TBX-Basic
does since we are using a superset of TBX-Basic. TBX specifies the use of the
<termNote> tag with the value “administrativeStatus” on its “type” attribute
and the text that indicates the status between its opening and closing tags.
TBX defines a list of several states but we are only going to use three of
them: “preferredTermadmnsts” to indicate that this is a recommended
translation, “admittedTermadmnsts” to indicate that it is a valid
translation but that be prefer not to use it since there is another one that
is recommended, and “deprecatedTermadmnsts” to indicate that this
translation is forbidden (for not being a valid translation for a given
language for some reasons: false friend,...). It goes on the translation
level. Example: <strong>*<termNote
type=”administrativeStatus”>preferredTermadmnsts</termNote>*</strong></li>
<li><strong>Administrative status reason:</strong> TBX doesn’t define any way to save the
reason why a translation has a given administrative status. Due to that we
decided to use the <note> tag for specifying the reason. Since this tag is
also used for saving notes we are considering to use the <termNoteGrp> to
group it together with the administrative status tag. Maybe some languages
are not going to use that, but in galician it is very very important. Note
that the reason is not specified if the administrative status is
“preferredTermadmnsts”. It goes on the translation level. Example:
<strong>galicism</strong></li>
</ul>
<p>Below you can see a diagram that shows the levels and the data that goes in
each level. Click on the image to enlarge.</p>
<img alt="../_images/tbx_levels_structure.png" src="../_images/tbx_levels_structure.png" />
<div class="section" id="features-priorization">
<span id="tbx-features-priorization"></span><h2>Features priorization<a class="headerlink" href="#features-priorization" title="Permalink to this headline">¶</a></h2>
<p>The upper ones are the most needed and interesting:</p>
<ul class="simple">
<li>Definition</li>
<li>Several translations in the same language for the same concept</li>
<li>Part of speech</li>
<li>Grammatical gender</li>
<li>Grammatical number</li>
<li>Concept subject field</li>
<li>Pretty printing</li>
<li>Use of tig tag by default</li>
<li>Link to external resources (including its type, address and description)</li>
<li>Completion status</li>
<li>Administrative status</li>
<li>Administrative status reason</li>
<li>Translation explaining note</li>
<li>Translation identifier</li>
<li>Related concepts</li>
<li>Broader concept</li>
<li>Acronym</li>
<li>Abbreviation</li>
<li>Example of use</li>
<li>Link to real use example</li>
</ul>
</div>
<div class="section" id="example-for-galician-tbx-requirements">
<span id="tbx-example-for-galician-tbx-requirements"></span><h2>Example for galician TBX requirements<a class="headerlink" href="#example-for-galician-tbx-requirements" title="Permalink to this headline">¶</a></h2>
<div class="highlight-xml"><div class="highlight"><pre><span class="cp"><?xml version='1.0' encoding='UTF-8'?></span>
<span class="cp"><!DOCTYPE martif SYSTEM 'TBXcoreStructV02.dtd'></span>
<span class="nt"><martif</span> <span class="na">type=</span><span class="s">'TBX'</span> <span class="na">xml:lang=</span><span class="s">'en'</span><span class="nt">></span>
<span class="nt"><martifHeader></span>
<span class="nt"><fileDesc></span>
<span class="nt"><titleStmt></span>
<span class="nt"><title></span>Localization glossary<span class="nt"></title></span>
<span class="nt"></titleStmt></span>
<span class="nt"><sourceDesc></span>
<span class="nt"><p></span>Test glossary with concepts from software localization...<span class="nt"></p></span>
<span class="nt"></sourceDesc></span>
<span class="nt"></fileDesc></span>
<span class="nt"><encodingDesc></span>
<span class="nt"><p</span> <span class="na">type=</span><span class="s">'XCSURI'</span><span class="nt">></span>http://www.lisa.org/fileadmin/standards/tbx/TBXXCSV02.xcs<span class="nt"></p></span>
<span class="nt"></encodingDesc></span>
<span class="nt"></martifHeader></span>
<span class="nt"><text></span>
<span class="nt"><body></span>
<span class="nt"><termEntry</span> <span class="na">id=</span><span class="s">"cid-23"</span><span class="nt">></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"subjectField"</span><span class="nt">></span>computer science<span class="nt"></descrip></span><span class="c"><!-- enclosed text in english since it is the glossary</span>
<span class="c"> language (see martif opening tag) --></span>
<span class="nt"><ref</span> <span class="na">type=</span><span class="s">"crossReference"</span> <span class="na">target=</span><span class="s">"cid-12"</span><span class="nt">></span>microprocessor<span class="nt"></ref></span><span class="c"><!-- enclosed text in english since it is the</span>
<span class="c"> glossary language (see martif opening tag) --></span>
<span class="nt"><ref</span> <span class="na">type=</span><span class="s">"crossReference"</span> <span class="na">target=</span><span class="s">"cid-16"</span><span class="nt">></span>keyboard<span class="nt"></ref></span><span class="c"><!-- enclosed text in english since it is the glossary</span>
<span class="c"> language (see martif opening tag) --></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"broaderConceptGeneric"</span> <span class="na">target=</span><span class="s">"cid-7"</span><span class="nt">></span>hardware<span class="nt"></descrip></span><span class="c"><!-- enclosed text in english since it is</span>
<span class="c"> the glossary language (see martif opening tag) --></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"en"</span><span class="nt">></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>A computer is a programmable machine that receives input, stores and manipulates
data, and provides output in a useful format.<span class="nt"></descrip></span>
<span class="nt"><xref</span> <span class="na">type=</span><span class="s">"xGraphic"</span> <span class="na">target=</span><span class="s">"http://en.wikipedia.org/wiki/File:HPLaptopzv6000series.jpg"</span><span class="nt">></span>computer image<span class="nt"></xref></span>
<span class="nt"><xref</span> <span class="na">type=</span><span class="s">"externalCrossReference"</span> <span class="na">target=</span><span class="s">"http://en.wikipedia.org/wiki/Computer"</span><span class="nt">></span>English Wikipedia computer page<span class="nt"></xref></span>
<span class="nt"><tig</span> <span class="na">id=</span><span class="s">"tid-59"</span><span class="nt">></span>
<span class="nt"><term></span>computer<span class="nt"></term></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>PC<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"termType"</span><span class="nt">></span>acronym<span class="nt"></termNote></span><span class="c"><!-- "PC" is an acronym of "Personal Computer" --></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>admittedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"usageNote"</span><span class="nt">></span>Do not abuse of using this translation.<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>comp.<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"termType"</span><span class="nt">></span>abbreviation<span class="nt"></termNote></span><span class="c"><!-- "comp." is an abbreviation of "computer" --></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>admittedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"></langSet></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"es"</span><span class="nt">></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>Máquina electrónica que recibe y procesa datos para convertirlos en información
útil<span class="nt"></descrip></span><span class="c"><!-- definition text in spanish --></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>sistema<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>admittedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>equipo<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>deprecatedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"processStatus"</span><span class="nt">></span>provisionallyProcessed<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>ordenador<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"partOfSpeech"</span><span class="nt">></span>noun<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"grammaticalGender"</span><span class="nt">></span>masculine<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"grammaticalNumber"</span><span class="nt">></span>singular<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>preferredTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"context"</span><span class="nt">></span>El ordenador personal ha supuesto la generalización de la informática.<span class="nt"></descrip></span><span class="c"><!-- example phrase --></span>
<span class="nt"><xref</span> <span class="na">type=</span><span class="s">"corpusTrace"</span> <span class="na">target=</span><span class="s">"http://es.en.open-tran.eu/suggest/ordenador"</span><span class="nt">></span>ordenador en open-tran.eu<span class="nt"></xref></span><span class="c"><!-- enclosed text in spanish --></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>computador<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>deprecatedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>computadora<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>deprecatedTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"></langSet></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"fr"</span><span class="nt">></span>
<span class="nt"><descripGrp></span><span class="c"><!-- Using descripGrp tags for enclosing the definition and its source --></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>Un ordinateur est une machine dotée d'une unité de traitement lui permettant
d'exécuter des programmes enregistrés. C'est un ensemble de circuits électroniques permettant de manipuler des données sous forme
binaire, ou bits. Cette machine permet de traiter automatiquement les données, ou informations, selon des séquences d'instructions
prédéfinies appelées aussi programmes.
Elle interagit avec l'environnement grâce à des périphériques comme le moniteur, le clavier, la souris,
l'imprimante, le modem, le lecteur de CD (liste non-exhaustive). Les ordinateurs peuvent être classés selon plusieurs critères
(domaine d'application, taille ou architecture).<span class="nt"></descrip></span>
<span class="nt"><xref</span> <span class="na">type=</span><span class="s">"xSource"</span> <span class="na">target=</span><span class="s">"http://fr.wikipedia.org/wiki/Ordinateur"</span><span class="nt">></span>Wikipedia: ordinateur<span class="nt"></xref></span>
<span class="nt"></descripGrp></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>ordinateur<span class="nt"></term></span>
<span class="nt"></tig></span>
<span class="nt"></langSet></span>
<span class="nt"></termEntry></span>
<span class="nt"><termEntry</span> <span class="na">id=</span><span class="s">"cid-27"</span><span class="nt">></span><span class="c"><!-- Another concept --></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"subjectField"</span><span class="nt">></span>computer science<span class="nt"></descrip></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"en"</span><span class="nt">></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>A technical standard is an established norm or requirement. It is usually a formal
document that establishes uniform engineering or technical criteria, methods, processes and practices. In contrast, a custom,
convention, company product, corporate standard, etc. which becomes generally accepted and dominant is often called a de facto standard.<span class="nt"></descrip></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>standard<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"partOfSpeech"</span><span class="nt">></span>noun<span class="nt"></termNote></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>preferredTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"></langSet></span>
<span class="nt"><langSet</span> <span class="na">xml:lang=</span><span class="s">"gl"</span><span class="nt">></span>
<span class="nt"><descrip</span> <span class="na">type=</span><span class="s">"definition"</span><span class="nt">></span>Norma que mediante documentos técnicos fixa a especificación de determinado tema.<span class="nt"></descrip></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>estándar<span class="nt"></term></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>preferredTerm-admn-sts<span class="nt"></termNote></span>
<span class="nt"></tig></span>
<span class="nt"><tig></span>
<span class="nt"><term></span>standard<span class="nt"></term></span>
<span class="nt"><termGrp></span><span class="c"><!-- Example of administrative status along with its reason --></span>
<span class="nt"><termNote</span> <span class="na">type=</span><span class="s">"administrativeStatus"</span><span class="nt">></span>deprecatedTermadmnsts<span class="nt"></termNote></span>
<span class="nt"><note></span>Razón: anglicismo<span class="nt"></note></span><span class="c"><!-- the translation of the enclosed text is: "Reason: anglicism" --></span>
<span class="nt"></termGrp></span>
<span class="nt"></tig></span>
<span class="nt"></langSet></span>
<span class="nt"></termEntry></span>
<span class="nt"></body></span>
<span class="nt"></text></span>
<span class="nt"></martif></span>
</pre></div>
</div>
</div>
</div>
</div>
<hr>
<footer class="footer">
<div class="container">
<p class="pull-right"><a href="#">Back to top ↑</a></p>
<ul class="unstyled muted">
<li><small>
© 2012, Translate.org.za.<br/>
</small></li>
<li><small>
Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
</small></li>
</ul>
</div>
</footer>
</body>
</html>
