ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: Reference + footnote = bug
Date: Tue, 17 Dec 2002 11:00:24 +0100	[thread overview]
Message-ID: <984752133.20021217110024@iol.it> (raw)
In-Reply-To: <BD2E152E-1148-11D7-9CCF-0003931D13E2@mac.com>

Monday, December 16, 2002 Otared Kavian wrote:


OK> 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
>>

OK> Also it seems that instead of
OK> \reference[hook] referenced...
OK> one has to put
OK> \reference[hook]{} referenced...
OK>                 ^^^^
OK> since otherwise in the resulting typeset "referenced..." becomes 
OK> "eferenced...".
OK> Is this the normal use of the command "\reference[xxx]" ?

Uh, yes, that was an overlook on my part --use \pagereference
instead of \reference if you don't want to attach a text in the
reference. The bug is with the \footnote within the \ref. I
*think* it might be because the \footnote becomes a reference
itself, and it seems that ConTeXt doesn't deal well with refs
within refs ...

-- 
Giuseppe "Oblomov" Bilotta

  parent reply	other threads:[~2002-12-17 10: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
2002-12-17 10:00   ` Giuseppe Bilotta [this message]
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=984752133.20021217110024@iol.it \
    --to=gip.bilotta@iol.it \
    --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).