2. Transcription Guidelines: Leidenisation
In this page is displayed a set of rules designed for SigiDoc in order to establish a scholarly edition of the seals' legend: the following thematic list contains all the mark-up necessary to visualise the Leiden symbols used in representing the editorial interventions on the legend's transcription (e.g. ( ), [ ], < >, ..., etc.). Among the different sets of conventions available through the EpiDoc stylesheet, SigiDoc is loosely based on those designed by Hans Krummrey and Silvio Panciera, with variations intended to make some of them more suitable for (Byzantine) sigillographic routines.
2.1.1. Lines
- Editorial interpretation: 1 [1st line]
- Diplomatic edition: 1 [1st line]
The numbers of legend’s lines should be continuous between obverse and reverse, thus including also the invocation (if applicable) and excluding an image's label or a sigla, often rendered in columns (see).
<lb n="1"/>[text]
<lb n="2"/>[text] If the text of a line is engraved following the direction right to left, a rend attribute could be added to lb:
<lb n="2" rend="right-to-left"/>[text]
This will print an arrow (←) at the end of the line (with a rend’s value “left-to-right” an arrow in the opposite direction will be printed):
2 [text] ←
Crosses and decoration engraved on separate lines from the legend should not be part of the editorial transcription, while there are part of the diplomatic edition, where the tag should be:
<lb n="0"/>[decoration]
2.1.2. Columns
- Editorial interpretation: ᵃ[1st col] – ᵇ[2nd col]
- Diplomatic edition: ᵃ[1st col] – ᵇ[2nd col]
Should be used for labels and sigla. Note: the n's value is here alphabetical, in order to differentiate the cb from the lb in apparatus and commentary:
<cb n="a"/>[text]
<cb n="b"/>[text]
The transformation will separate with a – the content of each column, and to each column will be assigned the letter (printed in superscript) used as n’s attribute (the stylesheet can handle a max of 4 columns [a,b,c,d]):
ᵃ(Ὁ ἅγιος) Νι – ᵇκόλ(αος)
2.1.3. Words divided across line
- Editorial interpretation: 1 αβγ- 2 δεζ
- Diplomatic edition: 1 ΑΒΓ 2 ΔΕΖ (none)
Note that the attribute break is in the second line, not in the line where the hyphen (–) will appear after transformation:
<lb n="1"/>αβγ
<lb n="2" break="no"/>δεζ
The hyphen (–) for the line break is not supposed to appear in the
diplomatic transcription, consequently the attribute
@break is not necessary there.
2.1.4. Verse lines (metrical legends)
- Editorial interpretation: none
- Diplomatic edition: none
<lg type="metrical" met="" subtype="true/false">
<l>
<lb n="1"/>[text]
<lb n="2"/>[text]
</l>
</lg>
<lg> = a group of verse lines; must always
contain a child <l>.
Each <l> = one metrical sequence, a single line
of verse (ex. 12 syllables), different from the physical/typographical
line tagged with <lb>. Note that within the
verse line (<l>) the beginning of each line of
text on the support still needs to be marked with an
<lb>.
In @met attribute standard terms can be used
in order to define the metre: dodecasyllabic, iambic trimeter, political
verse/decapentasyllabic verse, pseudo-pentameter, hexameter, ...; or a
representation for the metrical pattern can be used.
If the metrical legend is spanned over the two faces of the seal,
<lg> should be duplicated on the 2 faces
(because they are encoded in two separate
<div>s) for a proper tagging.
A @real attribute (for ‘realisation’)
could be used with <l> to indicate
any deviation from the pattern defined by the
@met attribute which the encoder wishes to
record: it could be used for a different kind of meter or for an
incomplete metre.
A @subtype attribute could be used with
<lg>: the value should be ‘true’ if the same
metre is respected in all the legend; if not, ‘false’.
Notice that <lg> replaces the element
<ab> in <div @type="textpart"> in a seal's edition, that
is, <lg> should not be nested inside
<ab>.
2.2.1. Clear text
- Editorial interpretation: αβγ (none)
- Diplomatic edition: ΑΒΓ (none)
No tags.
2.2.2. Uninterpreted characters: clear but incomprehensible letters
- Editorial interpretation: ΑΒΓ
- Diplomatic edition: ΑΒΓ (none)
<orig>αβγ</orig>
The letters are shown in the edition as capital letters.
This tag is for the editorial interpretation only.
2.2.3. Ambiguous / damaged characters
- Editorial interpretation: none
- Diplomatic edition: none
<unclear>α</unclear>βγ = ̣αβγ
<damage>α</damage>βγ = αβγ
Stretches of ambiguous text that span words, lines, names, dates, or
other tagged features, should be marked with multiple
unclear elements.
Sigillographic habits do not include the underdot in the editorial
interpretation, but only in the diplomatic edition, for which, however,
Athena Ruby’s underdot should be used; hence,
unclear and damage are not really necessary.
For lost characters, see gap.
2.2.4. Lost lines: quantity known
- Editorial interpretation: [ - - - - - - - - - - ]
- Diplomatic edition: none
<gap reason="lost" quantity="1" unit="line"/>
When the loss is complete.
Note: the @quantity's value does not affect
the visualisation; for this reason, this tag should be repeated for each
lost line, after lb, with a fixed
@quantity’s value of “1”.
2.2.5. Lost lines: quantity unknown
- Editorial interpretation: [- - -?- - -]
- Diplomatic edition: none
<gap reason="lost" extent="unknown" unit="line"/>
2.2.6. Lost lines: approximate quantity
- Editorial interpretation: [- - -c. 2- - -]
- Diplomatic edition: none
<gap reason="lost" quantity="2" unit="line" precision="low"/>
2.2.7. Lost lines: approximate extent
- Editorial interpretation: [- - -c. 3 - 5- - -]
- Diplomatic edition: none
<gap reason="lost" atLeast="3" atMost="5" unit="line"/>
2.2.8. Illegible lines: quantity known
- Editorial interpretation: [- - -c. 3 - 5- - -]
- Diplomatic edition: none
<gap reason="lost" atLeast="3" atMost="5" unit="line"/>
2.2.9. Illegible lines: quantity unknown
- Editorial interpretation: - - -?- - -
- Diplomatic edition: none
<gap reason="illegible" extent="unknown" unit="line"/>
2.2.10. Illegible lines: approximate quantity
- Editorial interpretation: - - - c. 2- - -
- Diplomatic edition: none
<gap reason="illegible" quantity="2" unit="line" precision="low"/>
2.2.11. Illegible lines: approximate extent
- Editorial interpretation: - - -c. 3 - 5- - -
- Diplomatic edition: none
<gap reason="illegible" atLeast="3" atMost="5" unit="line"/>
2.2.12. Lost characters: quantity known
- Editorial interpretation: [..]
- Diplomatic edition: none
<gap reason="lost" quantity="2" unit="character"/>
When the loss is complete. The number of dots should represent the extent of the loss.
The maximun number of dots visualised after transformation is 25, representing a lacuna of 25 characters on a single line; if more dots were needed, the relevant EpiDoc stylesheet should be modified (this stylesheet in EFES lives in ROOT>kiln>stylesheets>epidoc>teigap.xsl, line 40; note that EFES must be restarted), otherwise, over 25 the visualisation will change to [c. 26], [c. 27], etc.
2.2.13. Lost characters: quantity unknown
- Editorial interpretation: [...?...]
- Diplomatic edition: none
<gap reason="lost" extent="unknown" unit="character"/>
2.2.14. Lost characters: approximate quantity
- Editorial interpretation: [c. 3]
- Diplomatic edition: none
<gap reason="lost" quantity="3" unit="character" precision="low"/>
2.2.15. Lost characters: approximate extent
- Editorial interpretation: [c. 1 - 3]
- Diplomatic edition: none
<gap reason="lost" atLeast="1" atMost="3" unit="character"/>
2.2.16. Lost characters: numerals
- Editorial interpretation: L[.]
- Diplomatic edition: none
<num atLeast="51" atMost="55">L<gap reason="lost" quantity="1" unit="character"/></num>
gap is nested inside
num; in @atLeast
and @atMost the lowest and the highest number
possible according to what remains, and the quantity of lost characters
in @quantity (it is also possible to replace
@quantity with
@atLeast/@atMost
or @extent).
2.2.17. Illegible characters: quantity known
- Editorial interpretation: ..
- Diplomatic edition: none
<gap reason="illegible" quantity="2" unit="character"/>
Vestiges of letters visible but illegible.
The maximun number of dots visualised after transformation is 25, representing a series of 25 characters on a single line; if more dots were needed, the relevant EpiDoc stylesheet should be modified (this stylesheet in EFES lives in ROOT>kiln>stylesheets>epidoc>teigap.xsl, line 40; note that EFES must be restarted), otherwise, over 25 the visualisation will change to c. 26, c. 27, etc.
2.2.18. Illegible characters: quantity unknownn
- Editorial interpretation: ...?...
- Diplomatic edition: none
<gap reason="illegible" extent="unknown" unit="character"/>
2.2.19. Illegible characters: approximate quantity
- Editorial interpretation: c. 3
- Diplomatic edition: none
<gap reason="illegible" quantity="3" unit="character" precision="low"/> 2.2.20. Illegible characters: approximate extent
- Editorial interpretation: c. 4 - 6
- Diplomatic edition: none
<gap reason="illegible" atLeast="4" atMost="6" unit="character"/>
2.3.1. Supralinear lines, underlining
- Editorial interpretation: solved abbreviation, number
- Diplomatic edition: a̅c̅e̅, a̲c̲e̲
<hi rend="supraline">ace</hi>
<hi rend="underline">ace</hi> Characters written with a supralinear line above, with solid line beneath, scored.
This is separate from any tagging of what that decoration might represent in the text, e.g. abbreviations or numerals. If that means numerals or abbreviations, these tags are for the diplomatic edition only (they could be useful when AthenaRuby has problems in creating supralines for abbreviations); in the editorial interpretation the abbreviation is solved (with appropriate tag), or there is the appropriate number.
2.3.2. Raised or lowered characters
- Editorial interpretation: (none)
- Diplomatic edition: none
Characters written higher than the surrounding text:
<hi rend="superscript">γ</hi> = αβᵞ
Characters written lower than the surrounding text:
<hi rend="subscript">γ</hi> = αβᵧ
Character written directly above another character (as opposed to superscript):
<hi rend="stacked">c</hi>
but it is not currently handled by stylesheets.
If it is for an abbreviation or something supposed to be ‘regularised’ in the edition, those characters should appear above or below line only in the diplomatic edition, especially using Athena Ruby; but sometimes they are simply written like this, and should be represented in the editorial interpretation too.
2.3.3. Ligatured letters
- Editorial interpretation: none
- Diplomatic edition: none (a͡b)
<hi rend="ligature">ab</hi> = a͡b Ligatures are not visualised as such in the editorial interpretation and are handled by Athena Ruby in the diplomatic edition: however, this could be useful if a ligature was lacking in Athena Ruby’s palette.
It should be noticed that this chapter concerns simple ligatures of consecutive letters, such as ΣΤ in θεοσεβεστάτοις (Tatış 6.7); for ligatures which also need to be expanded, see 2.4.14. Expansion of symbol or ligature.
2.3.4. Symbols, not meaning-bearing (cross, leaf, scroll, fleurette, etc.)
- Editorial interpretation: +, ((cross)), ((+))
- Diplomatic edition: none
Not meaning-bearing symbols, i.e. not to be expanded.
These symbols should be simply added by typing those supposed to appear in the editorial interpretation; for the diplomatic edition, Athena Ruby should be used.
Alternatively, if Athena Ruby was not used or if a project plans to have a more detailed encoding of symbols, a slightly more elaborated tagging would be required, such as the following, in the editorial interpretation:
<g ref="#cross">+</g>
The attribute @ref in <g> points to a list of glyphs in the <charDecl> element, such as the following:
<charDecl>
<glyph xml:id="cross">
<mapping type="standard">+</mapping>
<mapping type="simplified">(cross)</mapping>
</glyph>
</charDecl>
This solution is not currently supported by the SigiDoc instance of EFES: a project which would decide to adopt it should also take care of adapting in the relevant stylesheet the final visualisation of the symbols listed in the <charDecl> element.
2.4.1. Characters lost but restored
- Editorial interpretation: [αβ]
- Diplomatic edition: none
<supplied reason="lost">αβ</supplied> Different cases:
1) gap+supplied -
If inside the restoration there is also a lacuna,
gap preceeds or follows
>supplied:
<gap reason="lost" quantity="2" unit="character"/><supplied reason="lost">abg</supplied> = [..abg]
<supplied reason="lost">abg</supplied><gap reason="lost" quantity="2" unit="character"/> = [abg..]
<gap reason="lost" unit="character"/><supplied reason="lost">abg</supplied> = [.. ? ..abg] Note: adding @quantity,
@extent and @unit
to gap, or changing the
@reason's value in 'illegible' will change
the transformation according to the visualisation designed for those
attributes/values.
2)
expan+supplied -
If the supplied text includes an expansion of abbreviation,
expan is nested inside
supplied:
<supplied reason="lost">
<expan><abbr>a</abbr><ex>bg</ex></expan>
</supplied> = [a(bg)] Otherwise, if an expansion of abbreviation includes a supplied text,
supplied is nested inside
expan:
<expan>
<abbr>Au</abbr>
<supplied reason="lost">
<abbr>g</abbr>
<ex>usti</ex>
</supplied>
</expan>
<supplied reason="lost">Lici</supplied>nia = Au[g(usti) Lici]nia 3)
supplied+supplied -
Adjacent lacunae, i.e. two or more words in the same restoration:
supplied should be repeated for each word or
part; note that the stylesheet will join together more consecutive
restorations:
Καῖσ<supplied reason="lost">αρ</supplied>
<supplied reason="lost">Σεβαστὸς</supplied> = Καῖσ[αρ Σεβαστὸς] Note: a white space between these 2 elements should be added in order to separate the two parts inside the square brackets.
2.4.2. Characters lost and restored tentatively
- Editorial interpretation: [αβ(?)]
- Diplomatic edition: none
<supplied reason="lost" cert="low">αβ</supplied> 2.4.3. Word incompletely restored
- Editorial interpretation: [sta-·· ? ··]
- Diplomatic edition: none
<w part="I">
<supplied reason="lost">sta</supplied>
</w>
<gap reason="lost"/> In w the attribute
@part explains which part of the word has
been restored, and, as a consequence, which part is missing. Its values
are:
"I" - the initial part of a word (i.e. the end is missing)
"M" - the middle part of a word (i.e. the beginning and end are both missing)
"F" - the final part of a word (i.e. the beginning is missing)
2.4.4. Text visible to previous editor, but now lost
- Editorial interpretation: αβγ
- Diplomatic edition: none
<supplied reason="undefined" evidence="previouseditor">αβγ</supplied> or @reason="lost"
The value ‘undefined’ is generic and does not give any detail about the current state of the text.
2.4.5. Text restored by comparison with parallel seal
- Editorial interpretation: αβγ
- Diplomatic edition: none
<supplied reason="undefined" evidence="parallel">αβγ</supplied> or @reason="lost"
The value ‘undefined’ is generic and does not give any detail about the current state of the text.
2.4.6. Text restored by comparison with similar but not parallel seal
- Editorial interpretation: αβγ
- Diplomatic edition: none
<supplied reason="undefined" evidence="similar">αβγ</supplied> or @reason="lost"
The value ‘undefined’ is generic and does not give any detail about the current state of the text.
2.4.7. Superfluous letters/text suppressed by editor
- Editorial interpretation: {αβγ}
- Diplomatic edition: none
<surplus>αβγ</surplus> 2.4.8. Omitted letters added by editor
- Editorial interpretation: <αβγ>
- Diplomatic edition: none
<supplied reason="omitted">αβ</supplied> Letters erroneously omitted from the text, which the editor adds; omitted by mistake/accidentally.
For letters out of the support, because, for example, the latter is too little for the die, the value 'lost' should be used.
Note: it is not possible to add an
@evidence="parallel" attribute, because the
visualisation after transformation would be the same as for
Text restored by comparison with parallel seal.
2.4.9. Letters corrected by editor
- Editorial interpretation: ⌈αβ⌉
- Diplomatic edition: none
<choice>
<sic>γδ</sic>
<corr>αβ</corr>
</choice> sic is for the part to be corrected and
corr for the proposed correction.
Note: if the proposed correction concerns only a part of a word,
choice should include only the part to be
corrected:
<choice>
<sic>αβ</sic>
<corr>δε</corr>
</choice>γ = ⌈δε⌉γ It is possible to add a @resp attribute to
corr in order to mention the author of the
correction, but the latter will be also discussed in the apparatus.
Alternative: leaving the original version in the edition and adding the correction in the external apparatus criticus (see).
2.4.10. Regularisation
- Editorial interpretation: ⌈αβ⌉
- Diplomatic edition: none
<choice>
<orig>αβγ</orig>
<reg>δεζ</reg>
</choice> orig is for the part to be corrected and
reg for the proposed correction.
Regularised spellings of irregular forms, such as dialect forms, late spellings, phonetic spellings, etc. (see also the previous).
These tags are intended to make a distinction between the scribal errors (for which see the previous entry) and text normalized or regularized from a dialect or phonetic spelling, grammatical form, etc., which can not be considered errors strictly speaking. However, because there is not a Leiden symbol for this kind of regularisations, the output of this tagging after transformation is the same as the previous.
Alternative: leaving the original version in the edition and adding the correction in the external apparatus criticus (see).
2.4.11. Expansion of abbreviation
- Editorial interpretation: α(βγ)
- Diplomatic edition: none
<expan>
<abbr>α</abbr>
<ex>βγ</ex>
</expan> Abbreviation fully expanded.
abbr contains the abbreviated part, i.e. the
letters actually on the seal.
ex contains the letters added by the editor
when expanding an abbreviation.
expan contains the full expansion of an
abbreviated word or term.
Note: the tag starts at the beginning of the word, even if the word is broken between two lines.
2.4.12. Uncertain expansion of abbreviation
- Editorial interpretation: 1) α(βγ(?)), 2) α(βγ)(?)
- Diplomatic edition: none
1) <expan>
<abbr>α</abbr>
<ex cert="low">βγ</ex>
</expan>
2) <expan cert="low">
<abbr>α</abbr>
<ex>βγ</ex>
</expan>
The question mark (?) should be exactly linked to the expanded part,
inside the brackets: in this case the @cert
attribute goes with ex; if the question mark
(?) is outside the brackets, it concerns the whole word and
@cert should go with
expan.
2.4.13. Abbreviation where expansion unknown
- Editorial interpretation: α(- - -)
- Diplomatic edition: none
<abbr>α</abbr> 2.4.14. Expansion of symbol or ligature
- Editorial interpretation: (καί), Ὁ ἅ(γιος)
- Diplomatic edition: none
In case of meaning-bearing symbols, which require an expansion, they should be encoded in the interpretive edition as an expanded abbreviation.
Below a few examples of some of the most common meaning-bearing symbols:
Α, πρῶτος
<expan>
<abbr>
<am>Α</am>
</abbr>
<ex>πρωτο</ex>
<abbr>σπαθάριος</abbr>
</expan>
Α, μόνος
<expan>
<abbr>
<am>Α</am>
</abbr>
<ex>μονα</ex>
<abbr>χός</abbr>
</expan>
S, καί
<expan>
<abbr>
<am>
S
</am>
</abbr>
<ex>καί</ex>
</expan> Γ, τρί
<expan>
<abbr>Χρυσο</abbr>
<abbr>
<am>Γ</am>
</abbr>
<ex>τρί</ex>
<abbr>κλινος</abbr>
</expan>
Τhe <abbr> element contains <am> (abbreviation mark), to indicate that the symbol, while part of the abbreviation, is not part of the resolved word (i.e. the symbol in <am> will not be displayed).
See also: 2.3.4. Symbols, not meaning-bearing.
In case of ligatures to be expanded, they should be encoded in the interpretive edition as an expanded abbreviation.
Below a few examples of some of the most common ligatures:
Ο+Α, Ὁ ἅ(γιος)
<expan>
<abbr>Ὁ ἅ</abbr>
<ex>γιος</ex>
</expan>
Χ+Ρ, Χρ(υσο)τρίκλινος
<expan>
<abbr>Χρ</abbr>
<ex>υσο</ex>
<abbr>τρίκλινος</abbr>
</expan>
Μ+Γ, μ(έ)γ(ας)
<expan>
<abbr>μ</abbr>
<ex>έ</ex>
<abbr>γ</abbr>
<ex>ας</ex>
</expan>
Μ+Ρ, Μ(ήτη)ρ
<expan>
<abbr>Μ</abbr>
<ex>ήτη</ex>
<abbr>ρ</abbr>
</expan>
The <abbr> element contains the letters forming the ligature and <ex> completes the word.
See also 2.3.3. Ligatured letters.
2.4.15. Monograms
- Editorial interpretation: (Ἀθανασίου)
- Diplomatic edition: none
<expan>
<ex>Ἀθανασίου</ex>
</expan> A monogram should be treated as an expansion of abreviation.
In the diplomatic edition an hyphen (−) should separate the letters forming the monogram and, in case of a monogram with letters in the quarters, a vertical bar (|) should separate the letters in the upper quarters from those in the lower quarters.
See also: Symbols (not meaning-bearing).
2.4.16. Monograms: uncertain solution
- Editorial interpretation: 1) (Ἀθανασίου) (?), 2) (Ἀθανασίου(?))
- Diplomatic edition: none
1) <expan cert="low">
<ex>Ἀθανασίου</ex>
</expan>
2) <expan>
<ex cert="low">Ἀθανασίου</ex>
</expan> 2.4.17. Unsolved monograms
- Editorial interpretation: (Θ ΟΥ Ν Α)
- Diplomatic edition: none
<expan>
<orig>
<ex>θ ου ν α</ex>
</orig>
</expan> Of course, this is not really an expansion.
Note: it is not possible to add @cert='low'
for a particular letter in order to get a question mark (?), but it is
possible to manually add it inside ex.
2.4.18. Editor’s note
- Editorial interpretation: (!) (sic)
- Diplomatic edition: none
<note>!</note>
<note>sic</note> The note will be visualised in italic.
Alternative: the apparatus criticus, or, using the apparatus to give the correct reading, this helps to highlight the faulty version.
Note: if necessary, add a white space to separate editor’s note from the text.
2.4.19. Alternative readings
- Editorial interpretation: vel
- Diplomatic edition: none
<app type="alternative">
<lem><expan><abbr>χ</abbr><ex>α</ex><abbr>ρτελ</abbr><ex>αρίῳ</ex></expan></lem>
<rdg><expan><ex>χρυσο</ex><abbr>τελ</abbr><ex>ῇ</ex></expan></rdg>
</app> Visualisation after transformation: χ(α)ρτελ(αρίῳ) vel (χρυσο)τελ(ῇ).
The app element should have a
@type attribute of "alternative".
The alternatives could be discussed in full detail in the apparatus.
Another way to mention an alternative reading is as an entry in a separate, external, apparatus criticus (see).
2.5.1. Numerals: value known
- Editorial interpretation: ιβ´
- Diplomatic edition: none
<num value="12">ιβ</num> It is not necessary to add the tick for Greek numeral inside the tag,
because it will be automatically added after transformation in Greek
legends encoded with @>xml:lang="grc"; in
Latin legends encoded with @xml:lang="la"
obviously the tick does not apply.
2.5.2. Numerals: value unknown because lost or illegible
- Editorial interpretation: 1) [.. ? ..], 2) .. ? ..
- Diplomatic edition: none
1) <num>
<gap reason="lost"/>
</num>
2) <num>
<gap reason="illegible"/>
</num> It is visualised as a gap.
It is possible to add attributes to gap.
2.5.3. Numerals: with tick symbol/diacritic
- Editorial interpretation: ͵αχο´
- Diplomatic edition: none
<num value="1670" rend="tick">αχο</num> 2.5.4. Numerals: with range of possible values
- Editorial interpretation: (see Explanation)
- Diplomatic edition: none
<num atLeast="26" atMost="29">XXVI<gap reason="lost" extent="unknown" unit="character"/></num> = XXVI[...?...]
<num atLeast="26" atMost="29">XXVI<gap reason="lost" atLeast="1" atMost="3" unit="character"/></num> = XXVI[c. 1 - 3] Note: gap is written close to XXVI in order
to avoid a white space after transformation;
@atleast and
@atMost in num
don't have any effect on visualisation.
2.5.5. Numerals: dates (years and indictions)
- Editorial interpretation: (see Explanation)
- Diplomatic edition: none
<date>
<expan><abbr>ἰ</abbr><ex>νδικτιῶνι</ex></expan> <num value="2">Β</num>
</date> = ἰ(νδικτιῶνι) Β´
<date>ἔτους <num value="512">φιβ</num></date> = ἔτους φιβ´
<date>ἔτους
<num value="512">φιβ</num>, ἐν <expan><abbr>ἰνδ</abbr><ex>ικτιῶνι</ex></expan> <num value="11">ια</num>
</date> = ἔτους φιβ´, ἐν ἰνδ(ικτιῶνι) ια´ [year+indiction] Or it is possible to use the calendar element:
<teiHeader>
<profileDesc>
<calendarDesc>
<calendar xml:id="indiction/byzantineWorldEra/..."/>
</calendarDesc>
</profileDesc>
</teiHeader>
[...]
<date when="*" when-custom="**" datingMethod="#indiction/byzantineWorldEra/...">
</date> *Date according to the modern calendar.
**Date according to the ancient system (indiction, Byzantine world era, etc.).
2.5.6. Legend's language(s) and script(s)
- Editorial interpretation: abc αβγ
- Diplomatic edition: abc αβγ
<div type="edition" subtype="">
<div type="textpart" n="obv" xml:lang="***"/>
<div type="textpart" n="rev" xml:lang="***"/>
</div> The language and the script of a seal's legend should be encoded with
the @xml:lang attribute, associated to the
two div @type="textpart" for obverse and reverse,
nested inside div @type="edition". Because the most part of the
Byzantine seals' legends are written in a single language and in a
single alphabet, the same value will be given to both
@xml:lang.
However, it is not uncommon to work on legends written in different
languages and/or different scripts on a same seal. In those cases, the
encoding should reflect this more complex situation and the
@xml:lang's values could be different.
In order to choose the appropriate
@xml:lang's value, a SigiDoc user should
refer to the IANA Language Subtag Registry. The most common for
Byzantine seals are the following:
• Grek = Greek script
• Latn = Latin script
• grc = Ancient Greek language (to 1453; assumed to be in its standard script: Grek)
• la = Latin language (assumed to be in its standard script: Latn)
• grc-Latn = Ancient Greek Language (to 1453), rendered in Latin script
• la-Grek = Latin written in Greek script
Not all of these codes are officially registered. In fact, a project may
need specific language codes: it is recommended to define these codes
within the SigiDoc file (with langUsage) and
to create them taking into account the rules established by the Network
Working Group's RFC 5646, on which see the EpiDoc Guidelines.
The following is an example of a bilingual (Greek and Latin) legend (from the Seyrig Collection, no. 91):
<div type="edition" subtype="editorial" xml:space="preserve">
<div type="textpart" subtype="face" n="obv" rend="linear" xml:lang="grc">
<ab>
<lb n="1"/>Γεν
<lb n="2" break="no"/>ναδί
<lb n="3" break="no"/>ου
</ab>
</div>
<div type="textpart" subtype="face" n="rev" rend="linear" xml:lang="la">
<ab>
<lb n="4"/><expan><abbr>com</abbr><ex>itis</ex></expan>
<lb n="5"/><expan><abbr>Sacr</abbr><ex>arum</ex></expan>
<lb n="6"/><expan><abbr>L</abbr><ex>argitionum</ex></expan>
</ab>
</div>
</div> 2.5.7. Legend's cases
- Editorial interpretation: abc αβγ
- Diplomatic edition: abc αβγ
<div type="textpart" subtype="face" n="rev" rend="linear" xml:lang="grc">
<ab ana="gen">[text here]</ab>
</div> The @ana attribute of the element <ab> allows to encode the case(s) in which the legend has been written and this, for each face of the seal, because <ab> is a child of each <div type="textpart"> of the edition. @ana should be used with a predefined list of values.
However, due to their complexity and their literary nature, it is not recommended to use @ana for metrical legends.