ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: back-up.lua; mtx-epub.lua
Date: Thu, 07 Jun 2012 18:33:02 +0200	[thread overview]
Message-ID: <4FD0D7BE.8000908@wxs.nl> (raw)
In-Reply-To: <8E68CF1E-5817-4F6C-B768-3EB03D02F3AE@web.de>

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
___________________________________________________________________________________


      parent reply	other threads:[~2012-06-07 16:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 19:09 Andy Thomas
2012-06-06 22:00 ` Andy Thomas
2012-06-07 12:48   ` Henning Hraban Ramm
2012-06-07 13:53     ` Hans Hagen
2012-06-07 14:51       ` luigi scarso
2012-06-08 18:08     ` Andy Thomas
2012-06-08 18:25       ` Aditya Mahajan
2012-06-08 21:02         ` Hans Hagen
2012-06-08 21:03       ` Hans Hagen
     [not found]         ` <8EC49686-C7B3-47A1-A646-17AEC310836C@web.de>
2012-06-08 23:31           ` Hans Hagen
2012-06-09  0:38             ` Aditya Mahajan
2012-06-09 10:44               ` Hans Hagen
2012-06-09 12:58             ` Andy Thomas
2012-06-10 22:21               ` Hans Hagen
2012-06-11  5:41                 ` Andy Thomas
2012-06-11  7:35                   ` Hans Hagen
2012-06-07 16:33   ` Hans Hagen [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=4FD0D7BE.8000908@wxs.nl \
    --to=pragma@wxs.nl \
    --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).