ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Leave out reference to page if on the same page?
Date: Thu, 24 Jul 2014 13:20:56 +0200	[thread overview]
Message-ID: <B2676FE8-6415-402C-9B1F-E2BCB84F554E@gmail.com> (raw)
In-Reply-To: <53D05484.3040803@panix.com>


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

Hi Rik,

As a matter of fact the example given by Wolfgang works despite mkiv complaining about
	\analyzecurrentreference
being unknown… Whent the typesetting stops because of this command, saying « run » or rather « r » continues the typesetting.
I didn’t send the example module of Marco Patzer since it doesn’t seem to work anymore with recent versions of mkiv.

Maybe Marco has a solution for his module?

Best regards: OK


On 24 Jul 2014, at 02:34, Rik <rik@panix.com> wrote:

> On 2014-07-23 14:01, Otared Kavian wrote:
>> In my ConTeXt archives I found the following example from a discussion on the mailing list: Wolfgang S. gave an answer which may help you:
>> Best regards: OK
> 
> ...some text elided...
> 
>> one can set conditional texts but these are internal macros
>> (which can change) and meant for users.
>> 
>> Wolfgang
>> %%%% end test-ref.tex
>> 
> 
> I suspect that Wolfgang meant to warn:
> ... internal macros (which can change) and are not meant for users
> because that certainly appears to be the case. More specifically, the example (from 2011) fails, complaining about an undefined control sequence with \analyzecurrentreference.
> 
> As others pointed out in related discussions, there is another serious shortcoming with this. References should be relative to the current page spread, which on doublesided layouts includes two pages, verso and recto. A reference to something on either of these pages is traditionally considered to be current, and above and below refer to previous and subsequent page spreads.
> 
> There is a module, smartref, by Marco Patzer, that may address the needs of the original poster. It has some limitations, but generally addresses the issue quite well. See the list message at http://www.mail-archive.com/ntg-context%40ntg.nl/msg71889.html for more on smartref.
> 
> (The primary limitation in my use is that it assumes that a following argument, as in \smartref{preceding}{following}[label], should follow the at page number text, thus disabling the use of the following text to provide a subfigure label. Thus, one ends up with "see figure 6.4 at page 73a" instead of "see figure 6.4a at page 73".)
> 
> -- 
> Rik Kabel
> 
> 
> 
> 
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 4761 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
___________________________________________________________________________________

  reply	other threads:[~2014-07-24 11:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 15:46 Gerben Wierda
2014-07-23 18:01 ` Otared Kavian
2014-07-24  0:34   ` Rik
2014-07-24 11:20     ` Otared Kavian [this message]
2014-07-24 11:26       ` luigi scarso
2014-07-24 11:38         ` Wolfgang Schuster
2014-07-24 15:43           ` luigi scarso
2014-07-24 11:34       ` Wolfgang Schuster
2014-07-24 12:03         ` Otared Kavian
2014-07-24 12:10           ` Wolfgang Schuster
2014-07-25 11:06           ` Hans Hagen
2014-07-25 14:31             ` Gerben Wierda
2014-07-26  8:43               ` Hans Hagen
2014-08-01 11:30                 ` Gerben Wierda
2014-08-01 14:13                   ` Otared Kavian
2014-08-02 13:12                     ` Gerben Wierda
2014-08-02 13:24                       ` Gerben Wierda
2014-08-02 16:58                         ` Otared Kavian
2014-08-02 19:01                           ` Gerben Wierda
2014-07-25 14:34             ` Rik Kabel
2014-07-25 15:44               ` Hans Hagen
2014-07-24 13:36       ` Rik Kabel

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=B2676FE8-6415-402C-9B1F-E2BCB84F554E@gmail.com \
    --to=otared@gmail.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).