From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Now that I have something working on mkiv, I'd like to try ePUB
Date: Wed, 18 Mar 2015 08:46:58 +0100 [thread overview]
Message-ID: <55092D72.2060509@wxs.nl> (raw)
In-Reply-To: <5D4ACBA4-46BB-4ABD-A34C-E3D0088C45DF@rna.nl>
On 3/18/2015 7:34 AM, Gerben Wierda wrote:
> On 18 Mar 2015, at 02:14, Hans Hagen <pragma@wxs.nl
> <mailto:pragma@wxs.nl>> wrote:
>
>> On 3/17/2015 10:33 PM, Gerben Wierda wrote:
>>> On 17 Mar 2015, at 16:51, Hans Hagen <pragma@wxs.nl
>>> <mailto:pragma@wxs.nl>> wrote:
>>>
>>>> On 3/17/2015 3:41 PM, Gerben Wierda wrote:
>>>>> Nobody?
>>>>>
>>>>> On 15 Mar 2015, at 22:12, Gerben Wierda <Gerben.Wierda@rna.nl
>>>>> <mailto:Gerben.Wierda@rna.nl>> wrote:
>>>>>
>>>>>> Now that I have my book project basically running on mkiv (the
>>>>>> layout probably has a few problems left, the main one currently
>>>>>> being extra whitespace after a chapter heading compared to mkii),
>>>>>> I’d like to try producing ePUB from it.
>>>>>>
>>>>>> ConTeXtgarden says I have to add a backend and points me to the
>>>>>> info on the standard project structure (which I use), but there I
>>>>>> don’t find anything about a backend. The extended example says
>>>>>> that starting january 2015, things have changed with ePUB, which
>>>>>> probably also applies to me as I only recently started with a
>>>>>> fresh download of a current ConTeXt mkiv.
>>>>>>
>>>>>> So, can someone tell me what I need to do to get a basic ePUB output?
>>>>
>>>> \setupbackend
>>>> [export=yes]
>>>>
>>>> more on wiki
>>>
>>> The wiki doesn’t really help. Am I supposed to create another product
>>> file in …/products?
>>
>> no, just enable it ... export files end up in a subpath
>
> I did add this to the environment file and tried to create an ePub for
> the whole book and for an individual chapter, but no success yet:
>
> luna-wifi:chapters gerben$ (. /usr/local/src/ConTeXt/tex/setuptex &&
> mtxrun --script epub --make c_loosely.specification)
> Setting "/usr/local/src/ConTeXt/tex" as ConTeXt root.
>
> mtx-epub | unknown specificaton file
> 'c_loosely.specification-export/c_loosely.specification-pub' for
> 'c_loosely.specification'
> luna-wifi:chapters gerben$ (. /usr/local/src/ConTeXt/tex/setuptex &&
> mtxrun --script epub --make prd_book.specification)
> Setting "/usr/local/src/ConTeXt/tex" as ConTeXt root.
>
> mtx-epub | unknown specificaton file
> 'prd_book.specification-export/prd_book.specification-pub' for
> 'prd_book.specification'
>
>
> What am I missing? What is a specification file?
you process the tex file as normal .. that will produce a specification
file that will be used if you use mtxrun --script epub later (the call
is mentioned at the end of a tex run that has the export enabled)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-03-18 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 21:12 Gerben Wierda
2015-03-17 14:41 ` Gerben Wierda
2015-03-17 15:51 ` Hans Hagen
2015-03-17 21:33 ` Gerben Wierda
2015-03-18 1:14 ` Hans Hagen
2015-03-18 6:34 ` Gerben Wierda
2015-03-18 7:46 ` Hans Hagen [this message]
2015-03-18 11:11 ` Gerben Wierda
2015-03-17 15:54 ` Procházka Lukáš Ing. - Pontex s. r. o.
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=55092D72.2060509@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).