Also my chapter headers in that same book are also big and bold and over-sized – in a specific font – which also plays into a more subtle joke. Again, gone.

Also my chapter headers in that same book are also big and bold and over-sized – in a specific font – which also plays into a more subtle joke. Again, gone.

there is some merit to that thought.

the thing is, it would mean that e-book producers would still
have to go through the rigamarole of creating e-book files, and
e-book libraries and e-book-stores would have to stock them,
and e-book viewer-programs would have to deal with them,
and researchers would have to unpack them to analyze them
and then dodge their obtuse markup, and so on and so forth…

and all of these difficulties are unnecessary…

it will be far easier for everyone along the toolchain to convert
to a simpler, flat, ascii/unicode, light-markup e-book file-format.

i've already written authoring-tools and viewer-programs and
analysis-tools for this light-markup format, in various languages,
and i'm just a garage hacker/programmer with few special skills,
so i know this approach returns the best cost/benefit ratio to us.

and — to return to the original point here — it gives us the ability
to create beautifully-formatted books that are also very powerful
– without having to deal with the difficulties of obtuse markup –
with customization options that allow users to get what they want.

-bowerbird