From: Daniel Lyons <fusion@storytotell.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: EPUB workflow from ConTeXt source?
Date: Thu, 17 Feb 2011 01:10:42 -0700 [thread overview]
Message-ID: <D7225CF0-F6CF-485F-BE01-C8A254EFCA93@storytotell.org> (raw)
In-Reply-To: <4D5CD577.80702@wxs.nl>
On Feb 17, 2011, at 12:59 AM, Hans Hagen wrote:
> On 17-2-2011 8:14, Gerben Wierda wrote:
>> On 16 Feb 2011, at 17:47, Wolfgang Schuster wrote:
>>
>>>
>>> Am 16.02.2011 um 17:42 schrieb Gerben.Wierda@rna.nl:
>>>
>>>> I'd like to keep working in one format so I was wondering if there is a
>>>> ConTeXt based workflow/setup that can produce EPUB (next to normal PDF)?
>>>
>>> With MkIV you can get a xml version of document with \setupbackend[export=yes].
>>
>> But that XML is not ePUB's XML, I assume.
>
> no, but one can of course convert one kind of xml into another
>
> for epub one has to provice css etc anyway (and epub is not much more than packaged html + css)
This would also be useful to me. In my experience, the unpleasant part of generating ePub is making correctly formatted manifests and putting them in the right places inside the right kinds of zip files. If ConTeXt could do this for me, it would certainly make life easier. On the other hand, it may not be appropriate to bother because there are other tools that will convert HTML to ePub for you and make the manifests (Calibre, for example).
I consider CSS intractable so that's not something I would worry about ConTeXt generating for me, if it were on the table.
> going the other way around, processing an epub file also demands some handywork as the source code is not by definition well structured
ePub is definitely structured. I would say too structured, since it makes you provide both a ToC manifest and a navigation manifest that necessarily must include almost identical information ;) Of course, depending on a simplified browser for your document viewing and having lots of secret failover modes to handle poorly formatted documents makes the structure less meaningful than it ought to be.
You are free to break your document into as many HTML chunks as you wish, but you are limited to fairly prosaic HTML and CSS. I'm of the impression the HTML documents generally map onto chapters so as not to distress the hardware's memory constraints too much.
Overall, ePub and Kindle's format strike me as too much and too little respectively. I should be able to change the font and the formatting, but I definitely consider HTML + CSS is too much complexity.
—
Daniel Lyons
___________________________________________________________________________________
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:[~2011-02-17 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:42 Gerben.Wierda
2011-02-16 16:47 ` Wolfgang Schuster
2011-02-17 7:14 ` Gerben Wierda
2011-02-17 7:59 ` Hans Hagen
2011-02-17 8:10 ` Daniel Lyons [this message]
2011-02-17 9:49 ` Hans Hagen
2011-02-17 10:48 ` Gerben Wierda
2011-02-17 18:52 ` William Adams
2011-02-18 2:43 Mica Semrick
2011-02-18 18:12 ` Daniel Lyons
2011-02-19 8:32 ` Gerben Wierda
2011-02-19 11:40 ` Hans Hagen
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=D7225CF0-F6CF-485F-BE01-C8A254EFCA93@storytotell.org \
--to=fusion@storytotell.org \
--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).