10.1.69. <language>

<language> (language) characterizes a single language or sublanguage used within a text. [2.4.2. Language Usage]

Module header — Specification

Attributes

att.typed
- @type
- @subtype

role

Status

Required

Legal values are:

objectLanguage: Object language is the "language being described." (ISO 16642:2017)
workingLanguage: Working language is the "language used to describe objects." (ISO 16642:2017)
sourceLanguage: Source language is the language of the content to be translated. (ISO 17100:215)
targetLanguage: Target language is the language of the content into which source language content is translated. (ISO 17100:215)

status

Status

Optional

ident

(identifier) Supplies a language code constructed as defined in BCP 47 which is used to identify the language documented by this element, and which may be referenced by the global xml:lang attribute.

Status	Required
Datatype	teidata.language

usage

specifies the approximate percentage of the text which uses this language.

Status	Optional
Datatype	nonNegativeInteger

Contained by

header: langUsage

May contain

core: bibl date desc listBibl name note

corpus: channel domain interaction purpose settingDesc

namesdates: person personGrp

tagdocs: ident

character data

Note

In a monolingual dictionary, where the object language and the working language are the same, one should list each as a separate <language> element with a specific role attribute. A human-readable, informal prose characterization should be supplied in the child <name> element.

Example

When the human-readable name(s) of languages are provided in multiple languages, the attribute xml:lang should be used on <language>

<langUsage>
 <language ident="ru-x-lit19c" role="objectLanguage">
  <name xml:lang="ru">Русский литературный язык XIX века</name>
  <name xml:lang="en">19th-century literary Russian</name>
 </language>
 <language ident="ru" role="workingLanguage">
  <name xml:lang="ru">Современный русский язык</name>
  <name xml:lang="en">Modern Russian</name>
 </language>
</langUsage>

Example

Bilingual or multilingual dictionaries could be documented as having two or more object languages. In those cases, however, it is recommended -- and more precise -- to describe each object language as either a source language or a target language.

<langUsage>
 <language ident="chu" role="sourceLanguage">
  <name>Old Church
     Slavic</name>
 </language>
 <language ident="la" role="targetLanguage">
  <name>Latin</name>
 </language>
 <language ident="grc" role="targetLanguage">
  <name>(Premodern)
     Greek</name>
 </language>
</langUsage>

Example

The ident attribute is required and is used to indicate the language code used for the given lanuguage variety in the rest of the dictionary. If multiple language identifiers exist for the given language variety, they should be encoded using the <ident> element.

<langUsage>
 <language status="active" role="sourceLanguage" ident="fr" type="individual" subtype="living">
  <ident type="languageIdentifier" subtype="ISO639-3B">fre</ident>
  <ident type="languageIdentifier" subtype="ISO639-3T">fra</ident>
  <ident type="languageIdentifier" subtype="ISO639-2">fr</ident>
  <name type="languageName" role="languageReferenceName" xml:lang="en">French</name>
  <name type="languageName" xml:lang="fr">Français</name>
 </language>
</langUsage>

Content model

<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">
  <textNode/>
  <macroRef key="model.languageProfile"/>
 </alternate>
</content>
    ⚓

Schema Declaration


element language
{
   att.typed.attributes,
   attribute role
   {
      "objectLanguage"
    | "workingLanguage"
    | "sourceLanguage"
    | "targetLanguage"
   },
   attribute status { text }?,
   attribute ident { text },
   attribute usage { text }?,
   ( text | model.languageProfile )*
}⚓

TEI Lex-0

10.1.69. <language>

TEI LEX-0