From: Hans Hagen <j.hagen@xs4all.nl>
To: Nicola <nvitacolonna@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ebooks with ConTeXt?
Date: Tue, 10 Dec 2019 09:40:25 +0100 [thread overview]
Message-ID: <c790af7d-c958-cd81-a832-28e92a6f482f@xs4all.nl> (raw)
In-Reply-To: <qsmdcs$2uoa$1@blaine.gmane.org>
On 12/9/2019 10:13 PM, Nicola wrote:
> What is the current status of epub support in ConTeXt?
>
> I have never followed ConTeXt's development on the XML front too
> closely, but recently I have been asked to help format a text-only
> manuscript for publishing on platforms such as Kindle or Apple Books
> Store. Can ConTeXt be used (or perhaps even recommended) for that? Or
> would I have better luck with the proprietary tools (Kindle Create,
> iBooks Author)?
context has an xml export (a few variants) and one can start from that
... in the end it all boils down to some css (depends on the book i
guess) and tagged content (one can use the divs and spans output or
transform the xml to whatever wanted) ... for more complex setups i
think there are no generic solutions (unless all books should look
alike) ... of course for 'proze, itemize, simple table, simple
sectioning' not much is needed
(i gave away my ebook device so i can't check what's the fashion right
now but as color e-ink seems to be on it's way ...)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-12-10 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 21:13 Nicola
2019-12-10 7:05 ` Jan U. Hasecke
2019-12-10 7:50 ` Nicola
2019-12-10 15:53 ` Denis Maier
2019-12-10 16:50 ` Henning Hraban Ramm
2019-12-10 19:38 ` Nicola
2019-12-11 6:22 ` Jan U. Hasecke
2019-12-11 6:10 ` Jan U. Hasecke
2019-12-11 9:01 ` Hans Hagen
2019-12-11 15:17 ` Rik Kabel
2019-12-11 15:45 ` Henning Hraban Ramm
2019-12-11 17:53 ` Rik Kabel
2019-12-10 8:40 ` Hans Hagen [this message]
2019-12-10 19:50 ` Nicola
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=c790af7d-c958-cd81-a832-28e92a6f482f@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=nvitacolonna@gmail.com \
/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).