ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Denis Maier <denis.maier.lists@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: Ebooks with ConTeXt?
Date: Tue, 10 Dec 2019 16:53:46 +0100	[thread overview]
Message-ID: <635c2920-235e-449c-5750-f21fc5d3932d@mailbox.org> (raw)
In-Reply-To: <qsnino$71t9$1@blaine.gmane.org>


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

For Pandoc: Some things can be tweaked with pandoc, but for anything 
that is a bit more advanced you'll probably need a custom CSS. For 
special content you can use spans and divs. In your custom CSS you can 
define how those elements should be rendered. Sounds pretty similar to 
what Hans wrote in his response. Probably the main questions are if you 
prefer to work with pandoc markdown or with ConTeXt sources, and if you 
need additional output formats.

Denis
___________________________________________________________________________________
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 15:53 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 [this message]
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=635c2920-235e-449c-5750-f21fc5d3932d@mailbox.org \
    --to=denis.maier.lists@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).