<divGen>

<divGen> (automatically generated text division) indicates the location at which a textual division generated automatically by a text-processing application is to appear. [3.9.2 Index Entries]
Modul core — Elements Available in All TEI Documents
Attribute att.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source)) att.typed (type, @subtype)
type⚓︎ specifies what type of generated text division (e.g. index, table of contents, etc.) is to appear.
Abgeleitet aus att.typed
Zustand Optional
Datentyp teidata.enumerated
Beispielwerte sind etwa:
index
an index is to be generated and inserted at this point.
toc
a table of contents
figlist
a list of figures
tablist
a list of tables
Mitglied des
model.divGenLike model.frontPart
Enthalten in
textstructure: back body div div1 div2 div3 div4 div5 div6 front
Kann enthalten
core: head
Anmerkung

This element is intended primarily for use in document production or manipulation, rather than in the transcription of pre-existing materials; it makes it easier to specify the location of indices, tables of contents, etc., to be generated by text preparation or word processing software.
Beispiel

One use for this element is to allow document preparation software to generate an index and insert it in the appropriate place in the output. The example below assumes that the indexName attribute on index elements in the text has been used to specify index entries for the two generated indexes, named NAMES and THINGS:

<back>
 <div1 type="backmat">
  <head>Bibliography</head>
<!-- ... -->
 </div1>
 <div1 type="backmat">
  <head>Indices</head>
  <divGen n="Index Nominum" type="NAMES"/>
  <divGen n="Index Rerum" type="THINGS"/>
 </div1>
</back>
Beispiel

Another use for divGen is to specify the location of an automatically produced table of contents:

<front>
<!--<titlePage>...</titlePage>-->
 <divGen type="toc"/>
 <div>
  <head>Preface</head>
  <p> ... </p>
 </div>
</front>
Content model 
<content>
 <classRef key="model.headLike"
  minOccurs="0" maxOccurs="unbounded"/>
</content>
Schema Deklaration 
<rng:element name="divGen">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.rendition.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.global.responsibility.attributes"/>
 <rng:ref name="att.global.source.attributes"/>
 <rng:ref name="att.typed.attribute.subtype"/>
 <rng:optional>
  <rng:attribute name="type">
   <rng:ref name="teidata.enumerated"/>
  </rng:attribute>
 </rng:optional>
 <rng:zeroOrMore>
  <rng:ref name="model.headLike"/>
 </rng:zeroOrMore>
</rng:element>
element divGen
{
   att.global.attributes,
   att.global.rendition.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.global.responsibility.attributes,
   att.global.source.attributes,
   att.typed.attribute.subtype,
   attribute type { teidata.enumerated }?,
   model.headLike*
}