ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christian Dekant via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Christian Dekant <cdekant@googlemail.com>
Subject: Setting up the double pages of part beginnings
Date: Fri, 10 Sep 2021 19:25:18 +0200	[thread overview]
Message-ID: <CADuOV0rN4YnEBKt4aO9p5GJXf45GGYqZN8CHadjMSoHPhSdkOg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1559 bytes --]

Dear List,

I am trying to set up double pages at the beginning of a new part in such a
way that:
- on an odd/right-hand page there will be number and the title typeset in
some fashion, and
- on the even/left-hand page there should be a full (printpaper)size image.

If the part title ends up on an even page then there is no additional page
break (but then image and title are not on the same double-page obviously).
But there is a page break (and an empty left page) when the part title ends
up on an odd page (when you put page=right e.g.) as in the following
example:

%
% How to get rid of the empty page preceding a part title?
%

\setuppagenumbering [alternative=doublesided]

\setupexternalfigures[location=default] % cow


% startTEXpage does not increase page number => incrementpagenumber

% trimming in the print shop => printpaperwidth/height

\define[1]\FullScreen{\startTEXpage\externalfigure[#1][width=\printpaperwidth,height=\printpaperheight]\stopTEXpage\incrementpagenumber}

% tried page=yes/no/right/odd

\setuphead

[part]

[placehead=yes,

page=right,

before={\nowhitespace}, % ???

]


\starttext

\completecontent

\FullScreen{cow}

\startpart[title={A nice part}]

Some text ...

\stoppart

\FullScreen{cow}

\startpart[title={A nice part}]

Some text ...

\stoppart

\stoptext


On an additional note: I would love to utilise the XML capabilities of
context, so ... is the usage of \startTEpage XML-export-friendly?

Anyway, best regards, thank you for your patience in advance and a happy
weekend for everybody!

Cheers
Christian

[-- Attachment #1.2: Type: text/html, Size: 3441 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2021-09-10 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 17:25 Christian Dekant via ntg-context [this message]
2021-09-11  6:31 ` Pablo Rodriguez via ntg-context
2021-09-11 11:25 ` Wolfgang Schuster via ntg-context
2021-09-12 18:58   ` Christian Dekant via ntg-context
2021-09-13 20:18     ` Bruce Horrocks via ntg-context
2021-09-13 21:36       ` Wolfgang Schuster via ntg-context

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=CADuOV0rN4YnEBKt4aO9p5GJXf45GGYqZN8CHadjMSoHPhSdkOg@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=cdekant@googlemail.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).