48
edits
Changes
Jump to navigation
Jump to search
m
In order to typeset such '''NB:''' Some of the functionality described here has been introduced quite recently. You will need a file with ConTeXt, we need a style file which will map xml elements and attributes version not earlier than December 2010 in order to specific ConTeXt commands. try this example!
addrress of TEI by example modified
== General ==
TEI (Text Encoding Initiative) is "a consortium which collectively develops and maintains a standard for the representation of texts in digital form," to quote [http://www.tei-c.org/index.xml their own website]. They have developed a series of guidelines for editing texts in a digital form. In their latest form (which is called P 5), these guidelines weigh in at a hefty 1350 pages (OK, that's counting the bibliography and the index too; there are only 1290 pages of real text). These describe an xml format which is suitable for editing texts. The TEI guidelines have the advantage of being very well documented. There are a number of free resources available that should help everyone who is interested in getting started (one extremely helpful website with lots of tutorials, examples, and tests is [http://tbeteibyexample.kantl.be/TBE org TEI by example]). They are not (and do not aspire to be) an absolute standard that everyone has to follow, but many academic projects use these guidelines, and they should be a pretty good way to make sure that your electronic edition of a text will be useful in the future.
Since editing texts is something which quite a few users of ConTeXt are involved in, it makes sense to think about ways in which xml documents which follow the TEI guideline guidelines can be typeset with ConTeXt. We would invite users to keep a few caveats in mind:
# The TEI guidelines are very detailed because they try to cater to a large number of needs. Most users will only need a small subset of the tags and attributes which the guidelines offer (in fact, TEI is aware of this and have has a slimmed down version of their guidelines which is called [http://www.tei-c.org/Guidelines/Customization/Lite TEI Lite]. This is a very good starting place to familiarize yourself with TEI). It would not make sense to try and provide a monolithic solution that defines all TEI tags; instead, localized ConTeXt style sheets are necessary which will define a subset which is relevant for a number of texts with similar features.
# Even with this huge number of tags, TEI does not expect to be sufficient for every text. Users are encouraged to develop their own styles; again, this necessitates special ConTeXt style sheets to process such adaptations.
# Encoding and typesetting texts in xml is an ongoing process. As you go forward in your edition, you realize that you need more tags, that you need to distinguish more special cases, that you want to add more information to your edition. This means that you will have to go back and forth between your xml file and the ConTeXt style and adapt both to your needs.
== Our xml file ==
Philostratus's text is in ancient Greek, but since the text itself doesn't matter much when we talk about structure and typesetting xml, I have replaced it here with a simple lorem ipsum text that is easier to display. So here's what the first paragraphs of the xml file philostratus.xml look like:
<xmlcode>
<body>
<div xml:id="VS1" n="I" type="book">
<div xml:id="VS1.1" n="1" type="chapter"> <div xml:id="VS1.1.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="VS1.1.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="VS1.1.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
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 the <text> element has again two children: the . 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 <code><div></code> elements; to distinguish them from each other, these <code><div></code> elements have so-called attributes, so we have:
<xmlcode>
<div xml:id="VS1" n="I" type="book">
<div xml:id="VS1pVS1.1" n="praef1" type="chapter"> <div xml:id="VS1p1VS1.1.1" n="1" type="section">
</div>
</div>
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.
== 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. We have to save this file (let's call it tei-style.tex) somewhere where ConTeXt can find it (e.g., somewhere in your personal texmf tree or in the same directory as the xml file) and then typeset with the command <tt>context --environment=tei-style philostratus.xml</tt>. We will look at this file in detail: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-}\stopxmlsetups</texcode> We define a set of <code>\xmlsetups</code> in a <code>\start \stop</code> environment, and we give it a name in the namespace <tt>xml:</tt>. The first line of these setups does only one thing: the <code>\xmlsetsetup</code> operates on the current xml tree (that's what the first argument <code>{#1}</code> refers to), takes all its elements (<code>{*}</code>) and discards them (<code>{-}</code>). That means '''only''' elements which we address explicitly will be typeset. This is necessary in our case because we do not want the information in the TEI header to be typeset. For those elements we '''do''' want typeset, we have to add instructions. This involves a three-step process: # We have to add their names to a line which defines a <code>\xmlsetsetup</code># We define a specific setup for them# (optional) we define TeX commands for typesetting Let us begin with some easy steps. The xml tree we are operating on is empty now. So we first have to tell ConTeXt to pass the content of the topmost elements to its typesetting engine. The topmost element is TEI, so we write: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI}{xml:*}\stopxmlsetups \xmlregistersetup{xml:teisetups} \startxmlsetups xml:TEI \xmlflush{#1}\stopxmlsetups</texcode> So: we add the <tt>TEI</tt> element to a new <code>\xmlsetsetup</code>. We "register" the setups we have defined. And then we declare that the content of the element <tt>TEI</tt> should be passed to ConTeXt; this is what the line <code>\xmlflush{#1}</code> does. Of course, we will do the same for the <tt>text</tt> element, but not for the <tt>TEIheader</tt> element, which we do not want to be typeset. So we now have: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI|text}{xml:*}\stopxmlsetups \xmlregistersetup{xml:teisetups} \startxmlsetups xml:TEI \xmlflush{#1}\stopxmlsetups \startxmlsetups xml:text \xmlflush{#1}\stopxmlsetups</texcode> Things become a bit more interesting when we look at the next level. We will start with the text proper, which is contained in the <tt>body</tt> element. For the text, we want line numbers in the margin, and we want these linenumbers in steps of five, in a small font. Here you can see the three steps we have to take: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI|text|body}{xml:*}\stopxmlsetups \xmlregistersetup{xml:teisetups} \startxmlsetups xml:TEI \xmlflush{#1}\stopxmlsetups \startxmlsetups xml:text \xmlflush{#1}\stopxmlsetups \startxmlsetups xml:body \startlinenumbering \xmlflush{#1} \stoplinenumbering\stopxmlsetups \setuplinenumbering[location=inner, step=5, method=page, style=\tfxx, align=left, distance=0.3em, width=0.3cm] </texcode> So we have: # added the element <tt>body</tt> to our <code>\xmlsetsetup</code># added a specific setup for the element which puts its content within a <code>\startlinenumbering</code> environment # added ConTeXt setup commands for the <code>\startlinenumbering</code> environment. Things become even more interesting at the next level. When you look at our xml document, you will see that the entire body consists of different divisions in <tt>div</tt> elements; the different levels are distinguished by different <tt>type</tt> attributes. This means we cannot simply add the <tt>div</tt> element to our general <code>\xmlsetsetup</code>, but have to add a specific <code>\xmlsetsetup</code> for every type. Fortunately, ConTeXt makes it easy to address these different elements. We begin with the <tt>book</tt> level: (for clarity, I will now only show the new steps, not the entire style document): <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI|text|body}{xml:*} \xmlsetsetup{#1}{div[@type='book']}{xml:div:book}\stopxmlsetups \startxmlsetups xml:div:book \blank[line]\midaligned{\xmlatt{#1}{n}}\blank[medium] \xmlflush{#1}\stopxmlsetups</texcode> What happens here? The expression <code>div[@type='book']</code> means "every element div which has an attribute 'type' with the value 'book.'" We want a blank line before the title of the book. Then, we take the value of the <tt>n</tt> attribute (that's what the construct <code>\xmlatt{#1}{n}</code> expands to: the value of the attribute <tt>n</tt> of the current tag) and typeset it midaligned. We add another, smaller blank. And don't forget to "flush" the content of the <tt>div</tt> element! For the next level, the <tt>chapter</tt>, we need again three steps: add it to the <code>\xmlsetsetup</code>, define a setup command and a ConTeXt macro for it: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI|text|body}{xml:*} \xmlsetsetup{#1}{div[@type='chapter']}{xml:div:chapter}\stopxmlsetups \startxmlsetups xml:div:chapter \PhilSection{\xmlatt{#1}{n}} \xmlflush{#1} \par\stopxmlsetups \defineinmargin [PhilSection] [outer] [normal] [distance=0.3em,style=\tfa\bf]</texcode> So: here, the argument of the <tt>n</tt> attribute is passed to a ConTeXtmacro <code>\PhilSection</code>. This macro is defined as an<code>\inmargin</code> which will be typeset in the outer margin, in abigger, bold font. This will be the "chapter" numbering in the outermargin. For the section numbering, we take a similar approach, but as you will see,we need to define even more different setups: <texcode>\startxmlsetups xml:teisetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{TEI|text|body}{xml:*} \xmlsetsetup{#1}{div[@type='section']}{xml:div:section}\stopxmlsetups \startxmlsetups xml:div:section \doifelse {\xmlatt{#1}{n}} {1} {\xmlflush{#1}} {\doifelse {\xmlatt{#1}{rend}} {paragraph} {\par\PhilSubsection{\xmlatt{#1}{n}}\xmlflush{#1}} {\PhilSubsection{\xmlatt{#1}{n}}\xmlflush{#1}}}\stopxmlsetups \defineinmargin [PhilSubsection] [outer] [normal] [distance=0.3em,style=normal]</texcode> Here, we define a setup for the section level which contains two furthertests, for which we use ConTeXt's <code>\doifelse</code> macro. The first<code>\doifelse</code> tests if the value of the <tt>n</tt> attribute is"1," i.e., if this is the first section in a chapter. If it is, it doesnothing more than "flush" the content of this section -- remember, thenumber for the first section should not appear in the margin since it isimplied in the chapter number. It's still good to have this number -- ifyou ever decide that your typeset output should look different, theinformation is there and can be shown. But for the time being, we do notwant it to appear, and that's what the first condition does. If the<tt>n</tt> attribute's value '''isn't''' 1, another test is performed; thistime, we look at the value of the <tt>rend</tt> attribute. If thisattribute has the value "paragraph," we insert a <code>\par</code>, passthe value of the <tt>n</tt> attribute to the macro<code>\PhilSubsection</code>, and "flush" the content of our section. Ifthe value is anything else (i.e., "inline"), we flush the content withoutinserting a <code>\par</code>. Then, we define <code>\PhilSubsection</code>as another <code>\inmargin</code>, which will appear in the outer margin,at the same place as the chapter numbering, but in 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 <code>\Zolearius</code> and then a macro<code>\Olearius</code> 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}}} {}\stopxmlsetups \defineinmargin [ZOlearius] [outer] [normal] [distance=2em,style=small] \define[1]\Olearius% {\ZOlearius{[#1]}}</texcode> [[User:Thomas|Thomas]] 1121:3738, 10 October 7 November 2010 (UTC) == Removing unwanted strings from xml source == In some cases you might want to remove strings or characters from the xml source. For example ConTeXt cannot process a hashmark. The following example shows how to remove the hashmark from a xml identifier before processing with the command \cldcontext The xml source: <xmlcode><a href="#myspecialid">the previous section</a></xmlcode> The setup code: <texcode>\startxmlsetups xml:initialize \xmlsetsetup{#1}{a}{xml:*}\stopxmlsetups \xmlregistersetup{xml:initialize} \startxmlsetups xml:a \cldcontext{string.sub([[\xmlatt{#1}{href}]],2)}\stopxmlsetups</texcode> {{Getting started navbox}} [[Category:XML]]
