gardener
111
edits
Changes
Jump to navigation
Jump to search
m
<?context-directive job ctxfile sophiststei.ctx ?>
continuing
<xmlcode>
<?xml version="1.0"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
</front>
<body>
<div xml:id="VS1" n="ΑI" type="book"> <div xml:id="VS1pVS1" n="praef1" type="chapter"> <div xml:id="VS1p1VS1.1" n="1" type="section">
<p>Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed
diam nonumy eirmod tempor invidunt
nonumy eirmod tempor invidunt.</p>
</div>
<div xml:id="VS1p2VS1.2" n="2" rend="inline" type="section">
<p>ut labore et dolore magna aliquyam erat, sed diam
voluptua. <pb ed="Olearius" n="481"/> At vero eos et accusam et
amet</p>
</div>
<div xml:id="VS1p3VS1.3" n="3" rend="paragraph" type="section">
<p>Duis autem vel eum iriure dolor in hendrerit in vulputate
velit esse molestie consequat, vel illum dolore eu feugiat
</xmlcode>
So let's have a look at this file. This can be brief since most of the tags are described in the TEI guidelines and tutorials. Every TEI file has as its root level (i.e. the "outer" level of the xml file) the element <xmlcode><TEI> </TEI></xmlcode> which defines it as a TEI xml file. Everything else is a "child" of this root level. At the next level, you see two of these children: on the one hand, the <teiHeader> element. This contains meta-information about your electronic edition: title, author, editor, publication status, source of your edition. There can be much more information here. This is meta-information which will usually not be typeset in your edition. The other child is the <text> element. This is what will really be in a typeset, printed edition. As you see, this has again two children: the <front>, which contains the title of the work you edit in the form in which it will appear in your typeset document, prefatory material, etc. The <body> element contains the text itself. This text has a logical structure: It consists of books, chapters, and sections. All of these logical parts are expressed via different <div> elements; to distinguish them from each other, these <div> elements have so-called attributes, so we have: <xmlcode> <div xml:id="VS1" n="I" type="book"> <div xml:id="VS1p" n="praef" type="chapter"> <div xml:id="VS1p1" n="1" type="section"> </div> </div> </div></xmlcode> As you can see, most of these <div> elements have other attributes as well: the "xml:id" attribute gives every section in your document a unique identifier. This makes it easier if you want to refer to these sections later. You are free to choose these attributes; as an example, I have opted for a short numeric tag that refers to the paragraph. The "n" attribute is the name of the section as it will appear in your typeset edition. For classical prose texts, it is customary to have the chapter and section numbers appear in the margin of the edition, with no prefix and no additional information about the structure. E.g., at the beginning of chapter 8, there will be bold '''8''' in the margin (the mark for "section 1" is understood and usually not expressed). For subsequent sections of chapter 8, there will be smaller section numbers in the margin, like "2," "3," etc. Finally, such sections of chapters do not necessarily begin a new paragraph. In order to make this clear, I have used the "rend" attribute (not exactly in the way TEI defines it, but close enough). For sections, I have two types of "rend" attributes" "inline" means that this section should just continue the typographical paragraph; "paragraph" means that it should be begin in a new paragraph. This is an important distinction which I want to emphasize: in your typeset edition, these two will appear very different. For the '''logical''' structure of your digital text, however, they are both on the same level. That's why they are both <div> of the same type, but with different "rend" attributes. --[[User:Thomas|Thomas]] 0911:0337, 10 October 2010 (UTC)
