gardener
111
edits
Changes
Jump to navigation
Jump to search
m
finish so that example will work
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 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 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 <tt><pb></tt> 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.
<code>\PhilSubsection</code>, and "flush" the content of our section. If
the value is anything else (i.e., "inline"), we flush the content without
inserting a <code>\par</code>. FinallyThen, we define<code>\PhilSubsection</code> as another <code>\inmargin</code>, which willappear in the outer margin, at the same place as the chapter numbering, butin a normal font.Finally,when you look at the main text, you will see that we now have definedsetups for books, chapters, sections, but not yet for the smallest element,<tt>p</tt>. Remember: we don't want paragraph breaks for these elements, soall we need to do is "flush" them. Which means: we add the <tt>p</tt>element to the list:
<texcode>\xmlsetsetup{#1}{TEI|text|body|p}{xml:*}</texcode> and the appropriate setup is: <texcode>\startxmlsetups xml:p \xmlflush{#1}\stopxmlsetups</texcode> And that's it! This is our structure for the main text! If you typeset thexml file with this setup, you get text with marginal numbering for yourchapters and sections. We now add the bells and whistles. We begin with the Olearius pagebreaks,the <tt><pb></tt> elements. If you've followed so far, this should beeasy. As you see, these elements contain a reference to the relevantedition (the <tt>ed=</tt> attribute) and the pagenumber. If we had moreelements of this type, it would make sense to define a <tt>setsetup</tt>for every one of them. In the case of Philostratus, we will probably onlyhave Olearius, so we just add them to our list: <texcode>\xmlsetsetup{#1}{TEI|text|body|p|pb}{xml:*}</texcode> and add both the setup for the xml element and a new definition for amarginal text (since we're a bit paranoid, we still test whether the<tt>xmlattribute ed</tt> is set to <tt>Olearius</tt>). Since I want theOlearius numbers in square brackets, I needed to take a two--step approach(the square brackets would be confusing to the ConTeXt parser). So I firstdefine an inmargin <tex>\Zolearius</tex> and then a macro<tex>\Olearius</tex> which takes this value and typesets it within squarebrackets, in the outer margin, at a distance of 2em from the main text: <texcode>\startxmlsetups xml:pb \doifelse {\xmlatt{#1}{ed}} {Olearius} {\Olearius{\xmlatt{#1}{n}}} {} \defineinmargin [ZOlearius] [outer] [normal] [distance=2em,style=small] \define[1]\Olearius% {\ZOlearius{[#1]}}</texcode> [[User:Thomas|Thomas]] 1821:0831, 12 October 7 November 2010 (UTC)
