I am not an author of books but of shorter articles, the longest of
which is composed of about 20 Web pages (HTML5 documents). Some parts
have started out in a markdown format very similar to the format of the
Markdown software. When an article is updated, I never modify the
markdown source but always the HTML5 version. The benefit of markdown is
when the text is *written* for the first time but is neglegible when it
is already in HTML5 form.
Markdown as well as HTML5 are fairly powerful for the medium-range
structure of a text: sections, subsections, paragraphs, ... . They are
both weak in the large structure (chapters, new pages, table of
contents, portions with non-standard width), for which I use classes of
sections such as <section id="secname" class="chapter"> with a
hand-written postprocessor to make separate HTML5 documents where
appropriate and to make a table of contents. This works just fine.
The other weakness is the fine structure inside the inline elements.
There I want not only "italic" but rather the semantic reason for it,
e.g. "ex" (object-language example consisting of words), "ex-affix"
(object-language example below word level), "gcode" (abbreviation with
fixed meaning throught the article), ... They become classes and are
used with the <span> element which, by its mere frequency, makes the
HTML5 text unreadable and thus more tedious to maintain. To see what I
talk about, you might want to look into the source of
http://hhr-m.userweb.mwn.de/de-decl/patterns/ or even worse
http://hhr-m.userweb.mwn.de/sw-fibel/wortb-wortart/ (the latter in
German but this makes no difference for the issue).
I have already considered to replace <span class="ex"> simply by the
undefined element <ex> and use it in CSS as if it were defined. It could
well work with some or most browsers but it is non-standard which I despise.
--
Helmut Richter