Changes

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 a 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. Further, we have <pb> elements. These are used to denote pagebreaks in standard editions, which are often used for reference purposes and displayed in the margin; in the case of the ''Lives of the Sophists'', this is the 18th-century edition of Olearius. These elements are inserted at the places where these pagebreaks occur. Finally, we have the critical apparatus. Its notes are included in <app> elements. Every single entry into the apparatus is within a <rdg> (= reading) element. This should be enough to get us started. We will now look at the way in which we will typeset such a xml document with ConTeXt. == The ConTeXt style file == In order to typeset such a file with ConTeXt, we need a style file which will map xml elements and attributes to specific ConTeXt commands.