ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bugs in XML export (for ePub)
Date: Wed, 12 Mar 2014 11:17:38 +0600	[thread overview]
Message-ID: <4DAC2B60-0947-45F1-8691-3FD1AF28B801@fiee.net> (raw)
In-Reply-To: <151B6505-CD63-4AA1-99D7-BCD4488148D2@fiee.net>

[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]

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 <delimited detail="quotation“> is ended after the first paragraph.

Can’t reproduce that in my example, must investigate further.


> [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)

[-- Attachment #2: epub.zip --]
[-- Type: application/zip, Size: 36227 bytes --]

[-- Attachment #3: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2014-03-12  5:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  5:04 Henning Hraban Ramm
2014-03-11  6:42 ` Thangalin
2014-03-11  7:52   ` Henning Hraban Ramm
2014-03-11 17:54     ` Thangalin
2014-03-12  3:24       ` Henning Hraban Ramm
2014-03-12  4:49         ` Henning Hraban Ramm
2014-03-11  8:09 ` Henning Hraban Ramm
2014-03-11  9:33   ` Wolfgang Schuster
2014-03-12  5:17 ` Henning Hraban Ramm [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DAC2B60-0947-45F1-8691-3FD1AF28B801@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).