Hi again, please find attached a rather minimal project structure including the produced XML export.
[1] root node
First, the exported XML file lacks a root node! Just call it <export> or <context> or whatever you like, but it MUST be there, otherwise it’s no wellformed XML.
The <document> root node is just fine from standalone documents, but is missing in exports from project structure.
If I enable xhtml mode ... the exported file stops after a few lines.
I didn’t trace that yet, since xhtml mode make so sense anyway.
[2] metadata
The metadata from \setupexport is completely ignored.
still true - is \setupexport deprecated?
The metadata from \settaggedmetadata is exported just fine, but it ends up within the first block of the first page, if that’s not empty.
still true - in this test case, within „section“; I guess <metadata> is inserted into the tree after the first tag, that should be <document>. So [2] should be fixed if [1] is.
[3] cover picture
The firstpage key of setupexport is supposed to define a cover picture for the ePub, but it doesn’t do anything
probably part of [2] - \setupexport doesn’t do anything. Since the cover picture probably doesn’t need to end up in the exported XML but in one of the ePub auxiliary files, I don’t know how it should (or used to) work at all.
[4] delimited
If \quotation{} contains more than one paragraph (in my case it’s a quote), the
...
[5] emphasis
How to markup emphasize (\em, \bf, \it, \sl) so that it gets exported? {\em Something} doesn’t.
Ok, \definehighlight[important][style=italic] is feasible. [6] paragraphs But using \startparagraph … \stopparagraph is still a bit too much, writing XML or HTML would be more comfortable. Since ConTeXt knows about paragraphs (or does it?), would it be possible to make it an option to handle implicite paragraphs like explicite? Greetlings, Hraban --- http://www.fiee.net/texnique/ http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)