From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: starting a chapter on odd page
Date: Wed, 11 May 2016 13:19:41 +0200 [thread overview]
Message-ID: <65F58609-D535-4C4B-BFB9-9FCB0F856BC4@di.unito.it> (raw)
In-Reply-To: <20160511130229.52486f5a@homerow>
[-- Attachment #1.1: Type: text/plain, Size: 1903 bytes --]
Thanks marco, should I rather use
\definepagebreak
[chapterpagebreak]
[yes, odd]
?
-a-
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - StudiUm
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> http://www.fonurgia.unito.it/andrea/
--> http://www.flickr.com/photos/vanderaalle/sets/
--> http://vimeo.com/vanderaalle
--> andrea.valle@unito.it
--------------------------------------------------
"This is a very complicated case, Maude. You know, a lotta ins, a lotta outs, a lotta what-have-yous."
(Jeffrey 'The Dude' Lebowski)
> On 11 May 2016, at 13:02, Marco Patzer <lists@homerow.info> wrote:
>
> On Wed, 11 May 2016 12:38:17 +0200
> Andrea Valle <valle@di.unito.it> wrote:
>
>> in the book I’m finishing I’m using a structure like this
>>
>> \starttext
>>
>> \input c_preface.tex
>>
>> \input c_chapter1.tex
>>
>> [etc]
>>
>> \stoptext
>>
>>
>> where each .tex file contains
>>
>> \startchapter[various options]
>> \section{First section}
>> etc
>> \stopchapter
>>
>> The publisher is asking me to start each chapter on a odd page. Can I
>> do it by setting some options?
>
> \definepagebreak
> [chapterpagebreak]
> [yes, right]
>
> \setuphead
> [chapter]
> [page=chapterpagebreak]
>
> Marco
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 5057 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-11 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 10:38 Andrea Valle
2016-05-11 11:02 ` Marco Patzer
2016-05-11 11:19 ` Andrea Valle [this message]
2016-05-11 11:59 ` Marco Patzer
2016-05-11 16:02 ` Wolfgang Schuster
2016-05-12 5:34 ` Marco Patzer
2016-05-11 11:52 ` Wolfgang Schuster
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=65F58609-D535-4C4B-BFB9-9FCB0F856BC4@di.unito.it \
--to=valle@di.unito.it \
--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).