Transcription wherein the character would not be unambiguous outside its context

xml version || id: unclear|| traditional typographic representation | regular expression test | epidoc appearance with standard xslt | notes | usage | the reason attribute | alternative readings | tei p4 links | responsibility for this section | cvs information || post a comment

for divset 1: editionitemcount != typographicitemcount

Note: depending on your font, browser, browser settings, operating system and other factors, the subscript dots used in examples in this section may display after the character instead of beneath it.

Traditional typographic representation

Regular Expression Test

EpiDoc Encoding

  1. <unclear reason="undefined" cert="high">abc</unclear>
  2. <unclear reason="undefined" cert="high">a</unclear><unclear reason="undefined" cert="high">b</unclear><unclear reason="undefined" cert="high">c</unclear>
  3. <unclear reason="damage" cert="high">abc</unclear>
  4. <unclear reason="execution" cert="high">abc</unclear>
  5. <unclear reason="undefined" cert="high">abc</unclear>
  6. <app><rdg><unclear cert="high" reason="undefined">N</unclear></rdg><rdg n="default"><unclear cert="high" reason="undefined">M</unclear></rdg><rdg><unclear cert="high" reason="undefined">H</unclear></rdg></app>

EpiDoc appearance with standard XSLT

  1. ạḅc̣
  2. ạḅc̣
  3. ạḅc̣
  4. ạḅc̣

Notes

Usage

The EpiDoc DTD permits only the appearance of character data and the <mark/> element within <unclear></unclear>. When an editor or encoder encounters a continuous string of unclear characters in a text, two encoding options are available: each character may be encapsulated within its own <unclear></unclear> or the entire string may be encapsulated within a single <unclear></unclear>. No other markup may appear inside <unclear></unclear>, so if other aspects of a long string of unclear characters warrant additional tagging internal to the string, the per-character solution may be preferable or even required. For background on this issue, see a discussion on the markup list in July and August of 2005, subject: EpiDoc DTD issues [1: unclear].

The reason Attribute

TEI defines a reason attribute for the <unclear> element. In the EpiDoc DTD, this attribute has three possible values: "damage", "execution" and "undefined." "Undefined" is designated as the default/automatic value. See further the markup list discussion referenced above. The default stylesheets render all instances of <unclear> with the standard subscript dot, regardless of the value of the reason attribute.

Alternative readings

In cases where a letter trace is compatible with a range of characters but the context does not offer an unambiguous choice but the editor wishes to offer a default value, the alternative interpretations may be offered in a series of <rdg> elements within an <app>; in which case the particular reading to be rendered must be labelled with an attribute n='default' (see e.g. 6 above).

It is also envisaged that the possibility will exist to record the general shape of the surviving traces using embedded SVG or similar elements which could then be rendered as a drawing.

Where the editor is not willing to commit to a default reading, see vestiges.

Responsibility for this section

CVS Information

Revision number: $Revision: 1.9 $

Revision name (if any): $Name: r-4-beta-1 $

Revision date: $Date: 2006/04/18 21:19:01 $

Revision committed by: $Author: paregorios $