the value consists of a single token which may however
contain punctuation
characters, whitespace or word
separating characters. It need not be restricted to
numbers.
Note
The n attribute may be used to specify the numbering of chapters, sections,
list items, etc.; it may also be used in the specification of a standard reference system
for the text.
xml:lang
(language) indicates the language of the element content using a ‘tag’ generated
according to BCP 47
The value must conform to BCP 47. If the value is a
private use code (i.e., starts with x- or contains
-x-), a language element with a matching value for
its ident attribute should be supplied in the TEI
Header to document this value. Such documentation may also
optionally be supplied for non-private-use codes, though these
must remain consistent with their Unicode definitions.
<p> … The consequences of this rapid depopulation were the loss of the last <foreign xml:lang="rap">ariki</foreign> or chief (Routledge 1920:205,210) and their connections to ancestral territorial organization.</p>
Note
the xml:lang value will be inherited from the immediately
enclosing element, or from its parent, and so on up the document hierarchy.
It is generally good practice to specify xml:lang at the highest
appropriate level, noticing that a different default may be needed for the
teiHeader from that needed for the associated resource element or elements,
and that a single TEI document may contain texts in many languages.
rend
(rendition) indicates how the element in question was rendered or presented in the source text.
may contain any number of tokens, each of which may
contain letters, punctuation marks, or symbols, but not
word-separating characters.
<head rend="align(center) case(allcaps)"> <lb/>To The <lb/>Duchesse <lb/>of <lb/>Newcastle, <lb/>On Her <lb/> <hi rend="case(mixed)">New Blazing-World</hi>. </head>
Note
These Guidelines make no binding recommendations for the values of the rend
attribute; the characteristics of visual presentation vary too much from text to text and
the decision to record or ignore individual characteristics varies too much from project
to project. Some potentially useful conventions are noted from time to time at appropriate
points in the Guidelines.
rendition
points to a description of the rendering or presentation used for this element in the
source text.
The rendition attribute is used in a very similar way to the class
attribute defined for XHTML but with the important distinction that its function is to
describe the appearance of the source text, not necessarily to determine how that text
should be presented on screen or paper.
Where both rendition and rend are supplied, the latter is
understood to override or complement the former.
Each URI provided should indicate a rendition element defining the intended
rendition in terms of some appropriate style language, as indicated by the
scheme attribute.
xml:base
provides a base URI reference with which applications can resolve relative URI
references into absolute URI references.
