From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: "Meer, H. van der" <H.vanderMeer@uva.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: Re: interaction?
Date: Fri, 25 Nov 2011 21:15:29 +0100 [thread overview]
Message-ID: <07DB25AA-1EB8-4C7A-9CB7-F68C5DABFAAB@googlemail.com> (raw)
In-Reply-To: <550DDE0C-52BF-40FE-B559-B1CC0E3D014A@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1402 bytes --]
Am 25.11.2011 um 20:26 schrieb Meer, H. van der:
>
> On 25 nov. 2011, at 18:10, Wolfgang Schuster wrote:
> >>
> >> Reference is here <\reference[label:1]{Some text}>\blank
> >> and is: \getreference[tekst][label:1]
> >
> > tekst ≠ text
>
> Wolfgang,
>
> Thanks for that one. I completely misunderstood, thinking that for text one could substitute something to typeset (like in \in{}[]) instead of regarding it as a keyword hole.
>
> For the interaction problem I have made a very tiny project. At the start of the contents is an "outer reference" inside the project files an "inner reference". The outer one can be reached both from the outside as well as from the inside of the project files. The colouring of the links show it too. Yhe inner reference does not show up, instead the log shows:
>
> references > start problematic references
> unknown > 2: [part2][label:1]
> references > stop problematic references
>
> But I do not know enough of the referencing mechanism to interprete it.
> Hope you can nail the problem, either with my doing or something within ConTeXt.
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.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2089 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:[~2011-11-25 20:15 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 ` Wolfgang Schuster [this message]
2011-11-25 20:40 ` interaction? Hans Hagen
2011-11-26 5:27 ` interaction? Wolfgang Schuster
2011-12-03 0:02 ` interaction? Hans Hagen
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=07DB25AA-1EB8-4C7A-9CB7-F68C5DABFAAB@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=H.vanderMeer@uva.nl \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).