Hi,

so, i'd never claim that context produces epub but it can be used in a
> workflow that involves epub as it outputs xml which can be transformed
>

That's a distinction that either might not matter or sometimes is lost:

http://tex.stackexchange.com/a/17642/2148
http://wiki.contextgarden.net/epub
"ConTeXt has preliminary epub <http://en.wikipedia.org/wiki/EPUB>support..."

Does ConTeXt refer to a suite of tools, or only the "context" command?
Either way, it appears that the line between the command and the tool set
is blurred a bit. This is completely understandable, too, as you wouldn't
want to write, "the ConTeXt suite of tools includes a command, mtxrun, that
can produce EPUB files" all the time when talking about EPUBs.


> supporting all variants of epub in the backend would be the same as
> hardcoding all kind of xml dts in the frontend (docbook, tei, whatever);
> instead we provide a general xml handler and a general xml export


That paragraph would be an excellent addition to the wiki; not sure where
though.

Kind regards.