From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: Conditional float references
Date: Tue, 24 Sep 2013 00:24:44 +0200 [thread overview]
Message-ID: <20130923222444.GR17308@homerow> (raw)
In-Reply-To: <5240707A.5000902@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1214 bytes --]
On 2013–09–23 Hans Hagen wrote:
> >a couple of times the question came up¹²³ how to create more
> >intelligent referencing. There are already mechanisms in the core,
> >namely \somewhere and \atpage but they both have drawbacks.
> >\somewhere happily prints its text if the figure is placed on the
> >same double page. In fact, no text at all should be printed if the
> >figure is visible. Furthermore it's a little verbose to use unless
> >hidden in a custom macro. \atpage on the other hand doesn't hesitate
> >to print “see figure 1.2 at page 42” while you're on page 42.
>
> Just wondering .. did you look at \atpage?
I did, indeed.
> there is some info available about reference locations
\atpage basically just calls
\strc_references_by_reference_page_state which only provides three
states: current page, before of after the current page. This is not
flexible enough, e.g. it does not take short distances into account
(next/previous page), which is nice to have but not required. More
important is that it's not aware of the concept of double pages. So
the reader is presented with “as we show above” even if the graphic
is visible on the double page.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-23 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 21:02 Marco Patzer
2013-09-23 16:46 ` Hans Hagen
2013-09-23 22:24 ` Marco Patzer [this message]
2013-09-25 3:46 ` Otared Kavian
2013-09-25 7:29 ` Marco Patzer
2013-09-25 14:40 ` Otared Kavian
2013-09-25 15:28 ` Marco Patzer
2013-10-08 21:23 ` Marco Patzer
[not found] <mailman.222.1379923068.18665.ntg-context@ntg.nl>
2013-09-24 11:37 ` Robert Blackstone
2013-09-24 11:48 ` Marco Patzer
[not found] <mailman.236.1380044639.18665.ntg-context@ntg.nl>
2013-09-24 19:52 ` Robert Blackstone
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=20130923222444.GR17308@homerow \
--to=lists@homerow.info \
--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).