ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context <ntg-context@ntg.nl>
Subject: Re: how to: doublesided component but no empty pages
Date: Fri, 16 Feb 2001 17:48:42 +0100	[thread overview]
Message-ID: <3.0.6.32.20010216174842.01a86160@server-1> (raw)
In-Reply-To: <01021616465201.00577@bilbo>

At 04:46 PM 2/16/01 +0100, Uwe Koloska wrote:
>Hello Hans, hello all,
>
>is it possible to use components in a document with doublesided layout, 
>without forcing each component to start at an odd page?
>
>I am making a journal and have all articles organized as components -- that 
>helps setting each article and then combining all in one journal.  The 
>titlepage and the last page are components as well.  So I don't want to 
>have an empty page after the title- and backpage ...

In what sense components? You can set up chapter etc titles to start on any
page: 

\setupsection[chapter][page=yes] % right = default  

>Is this possible with components?  Is this a proper use of components, or 
>shall I use another structure?

if you use sectionblocks, you can also set the page key there. 

if you use standardmakeup, you can pass key/value pairs concerning page and
doublesided, see qrc. 

Hans 
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


      reply	other threads:[~2001-02-16 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16 15:46 Uwe Koloska
2001-02-16 16:48 ` Hans Hagen [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=3.0.6.32.20010216174842.01a86160@server-1 \
    --to=pragma@wxs.nl \
    --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).