TODO: explain differences between export variants
== raw.xml ==
<xmlcode>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
input filename : minimal
processing date : Sat Jan 17 19:42:37 2015
context version : 2014.12.29 10:01
exporter version : 0.33
-->
<?xml-stylesheet type="text/css" href="styles/minimal-defaults.css" ?>
<?xml-stylesheet type="text/css" href="styles/minimal-images.css" ?>
<?xml-stylesheet type="text/css" href="styles/minimal-styles.css" ?>
<document xmlns:m="http://www.w3.org/1998/Math/MathML" title="My first eBook 1" version="0.33" author="{Hans 1} " context="2014.12.29 10:01" date="Sat Jan 17 19:42:37 2015" language="en" file="minimal">
<section detail="chapter" chain="chapter" level="2">
<metadata>
<metavariable name="author">Hans 3</metavariable>
<metavariable name="subtitle"></metavariable>
<metavariable name="title">My first eBook 3</metavariable>
<metavariable name="version">\date </metavariable>
</metadata>
<sectionnumber>1</sectionnumber>
<sectiontitle>Example</sectiontitle>
<sectioncontent>
<paragraph>We thrive in information--thick worlds because of our marvelous and everyday capacity to select, edit, single out, structure, highlight, group, pair, merge, harmonize, synthesize, focus, organize, condense, reduce, boil down, choose, categorize, catalog, classify, list, abstract, scan, look into, idealize, isolate, discriminate, distinguish, screen, pigeonhole, pick over, sort, integrate, blend, inspect, filter, lump, skip, smooth, chunk, average, approximate, cluster, aggregate, outline, summarize, itemize, review, dip into, flip through, browse, glance into, leaf through, skim, refine, enumerate, glean, synopsize, winnow the wheat from the chaff and separate the sheep from the goats.</paragraph>
<section detail="section" chain="section" level="3">
<sectionnumber>1.1</sectionnumber>
<sectiontitle>A section</sectiontitle>
<sectioncontent>
<paragraph>We thrive in information--thick worlds because of our marvelous and everyday capacity to select, edit, single out, structure, highlight, group, pair, merge, harmonize, synthesize, focus, organize, condense, reduce, boil down, choose, categorize, catalog, classify, list, abstract, scan, look into, idealize, isolate, discriminate, distinguish, screen, pigeonhole, pick over, sort, integrate, blend, inspect, filter, lump, skip, smooth, chunk, average, approximate, cluster, aggregate, outline, summarize, itemize, review, dip into, flip through, browse, glance into, leaf through, skim, refine, enumerate, glean, synopsize, winnow the wheat from the chaff and separate the sheep from the goats. <itemgroup detail="itemize" chain="itemize" packed="yes" symbol="1" level="1"><item><itemtag><m:math xmlns:m="http://www.w3.org/1998/Math/MathML" display="inline"><m:mo>•</m:mo></m:math></itemtag><itemcontent>First</itemcontent></item><item><itemtag><m:math xmlns:m="http://www.w3.org/1998/Math/MathML" display="inline"><m:mo>•</m:mo></m:math></itemtag><itemcontent>Second</itemcontent></item><item><itemtag><m:math xmlns:m="http://www.w3.org/1998/Math/MathML" display="inline"><m:mo>•</m:mo></m:math></itemtag><itemcontent>Third</itemcontent></item><item><itemtag><m:math xmlns:m="http://www.w3.org/1998/Math/MathML" display="inline"><m:mo>•</m:mo></m:math></itemtag><itemcontent>Fourth</itemcontent></item></itemgroup> </paragraph>
<paragraph>Thus, I came to the conclusion that the designer of a new system must not only be the implementer and first large--scale user; the designer should also write the first user manual. <break/>
The separation of any of these four components would have hurt TEX significantly. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important. <break/>
But a system cannot be successful if it is too strongly influenced by a single person. Once the initial design is complete and fairly robust, the real test begins as people with many different viewpoints undertake their own experiments.</paragraph>
<paragraph>Coming back to the use of typefaces in electronic publishing: many of the new typographers receive their knowledge and information about the rules of typography from books, from computer magazines or the instruction manuals which they get with the purchase of a PC or software. There is not so much basic instruction, as of now, as there was in the old days, showing the differences between good and bad typographic design. Many people are just fascinated by their PC’s tricks, and think that a widely--praised program, called up on the screen, will make everything automatic from now on.</paragraph>
</sectioncontent>
</section>
</sectioncontent>
</section>
<section detail="chapter" chain="chapter" level="2">
<sectionnumber>2</sectionnumber>
<sectiontitle>Quoth<descriptionsymbol detail="footnote"><sup>1</sup></descriptionsymbol></sectiontitle>
<sectioncontent>
<lines detail="lines" chain="lines">
<line><delimited detail="quotation-1">“Prophet!”</delimited> said I, <delimited detail="quotation-1">“thing of evil!—prophet still, if bird or devil!”</delimited><line>By that Heaven that bends above us—by that God we both adore—</line><line>Tell this soul with sorrow laden if, within the distant Aidenn,</line><line>It shall clasp a sainted maiden whom the angels name Lenore—</line><line>Clasp a rare and radiant maiden whom the angels name Lenore.</line></line>
<line><highlight detail="emph">Quoth the Raven <delimited detail="quotation-1">“Nevermore.”</delimited></highlight></line>
</lines>
</sectioncontent>
<description detail="footnote" chain="footnote">
<descriptiontag><sup>1</sup> </descriptiontag>
<descriptioncontent>by Edgar Allan Poe</descriptioncontent>
</description>
</section>
</document>
<break/>
</xmlcode>
(WORK IN PROGRESS)