On 7-6-2012 00:00, Andy Thomas wrote:
Hello all,

I do not know, how many people are using the epub export, but here are two more 
changes in order to achieve a valid epub file with information from the context 
source:

On Jun 5, 2012, at 9:09 PM, Andy Thomas wrote:

Hi all,

in my attempts to validate epub export from my context source, I made the 
following changes to back-up.lua and mtx-epub.lua

1) the actual context language is put in the epub
2) changed the OPS directory to OEBPS. The 2.0.1 Standard does not actually say 
that is has to have that name, but I only found examples using that one, 
including the sample documents in the 2.0.1 white paper.
3) changed opf:scheme to UUID, since that is used and not a ISBN number
4) added the encoding info in the opf file
5) changed the single in double-quotes in the opf file manifest. I do not know 
if it is necessary, but this seams to be more consistent
6) the title is taken from \setupinteraction
7) the author is taken from \setupinteraction

Andy


The diff against the actual standalone is

Best send me a patched mtx-epub so that I can do a visible diff (handier than decyphering the mail).

Hans


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

Reply via email to