TermBase eXchange 形式

Added in version 4.5.

バージョン 5.12 で変更.

TBX は、用語データを交換するための XML 形式です。

対応機能

File extensions

.tbx

Linguality

Bilingual

Supports plural

No

Supports descriptions

Yes

Supports explanation

Yes

Supports context

Yes

Supports location

No

Supports flags

Yes

API identifier

tbx

Supports read-only strings

No

Supports removing obsolete strings

No

Term alternatives

Each TBX concept is one string with independent lists of source and target alternatives. Weblate reads every direct <tig> in the selected languages; IDs are optional and do not pair alternatives across languages. All source alternatives can match in the glossary, and each permitted target can be copied separately. Term statuses and notes are displayed with their alternatives.

See Multivalue formats for how alternatives are handled by quality checks, automatic fixes, and machine translation.

When editing alternatives, unchanged text is matched first, including duplicate occurrences. Remaining alternatives reuse unmatched terms in their original order, retaining IDs and metadata. Renaming and deleting alternatives together can therefore associate a renamed term with the first unmatched term's metadata. New alternatives are created without IDs. Term metadata is read-only in Weblate.

A missing target language does not remove a concept whose source exists. DNT terms can use the matching source alternative without creating a translation. Language codes still need to match the component configuration.

解説

Weblate は 用語集 で表示するために TBX ファイルから解説を読み込んで保存します。

  • 翻訳の解説は <note from="translator"></note> タグとして保存されます。

  • 原文の解説は <descrip></descrip> タグとして保存されます。

  • 原文の解説は <descrip type="Usage note"></descrip> タグとして保存されます。

Concept notes are shared. Language notes are read only for the selected language, and term notes belong to their own alternative. Editing a target explanation does not overwrite notes in other languages.

TBX components offer native and generated TBX downloads. Conversion to formats that use grammatical plurals is unavailable because those formats cannot preserve independent source and target alternatives.

Generated TBX downloads preserve represented flags, explanations, alternative IDs, statuses, and note scopes. Weblate flags use the same weblate-flags attribute as native TBX storage. Native file editing also preserves unrecognized XML and unselected languages; generated exports contain the selected language pair.

Glossary flags and read-only metadata

Weblate imports terms with forbidden or obsolete administrative status in <termNote type="administrativeStatus"> as 使用を禁止する訳語.

<descrip type="Translation needed">No</descrip> が含まれている用語には、読み取り専用フラグ(翻訳禁止の用語)が付与されます。

Importing glossary files

TBX can store multiple languages in one XML file, but Weblate still maps each component file to a translation language using the component file mask. For a TBX glossary component, the component source language is used for source terms and the language parsed from the file name is used as the target glossary language.

Avoid naming a TBX translation file with the same language code as the component source language, because the source language already exists in Weblate and the file can be detected as a duplicate language.

The Add upload method preserves alternative IDs, statuses, and scoped notes when importing TBX into a TBX glossary.

ファイルの例

ファイルの例:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE martif PUBLIC "ISO 12200:1999A//DTD MARTIF core (DXFcdV04)//EN" "TBXcdv04.dtd">
<martif type="TBX" xml:lang="en">
    <martifHeader>
        <fileDesc>
            <sourceDesc>
                <p>Translate Toolkit</p>
            </sourceDesc>
        </fileDesc>
    </martifHeader>
    <text>
        <body>
            <termEntry>
                <langSet xml:lang="en">
                  <tig>
                    <term>address bar</term>
                  </tig>
                </langSet>
                <langSet xml:lang="cs">
                  <tig>
                    <term>adresní řádek</term>
                  </tig>
                </langSet>
            </termEntry>
            <termEntry weblate-flags="terminology">
                <langSet xml:lang="en">
                  <tig>
                    <term>administrator</term>
                  </tig>
                </langSet>
                <langSet xml:lang="cs">
                  <tig>
                    <term>správce</term>
                  </tig>
                </langSet>
            </termEntry>
            <termEntry>
                <descrip>Example source string explanation text</descrip>
                <descrip type="Usage note">Example source string description text</descrip>
                <langSet xml:lang="en">
                  <tig>
                    <term>administrate</term>
                  </tig>
                </langSet>
                <langSet xml:lang="cs">
                  <tig>
                    <term>spravovat</term>
                    <note from="translator">Example translation string explanation text</note>
                  </tig>
                </langSet>
            </termEntry>
            <termEntry>
                <descrip type="Translation needed">No</descrip> <!-- mark as untranslateable -->
                <langSet xml:lang="en">
                  <tig>
                    <term>Weblate</term>
                  </tig>
                </langSet>
            </termEntry>
            <termEntry>
                <langSet xml:lang="en">
                  <tig>
                    <term>example forbidden term</term>
                    <termNote type="administrativeStatus">forbidden</termNote>
                  </tig>
                </langSet>
                <langSet xml:lang="cs">
                  <tig>
                    <term>příklad zakázaného výrazu</term>
                  </tig>
                </langSet>
            </termEntry>
        </body>
    </text>
</martif>

Weblate の設定

典型的な Weblate コンポーネント構成

ファイル マスク

tbx/*.tbx

モノリンガル用の、基礎となる言語ファイル

Empty(空)

新しい翻訳のテンプレート

Empty(空)

ファイル形式

TermBase eXchange ファイル