TEI output
The exact output depends on the template: whether words are wrapped, whether line breaks are numbered automatically, and whether the MENOTA levels are enabled. This page shows the shapes of the common constructs.
The document
Section titled “The document”A template supplies everything before and after the transcription. A minimal document looks like this:
<?xml version="1.0" encoding="UTF-8"?><TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> … </teiHeader> <text> <body> …compiled transcription… </body> </text></TEI>The MENOTA template adds the me namespace, the MENOTA doctype and entity declarations,
and wraps pages in paragraphs.
Breaks and paragraphs
Section titled “Breaks and paragraphs”<pb n="1r"/><lb n="1"/><p> …</p>With the Menota template, a page break opens a new <p>, and .p closes the current
paragraph and opens another. The plain TEI P5 template writes the breaks without adding
paragraph wrappers.
A bare // becomes <lb/> or <lb n="…"/> depending on the Auto line numbers option.
Single-level, with word wrapping:
<w>maðr</w><w>konungs</w>Punctuation is a <pc> element:
<pc>.</pc><pc>,</pc>Multi-level (MENOTA):
<w> <choice> <me:facs>&rrot;egn</me:facs> <me:dipl>regn</me:dipl> <me:norm>regn</me:norm> </choice></w>Lemmas and analyses
Section titled “Lemmas and analyses”A confirmed lemma and morphological analysis are attributes on the word:
<w lemma="kona" me:msa="xNC cN nP gF"> …</w>In an imported file, Saga-Scribe uses the attribute name the file already uses —
me:msa on MENOTA files, msa on plain TEI. Words loaded from the file that are not
edited keep their attributes exactly as they were.
Abbreviations
Section titled “Abbreviations”<w><choice><abbr>kgs</abbr><expan>konungs</expan></choice></w>On a multi-level document, the abbreviation form appears on the facsimile level and the expansion on the other two:
<w> <choice> <me:facs><abbr>kgs</abbr></me:facs> <me:dipl><expan>konungs</expan></me:dipl> <me:norm><expan>konungs</expan></me:norm> </choice></w>Gaps and editorial marks
Section titled “Gaps and editorial marks”<gap reason="illegible" quantity="3" unit="chars"/><supplied>ok</supplied><supplied>abc</supplied><del>hans</del><add>sona</add><unclear>Haralds</unclear><note>…</note>In multi-level output, a gap appears on the facsimile level; supplied text appears on the
diplomatic and normalized levels. <del>, <add>, <unclear> and <note> are carried
through where they make sense for the level.
Annotations
Section titled “Annotations”Semantic and paleographic annotations are written into the ana attribute:
<w ana="#person:name #paleo:unclear">…</w>ana values are pointers (#), with a category and optional subcategory for semantic
annotations, and a paleo: type for paleographic ones. A certainty, where recorded, is
written as cert with the value high, medium or low.
Text notes are written as a <note> attached to the word:
<w>…<note type="category">The scribe corrects himself here.</note></w>Imported files: notes and annotations stay in the project, because adding them would change markup the file does not have. See Importing existing files.
Round-trip behaviour
Section titled “Round-trip behaviour”For an imported file, the compiled XML is not a wholesale serialization of the document. The importer records the source span of every tag, and the patcher splices edits into the original bytes. The result is that unedited content is byte-identical, and only what you edited is rewritten.
