<layout>
<layout> describes how text is laid out on the page, including information about any ruling, pricking, or other evidence of page-preparation techniques. [10.7.2 Writing, Decoration, and Other Notations] | |||||||||||||||||||||||||
Modul | msdescription — 10 Manuscript Description | ||||||||||||||||||||||||
Attribute | att.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change))
| ||||||||||||||||||||||||
Mitglied des | |||||||||||||||||||||||||
Enthalten in | msdescription: layoutDesc | ||||||||||||||||||||||||
Kann enthalten | core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note num orig p pb ptr q quote ref reg rs said sic soCalled sp stage term time title unclear figures: figure formula notatedMusic table gaiji: g msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width namesdates: addName affiliation bloc climate country district forename genName geo geogFeat geogName listEvent listNym listOrg listPerson listPlace listRelation location nameLink offset orgName persName placeName population region relationGrp roleName settlement state surname terrain trait nets: eTree forest graph listForest tree tagdocs: att classSpec code eg egXML elementSpec gi ident listRef macroSpec moduleSpec schemaSpec specDesc specGrp specGrpRef specList tag val textstructure: floatingText | ||||||||||||||||||||||||
Deklaration |
element layout { att.global.attributes, att.global.linking.attributes, att.global.analytic.attributes, att.global.facs.attributes, att.global.change.attributes, attribute columns { list { data.count, data.count? } }?, attribute ruledLines { list { data.count, data.count? } }?, attribute writtenLines { list { data.count, data.count? } }?, macro.specialPara } | ||||||||||||||||||||||||
Beispiel | <layout columns="1" ruledLines="25 32">Most pages have between 25 and 32 long lines ruled in lead.</layout> | ||||||||||||||||||||||||
Beispiel | <layout columns="2" ruledLines="42"> <p>2 columns of 42 lines ruled in ink, with central rule between the columns.</p> </layout> | ||||||||||||||||||||||||
Beispiel | <layout columns="1 2" writtenLines="40 50"> <p>Some pages have 2 columns, with central rule between the columns; each column with between 40 and 50 lines of writing.</p> </layout> |