From: Mikael Sundqvist via ntg-context <ntg-context@ntg.nl>
To: "amano.kenji" <amano.kenji@proton.me>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mikael Sundqvist <mickep@gmail.com>
Subject: Re: How do I write a digital book that can become a physical book without a lot of modifications?
Date: Sat, 10 Sep 2022 15:09:59 +0200 [thread overview]
Message-ID: <CAHy-LL_ZYA=f3_KwH1kWQmVSZBC9zezEbCRJUKkrfFRvhm282A@mail.gmail.com> (raw)
In-Reply-To: <uVtNSkWNPq_MMzbTJEKptxoYwQMWA6YkXFoDjg5-NZV9uoxF6x74_5XdX3d30TUZ-WqAPzp96f2h3UCrCo263mbcnWrY7DMLms3YwgEjCAc=@proton.me>
On Sat, Sep 10, 2022 at 2:43 PM amano.kenji via ntg-context
<ntg-context@ntg.nl> wrote:
>
> A digital book doesn't need to be double-sided.
>
> But, a physical book can be double-sided.
>
> Double-sidedness may require adjusting contents in many places.
>
> How can I write a digital book that doesn't have to be heavily modified in order to become a physical book? I want almost no modification at all.
I think you can use modes: https://wiki.contextgarden.net/Modes.
Simply do different setups in different modes. Then choose the mode at
compilation time.
/Mikael
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-09-10 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 12:43 amano.kenji via ntg-context
2022-09-10 13:02 ` Henning Hraban Ramm via ntg-context
2022-09-10 13:09 ` Mikael Sundqvist via ntg-context [this message]
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='CAHy-LL_ZYA=f3_KwH1kWQmVSZBC9zezEbCRJUKkrfFRvhm282A@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=amano.kenji@proton.me \
--cc=mickep@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).