ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: placefigure feature request ?
Date: Tue, 04 Apr 2006 18:53:55 +0100	[thread overview]
Message-ID: <E1FQpj1-0000jr-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Tue, 04 Apr 2006 19:15:34 +0200." <4432A9B6.1030802@wxs.nl>

>> It would be nice if placefigure can be able to detect if the best
>> place is the top or the bottom of the page accordingly to its call,

A related point, which I didn't fiugre out how for my own TeX
figure-placement macros, is correct sequential numbering when some
figures are at the top of the page.  Some pseudocode on one page:

=============== snip ===================
\ref{figure:narrow} is a narrow figure.

\figuremacro{figure:narrow}{narrowfig.1}{A narrow figure.}

\ref{figure:wide} is a wide figure.

\figuremacro{figure:wide}{widefig.1}{A wide figure}
=============== snip ===================

Here \figuremacro figures out (sorry) that narrow figures go in the
margin and wide figures go at the top of the page.  But the page will
look funny: The narrow figure will be numbered, say, Figure 10, and
the wide figure will be Figure 11, but Figure 11 will appear before
Figure 10 on the page.  Which is disconcerting to the reader.  

One solution is to look at all the figures on the page and then number
them, instead of numbering them when \figuremacro is executed.  I
couldn't figure out how to do that in my TeX macros, but maybe there
are hooks into the context output routine for such tricks?

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  reply	other threads:[~2006-04-04 17:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 15:44 Renaud AUBIN
2006-04-04 17:15 ` Hans Hagen
2006-04-04 17:53   ` Sanjoy Mahajan [this message]
2006-04-04 21:06     ` Hans Hagen
2006-04-04 23:23       ` Sanjoy Mahajan
2006-04-05  7:37         ` Hans Hagen
2006-04-05  7:54           ` Taco Hoekwater
2006-04-05 15:43             ` Sanjoy Mahajan
2006-04-05 18:06               ` Hans Hagen
2006-04-05 19:37                 ` Sanjoy Mahajan
2006-04-05 20:46                   ` Hans Hagen
2006-04-06  2:20                     ` Sanjoy Mahajan
2006-04-06  8:01                       ` Taco Hoekwater
2006-04-04 21:23     ` Hans Hagen
2006-04-05 15:48       ` Sanjoy Mahajan
2006-04-05 16:53         ` Hans Hagen
2006-04-12 22:12       ` Sanjoy Mahajan
2006-04-13  7:57         ` Hans Hagen
2006-04-13 13:30           ` Sanjoy Mahajan
2006-04-14  8:52             ` Hans Hagen
2006-04-14 13:59               ` Sanjoy Mahajan
2006-04-14 14:09                 ` Hans Hagen
2006-04-14 16:45                   ` Sanjoy Mahajan

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=E1FQpj1-0000jr-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).