May contain:,<add<\/a>>|<anchor<\/a>\/>|<choice<\/a>>|<date<\/a>>|<del<\/a>>|<delSpan<\/a>\/>|<floatingText<\/a>>|<lb<\/a>\/>|<lg<\/a>>|<metamark<\/a>>|<note<\/a>>|<num<\/a>>|<pb<\/a>\/>|<restore<\/a>>|<seg<\/a>>|<stamp<\/a>>|<unclear<\/a>> The The value of the [xml]\n<seg n="MS-UoR-2934,[0127]">[\/xml]<\/p>\n <\/div>\n<\/div><\/p>\n In the case of a sentence that eventually did not make it into the base text, take the number of the preceding sentence that did make it into the base text, add a vertical bar (|<\/strong>)\u00a0and continue numbering:<\/p>\n [xml]\n<seg n="MS-UoR-2934,[0127|001]">[\/xml]<\/p>\n <\/div>\n<\/div><\/p>\n The first number should always consist of 4 digits: (0001<\/strong> and so on), the second number (after the vertical bar) should always consist of 3 digits: (001<\/strong> and so on).<\/p>\n <\/div> In manuscripts (not typescripts!), because we follow a more document-oriented hierarchy, we have to close all [xml]\n<div type="page" rend="recto" n="01r"> <\/div>\n<\/div><\/p>\n <\/div> This type of [xml]\n<seg type="paralipomena" n="MS-UoR-2934,[0034]">[\/xml]<\/p>\n <\/div>\n<\/div><\/p>\n These <\/p>\n
\nAttributes:,@n<\/strong><\/span>|@rend<\/strong>|@type<\/strong>|@version<\/strong><\/span>
\n[\/table]<\/p>\n
\nWhat is it?<\/h3>\n
<seg><\/code> tag contains a sentence in the manuscript. To make the edition's\u00a0collation and Synoptic Sentence View tools work, we\u00a0give each sentence a sentence number. These numbers are derived from the module's 'base text' – usually its first edition.<\/p>\n
\nAttributes<\/h3>\n
@n<\/code> attribute starts with the manuscript's catalogue number, followed by a comma, and ends with the sentence number itself in between square brackets. For example:<\/p>\n<seg><\/code> tags before moving on to the next facsimile. Whenever a sentence continues on another facsimile (e.g. from \"01r\"<\/code> to \"02r\"<\/code>), we link these two parts of the sentence together by using the @rend<\/code> attribute, adding the values \"part1\"<\/code> and \"part2\"<\/code> (and, in the case of extremely long sentences, \"part3\"<\/code>, \"part4\"<\/code>, etc.). For example:<\/p>\n
\n\t<pb n="01r">
\n\t<p>
\n\t\t<seg>\u2026<\/seg>
\n\t\t<seg rend="part1">\u2026<\/seg>
\n\t<\/p>
\n<\/div>
\n<div type="page" rend="verso" n="01v"><\/div>
\n<div type="page" rend="recto" n="02r">
\n\t<pb n="02r">
\n\t<p>
\n\t\t<seg rend="part2">\u2026<\/seg>
\n\t\t<seg>\u2026<\/seg>
\n\t<\/p>
\n<\/div>[\/xml]<\/p>\n
\nWe distinguish four\u00a0types of <seg><\/code>s:<\/p>\n\n
@type<\/code> attribute),<\/li>\ntype=\"paralipomena\"<\/code>),<\/li>\ntype=\"alternative\"<\/code>),<\/li>\ntype=\"transposition\"<\/code>).<\/li>\n<\/ol>\nParalipomena<\/h5>\n
<seg><\/code> contains a loose jotting (e.g. on the left hand page). Most loose jottings do not clearly correspond to any particular sentence in the text, and therefore do not need further attributes, except<\/strong>\u00a0if they can be linked to a certain sentence. In that case, they receive the @n<\/code> attribute of that sentence:<\/p>\n<seg><\/code>s will be included in the Synoptic Sentence View, not declared as "version" of the sentence, but as "loose jotting" pertaining to the sentence:<\/p>\n
![\"loose\"](\"https:\/\/bdmpmanual.uantwerpen.be\/wp-content\/uploads\/2014\/05\/loose.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/bdmpmanual.uantwerpen.be\/wp-content\/uploads\/2014\/09\/open.png\")
<\/a><\/pre>\n![\"\"](\"https:\/\/bdmpmanual.uantwerpen.be\/wp-content\/uploads\/2014\/09\/transp.png\"){kind=spacer}
<\/a><\/pre>\n