ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: Ebooks with ConTeXt?
Date: Wed, 11 Dec 2019 07:22:23 +0100	[thread overview]
Message-ID: <876c3238-e2b0-f85c-51be-ecf585d1926b@mailbox.org> (raw)
In-Reply-To: <qsos7a$1qa7$1@blaine.gmane.org>

Am 10.12.19 um 20:38 schrieb Nicola:
> As for ConTeXt, I have tried the latest beta with:
> 
>     context mybook.tex
>     mtxrun --script epub --make mybook
> 
> This, among the rest, creates an .epub file, which unfortunately the
> above mentioned tools do not like (maybe, that output is still
> experimental?). 

From time to time I publish an ebook either created with Pandoc or with
the pythonic Sphinx documentation tool. In most cases Pandoc epubs
validate fine. Sphinx only lately produces epub that validates without
errors. But I had issues with Apple when I tried to publish a valid epub
on their platform.

You can validate epubs with epubcheck:
https://github.com/w3c/epubcheck

I don't know if ConTeXt produces epub2 or epub3.
http://idpf.org/epub/30/

HTH
juh

-- 
Das ZEN von Pandoc
Bücher und E-Books einfach und professionell produzieren
http://www.amazon.de/Das-ZEN-von-Pandoc-professionell/dp/1505218799/
Paperback (232 Seiten) und E-Book
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-12-11  6:22 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 [this message]
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
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=876c3238-e2b0-f85c-51be-ecf585d1926b@mailbox.org \
    --to=juh+ntg-context@mailbox.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).