From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: start/stopregister
Date: Thu, 25 Apr 2024 18:16:08 +0200 [thread overview]
Message-ID: <4820b727-b0d6-45e9-b3cc-dcc5bf6c9a16@xs4all.nl> (raw)
In-Reply-To: <D072A65D-DBE5-454D-A124-A3AAA33B52C2@bittext.nl>
On 4/25/2024 4:51 PM, Taco Hoekwater wrote:
>
>
>> On 25 Apr 2024, at 16:45, Thomas A. Schmitz <thomas.schmitz@uni-bonn.de> wrote:
>>
>> On 4/25/24 16:13, Henning Hraban Ramm wrote:
>>> I’m using it like
>>> \startregister[index][bibliografie]{Bibliografie}
>>> …
>>> \stopregister[index][bibliografie]
>>> i.e. very similar to your example, and can confirm it doesn’t result in a page range in the index. Also gives no error.
>>
>> Since I've become an expert on tuc files since yesterday (ha!): if I compare the tuc from a mkiv and a mkxl run, I see that mkiv produces an entry ["lastrealpage"]=9 in the references table, mkxl doesn't. This appears to be the relevant bit, and it is connected with the replacement of realpageno by c_realpageno in line 638 of strc-reg.lmt
>>
>> references.lastrealpage = texgetcount(c_realpageno)
Let's seen if we can make Thomas more of an expert as he's zooming in on
the issue:
extendregister {
metadata = { name = name },
references = { abel = label },
}
Let me know if you't see it.
> Possibly related: I noticed last week that mkxl does not update the legacy counter \pageno any more for every page.
i'll check it
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-04-25 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 13:44 [NTG-context] start/stopregister Thomas A. Schmitz
2024-04-25 14:13 ` [NTG-context] start/stopregister Henning Hraban Ramm
2024-04-25 14:45 ` Thomas A. Schmitz
2024-04-25 14:51 ` Taco Hoekwater
2024-04-25 16:16 ` Hans Hagen [this message]
2024-04-25 16:27 ` Thomas A. Schmitz
2024-04-26 7:30 ` Thomas A. Schmitz
2024-04-26 7:54 ` Thomas A. Schmitz
2024-04-26 8:22 ` Hans Hagen
2024-04-26 9:31 ` Thomas A. Schmitz
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=4820b727-b0d6-45e9-b3cc-dcc5bf6c9a16@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).