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:10:34 +0100	[thread overview]
Message-ID: <383cd833-93ee-5587-8b84-4386f405bead@mailbox.org> (raw)
In-Reply-To: <qsnino$71t9$1@blaine.gmane.org>

Am 10.12.19 um 08:50 schrieb Nicola:
> On 2019-12-10, Jan U. Hasecke <juh+ntg-context@mailbox.org> wrote:

> 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?

Ebooks are xhtml so styles are limited to the capabilities of css. I
fear that initials has to be left flowing images.

>                                ***
> 
> 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?

No page numbers in E-Books and I would avoid headers. Footnotes are
endnotes. Ligatures might be possible if directly inserted, sorry never
tried this in an ebook.

You can modify the css to achieve what is possible in xhtml, though.

I have to confess that I never managed to create an ebook with context
right aways. AFAIK, please correct me Hans, you end up with an epub
folder not the compressed epub itself. I would guess that it is a good
thing if you want to postprocess the book manually by editing content
files or css.

What I can say about epub generally is: It's better to avoid fancy
styling at all and use the default fonts and styles of the ebook devices.

HTH
juh
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2019-12-11  6:10 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 [this message]
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=383cd833-93ee-5587-8b84-4386f405bead@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).