From: Hans Hagen <pragma@wxs.nl>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: interaction?
Date: Sat, 03 Dec 2011 01:02:33 +0100 [thread overview]
Message-ID: <4ED96719.9050103@wxs.nl> (raw)
In-Reply-To: <7FF44BF7-C31E-4491-AD06-099FC559FA5B@googlemail.com>
Hi,
what was the example that went wrong?
Hans
> Am 25.11.2011 um 21:40 schrieb Hans Hagen:
>
>> On 25-11-2011 21:15, Wolfgang Schuster wrote:
>>
>>> It’s a bug (maybe wrong default settings) which was introduced with Idris request
>>> to have lists which are local to a component, when you refer to the label with
>>> the name of the component as prefix (\getreference[text][part1:label:1]) the text
>>> is shown.
>>
>> Do you have a clue where?
>
> I was wrong, I tried it now with the beta from two days ago and there is also
> the same bug, maybe this was introduced when you rewrote the project code.
>
> The odd thing is the following block from the tuc file with the two reference
> which are generated with the \reference command. The reference “label:2”
> was written in the product file and it has an empty index but the second
> reference “label:1” has the index “part1” because this is the name of
> the component file where it was set.
>
> utilitydata.structures.references.collected={
> [""]={
> ["label:2"]={
> ["entries"]={
> ["text"]="Outer reference",
> },
> ["metadata"]=17,
> ["references"]={
> ["block"]="frontpart",
> ["realpage"]=1,
> ["section"]=0,
> },
> },
> },
> ["part1"]={
> ["label:1"]={
> ["entries"]={
> ["text"]="Inner reference",
> },
> ["metadata"]=18,
> ["references"]={
> ["block"]="bodypart",
> ["realpage"]=4,
> ["section"]=2,
> },
> },
> },
> }
>
> Wolfgang
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / 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:[~2011-12-03 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 16:26 interaction? Hans van der Meer
2011-11-25 16:33 ` interaction? Wolfgang Schuster
2011-11-25 17:08 ` interaction? Meer, H. van der
2011-11-25 17:10 ` interaction? Wolfgang Schuster
[not found] ` <550DDE0C-52BF-40FE-B559-B1CC0E3D014A@uva.nl>
2011-11-25 20:15 ` interaction? Wolfgang Schuster
2011-11-25 20:40 ` interaction? Hans Hagen
2011-11-26 5:27 ` interaction? Wolfgang Schuster
2011-12-03 0:02 ` Hans Hagen [this message]
2011-12-03 7:17 ` interaction? Wolfgang Schuster
2011-12-03 10:48 ` interaction? Hans Hagen
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=4ED96719.9050103@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.com \
/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).