ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Ebooks with ConTeXt?
Date: Tue, 10 Dec 2019 07:50:16 -0000 (UTC)	[thread overview]
Message-ID: <qsnino$71t9$1@blaine.gmane.org> (raw)
In-Reply-To: <00af8343-7bdd-7d5d-f0ac-2dc2fc810bfd@mailbox.org>

On 2019-12-10, Jan U. Hasecke <juh+ntg-context@mailbox.org> wrote:
> Am 09.12.19 um 22:13 schrieb Nicola:
>> 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)?
>
> Sorry, no info concerning ConTeXT.
>
> You don't have to use proprietary tools. An easy way to create ebooks
> from Markdown files (or other sources) is Pandoc. https://pandoc.org/
>
> I produce all of my ebooks in this way. In most cases they validate
> without errors. If there are some errors though I use Calibre to fix
> them manually.

Thanks, I didn't think of Pandoc, I'll give it a try. In the past,
I have tried to create some simple content (slides) with Markdown, but
my conclusion was that if you know TeX, it doesn't make sense to use
Markdown :)

Perhaps this is a silly question (excuse my ignorance about the topic):
what if you want to add some stylistic touches to your ebooks, such as
initials? Or Non-breaking spaces? How about adding, say, a text box with
a different background and a smaller font?

                               ***

Or fine control page numbering, headers, footnotes, ligatures, or the
spacing between paragraphs, or center a separator as above? Do you need
to modify the generated CSS for that, or would ConTeXt (or Pandoc)
allow you to take care of (some of) those things?

Nicola


___________________________________________________________________________________
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-10  7:50 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 [this message]
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
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='qsnino$71t9$1@blaine.gmane.org' \
    --to=nvitacolonna@gmail.com \
    --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).