From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Reference + footnote = bug
Date: Tue, 17 Dec 2002 10:00:17 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021217094717.026f9e30@server-1> (raw)
In-Reply-To: <BD2E152E-1148-11D7-9CCF-0003931D13E2@mac.com>
At 11:50 PM 12/16/2002 +0100, you wrote:
>On lundi, déc 16, 2002, at 22:33 Europe/Paris, Giuseppe Bilotta wrote:
>
>>... and a rather odd bug, too!
>>
>>\setupinteraction[state=start]
>>
>>\starttext
>>Some text \goto{text with footnote\footnote{here it is} showing
>>the bug}[hook]
>>\page[yes]
>>Some text \reference[hook] referenced from before.
>>\stoptext
this has to do with the text passed to goto being submitted to quite
rigourous manipulations; footnotes are inserts and inserts, like marks and
other funny nodes often spoil things, so here the solution is it to carry
over the footnote:
\def\donaar#1[#2]%
{\dontleavehmode
\bgroup
\postponefootnotes
\doifreferencefoundelse{#2}
{\doifelsenothing{#1}
{\dosymbolreference{}{}[#2]}
{\donaarspace{#1}[#2]}}
{\unknownreference{#2}#1\relax}% \relax catches lookahead
\egroup
\referentieinfo{<}{#2}}
You can put this in the file "cont-new.tex" and see if it solves the problem
>Also it seems that instead of
>\reference[hook] referenced...
>one has to put
>\reference[hook]{} referenced...
> ^^^^
>since otherwise in the resulting typeset "referenced..." becomes
>"eferenced...".
>Is this the normal use of the command "\reference[xxx]" ?
indeed, if you want to refer to something, you use \in {something} [ref] or
\at {somepage} [there] and alike; \reference just creates one, taking an
argument which is to show up as reference:
%D There are three ways of defining a reference:
%D
%D \pagereference[here]
%D \textreference[here]{some text}
%D
%D the third alternative combines them in:
%D
%D \reference[here]{some text}
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-12-17 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 21:33 Giuseppe Bilotta
2002-12-16 22:50 ` Otared Kavian
2002-12-17 9:00 ` Hans Hagen [this message]
2002-12-17 10:00 ` Re[2]: " Giuseppe Bilotta
2002-12-17 9:18 ` Hans Hagen
2002-12-17 10:15 ` Re[2]: " Giuseppe Bilotta
2002-12-17 11:07 ` Giuseppe Bilotta
2002-12-17 14:09 ` Hans Hagen
2002-12-17 14:19 ` Re[3]: " Giuseppe Bilotta
2002-12-17 15:53 ` 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=5.1.0.14.1.20021217094717.026f9e30@server-1 \
--to=pragma@wxs.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).