UTX 1.20 Minimal Specification
Table of Contents
0.

About this specificaion ................................................................................................. 1

1.

The structure of a UTX file ............................................................................................ 2

2.

Header ............................................................................................................................ 3

3.

Field definitions and body ............................................................................................ 3

Document information
Authors: AAMT Sharing/Standardization Working Group: YAMAMOTO Yuji (CosmosHouse),
AKIMOTO Kei (Kotobaya Inc.)
Website: http://www.aamt.info/english/utx/
Status: official release
Last updated: March 19, 2019
Document language: English
License: CC0 1.0
Disclaimer: See http://aamt.info/english/utx/index.htm#disclaimer.

0. About this specificaion
This specification explains the minimal information to create a UTX file. For more information, pleaserefer to the full specification.

- 1 -1. The structure of a UTX file
The following diagram illustrates the structure of a UTX glossary. For optional elements, refer to thefull specification.

UTX glossaryHeader
Glossary properties (mandatory + optional)

Glossary description (optional)
Field definitions(field name 1, field name 2, field name 3. . .)Body
Entry 1
Entry 2
Entry 3

1.1

Core UTX example

The following is an example of a complete UTX glossary with the minimum required information.
#UTX 1.20#term:enterm:jatest

テスト

1.2

File format details

File structure: tab-delimited text
File extension: ".utx"
Character encoding: UTF-8 with BOM.
New line code: "\r\n" (CR+LF). Blank lines are not allowed.
Line comment symbol: # (hash symbol).

- 2 -2. Header
2.1

UTX header structure

All lines in a UTX header begin with "#,” meaning that they are treated as commented-out lines.
A UTX header includes at least two mandatory lines, namely, glossary properties and fielddefinitions. The glossary properties can have two or more lines.
One or more lines can be added between the two mandatory lines for a description of the glossary.
The UTX version is the only mandatory glossary property. It indicates the UTX version of theglossary. It is specified with "UTX", a space, and the version number "1.20."

2.2

Field definitions

The last line of the UTX header (also begins with "#") includes a set of field (or column) definitions.

3. Field definitions and body
The body of a UTX glossary consists of entries in each line. Within a line, elements ("cells" in aspreadsheet) are separated by tab characters.

3.1

Language tags for fields

Use IETF's BCP 47 language tags to indicate languages in any part of a UTX glossary. These are
the same as the language tags used in HTML and XML, such as ja, fr, en-US, zh-CN, and zh-TW.
See <http://www.w3.org/International/articles/language-tags/Overview.en.php>.
Fields that are specific to a particular language are indicated by the respective language tag.
Language tags do not have a space after the colon.

3.2

term fields

The term field indicates a field of a term. The languages of these fields are indicated by language
tags. See the following table for examples.
Field nameSyntax/field item/field value

term

term:<language>

3.3

Exampleterm:enterm:ja

Other fields

The full UTX specification includes a complete list of other optional pre-defined fields.
Other than these pre-defined fields, any number of user-defined fields and their field items can be
added to a UTX glossary.
For a language-specific field, use a language tag to indicate the language.
SyntaxExampleUser-defined field:<language>

x-termUsage:en- 3 -