ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: multi-page floats
Date: Thu, 31 May 2012 20:25:18 +0200	[thread overview]
Message-ID: <C12C05E9-3B16-4A4C-B4B1-3DBCA65ECDAA@fiee.net> (raw)
In-Reply-To: <B5B0FDFC-2619-4FC1-99A5-C02AD6BC4B55@fiee.net>

Ok, some days later I'm still not where I'd like to be (and my  
deadline is overdue).
Let’s resume:

A running text is to be interrupted by spans of 3 pages.
Postponing (\startpostponing) works well for that, but I need to  
switch off page numbering on two of that 3 pages - as far as I tried,  
\setuppagenumbering as well as \setuppagenumber doesn’t work within  
postponed sections.

Further, these pages contain full-page pictures, i.e. I need them  
bleeding off the paper.
Normally, \setlayer works well for that, but I couldn’t get layers  
working within postponed sections.

Since I need these interruptions several times in a very similar way,  
I \def’ed that postponing stuff as a macro, but get errors that point  
to expanding problems (I never get those).

I’d appreciate some pointers in which direction I should think/ 
investigate further.
E.g.
- are there alternatives to postponing? perhaps multi-page floats (but  
at defined pages)?
- is there a possibility for bleeding full-page pictures without layers?
- can it work at all to change page numbering within a postponed page  
span?


Greetlings, Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

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


  reply	other threads:[~2012-05-31 18:25 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 [this message]
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
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=C12C05E9-3B16-4A4C-B4B1-3DBCA65ECDAA@fiee.net \
    --to=hraban@fiee.net \
    --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).