From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trying to force a particular page sequence
Date: Wed, 26 Nov 2014 17:52:26 +0100 [thread overview]
Message-ID: <E16173C1-EDD4-455E-9464-6670BAC3EE36@rna.nl> (raw)
In-Reply-To: <847D77FC-8E4C-408D-B3F1-EA5C1D0005C0@rna.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2031 bytes --]
Answering myself: don’t use \page, use \startstandardmakeup…\stopstandardmakeup with page=no and doubledsided=no
G
On 26 Nov 2014, at 15:57, Gerben Wierda <gerben.wierda@rna.nl> wrote:
> I’m having trouble to produce a particular page sequence, all pages without page numbers:
>
> Title page (I have that)
> First left page with a text block in the lower left corner
> First right page with a statement centered, 1/3 down
>
> I’ve been trying working with \page, but what I get is
>
> Title page
> Empty page (first left)
> Right page with text (not yet in the lower left corner
> Left page with statement
> Right page with page number on top
>
> This is what I have in my prd_book.tex. What is a cleaner way to do this and also one that works? ;-):
>
> \starttext
> \start
> \startstandardmakeup \ss
> \hairline \start
> \blank[line]
> \switchtobodyfont[16pt]\bf
> \leftaligned{Foo}%
> \blank[line]
> \leftaligned{bar bar bar bar}%
> \blank[line]
> \leftaligned{Foo}%
> \stop
> \hairline \blank[line]
> \leftaligned{Foo bar foo bar bar bar bar}%
> \hairline \blank[line]\rightaligned{Gerben Wierda}%
> \blank[6cm]\start\leftskip=10cm\hairline\stop
> \rightaligned{2014}%
> \stopstandardmakeup
> \stop
> Copyright notice (should be lower left on first lefthand side page)
> \page[yes]
> \start
> \switchtobodyfont[16pt]
> ~%otherwise \blank does nothing
> \blank[6cm]
> \midaligned{Statement, centered first righthand side page}
> \stop
> \startfrontmatter
>
> ___________________________________________________________________________________
> 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: 4860 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
___________________________________________________________________________________
prev parent reply other threads:[~2014-11-26 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 14:57 Gerben Wierda
2014-11-26 16:52 ` Gerben Wierda [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=E16173C1-EDD4-455E-9464-6670BAC3EE36@rna.nl \
--to=gerben.wierda@rna.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).