ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pagereferences
Date: Sun, 17 Jan 2016 20:59:52 +0100	[thread overview]
Message-ID: <569BF2B8.9000507@gmail.com> (raw)
In-Reply-To: <730102E8-820B-4952-A87B-193ADBB7168A@uva.nl>


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

> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 17. Januar 2016 um 20:43
> Thanks Wolfgang. I am experimenting with your code and there has 
> arisen a problem. The book I am typesetting has some pages before the 
> text on page-1 starts (cover and so on). Therefore the code
>     
> \def\mypageref[#1]{\setpagestate[hvdm][#1]\color[red]{page=\pagenumber\ and 
> pageref=\pagestaterealpage{hvdm}{#1}}}
> produces "page=29 and pageref=31". Not as intended. Do I change the 
> macro \pagestaterealpage into what macro? I tried \pagestatepage, but 
> that wasn't the right idea.
>
> Now what further to change?
You can use the dataset command which lets you store other information, 
e.g. the current value of the visible pagenumber.

\definedataset[hans][delay=yes]

\setupuserpagenumber[number=3]

\starttext

One\setdataset[hans][one][pagenumber=\userpagenumber]

\page[+2]

Two\setdataset[hans][two][pagenumber=\userpagenumber]

Three\setdataset[hans][three][pagenumber=\userpagenumber]

\blank

\ifnum0\datasetvariable{hans}{two}{realpage}=0\datasetvariable{hans}{one}{realpage}
     The references are on the same page.
\else
     The references are on different pages.
\fi

\blank

\ifnum0\datasetvariable{hans}{two}{realpage}=0\datasetvariable{hans}{three}{realpage}
     The references are on the same page.
\else
     The references are on different pages.
\fi

\page

\starttabulate
\NC One   \NC \datasetvariable{hans}{one}{pagenumber}   \NC\NR
\NC Two   \NC \datasetvariable{hans}{two}{pagenumber}   \NC\NR
\NC Three \NC \datasetvariable{hans}{three}{pagenumber} \NC\NR
\stoptabulate

\stoptext

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 3010 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:[~2016-01-17 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 15:58 pagereferences Meer, Hans van der
2016-01-17 16:42 ` pagereferences Wolfgang Schuster
2016-01-17 18:03   ` pagereferences Meer, Hans van der
2016-01-17 18:37     ` pagereferences Wolfgang Schuster
2016-01-17 19:43       ` pagereferences Meer, Hans van der
2016-01-17 19:59         ` Wolfgang Schuster [this message]

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=569BF2B8.9000507@gmail.com \
    --to=schuster.wolfgang@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).