ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: multi-page floats
Date: Tue, 5 Jun 2012 19:55:18 +0200	[thread overview]
Message-ID: <62FEB7A7-886E-4687-9A3E-D5F3C65F5C02@googlemail.com> (raw)
In-Reply-To: <DD80658C-00A2-4DC2-8CED-EE4FF2ECDB22@fiee.net>


Am 05.06.2012 um 14:00 schrieb Henning Hraban Ramm:

> Sorry for coming back again and again, but I’m still stuck, and my deadline is overdue.
> 
> * I need full-page pictures on defined pages in the middle of a chapter.
> 
> * I don’t care if I must define "on page x" or "on the next right page after the current paragraph".
> 
> - The only way for full-page pictures (i.e. bleeding over the page) that I know of is layers.
> - The only way to interrupt a story with full-page content that I know of is postponing.
> (makeups were a dead end so far - maybe they can help to get to a right page withput using \page[right])
> 
> While each works for itself, I can’t get layers working within postponing.
> 
> And when that works, I need to wrap it in a macro, since I alway need to define and postpone three sequential pages.

\starttext

\dorecurse{3}{\input tufte\par}

\startpostponing
\offset
  [x=-\the\dimexpr\backspace+1cm\relax,
   y=-\the\dimexpr\topspace+\headerheight+\headerdistance+1cm\relax]
  {\externalfigure[mill][width=\the\dimexpr\paperwidth+2cm\relax,height=\the\dimexpr\paperheight+2cm\relax]}
\page
\stoppostponing

\dorecurse{5}{\input tufte\par}

\stoptext

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2012-06-05 17:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-27 14:06 Henning Hraban Ramm
2012-05-28 17:27 ` Hans Hagen
2012-05-28 19:47   ` Henning Hraban Ramm
2012-05-31 18:25     ` Henning Hraban Ramm
2012-05-31 21:48       ` Hans Hagen
2012-06-04 12:03         ` Henning Hraban Ramm
2012-06-05 12:00           ` Henning Hraban Ramm
2012-06-05 12:33             ` luigi scarso
2012-06-05 12:42               ` luigi scarso
2012-06-05 16:01                 ` Henning Hraban Ramm
2012-06-05 16:08                   ` luigi scarso
2012-06-05 16:17                     ` luigi scarso
2012-06-05 18:25                       ` Henning Hraban Ramm
2012-06-06  7:37                         ` luigi scarso
2012-06-06  9:39                           ` luigi scarso
2012-06-06  9:52                             ` luigi scarso
2012-06-07 12:51                               ` Henning Hraban Ramm
2012-06-05 15:59               ` Henning Hraban Ramm
2012-06-05 17:55             ` Wolfgang Schuster [this message]
2012-06-05 18:35               ` Henning Hraban Ramm
  -- strict thread matches above, loose matches on Subject: below --
2001-09-03  7:52 Multi-page floats Giuseppe Bilotta
2001-09-04  9:14 ` Hans Hagen

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=62FEB7A7-886E-4687-9A3E-D5F3C65F5C02@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).