From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Footnotes in footnotes
Date: Sun, 28 Jan 2001 23:28:27 +0100 [thread overview]
Message-ID: <3.0.6.32.20010128232827.00accb60@server-1> (raw)
In-Reply-To: <3A72B5F0.7319C311@quicknet.nl>
At 12:50 PM 1/27/01 +0100, Taco Hoekwater wrote:
> This author has strange requests
I guess that you have the largest collection of funny requests -) I think
it would be very entertaining of you write an articles on all those cases.
>In descriptive text: sometimes I *do* want a footnotemarker in the
>text but don't want the footnote itself to be marked, and sometimes
>I don't want a footnotemarker but *do* want the footnotes to be
>marked. Contexts \footnote[-]{..} cannot do this because the resulting
>footnote cannot be referenced to.
So, in case one, what should happen to the footnote text? Should is just
disappear?
are
\footnotemark
\footnotetext
the most natural names for this?
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
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-01-28 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 15:43 Giuseppe Bilotta
2001-01-25 9:15 ` Taco Hoekwater
2001-01-26 13:05 ` Hans Hagen
2001-01-26 21:46 ` Giuseppe Bilotta
2001-01-27 11:50 ` Taco Hoekwater
2001-01-27 22:47 ` Giuseppe Bilotta
2001-01-28 22:28 ` Hans Hagen [this message]
2001-01-29 11:20 ` Taco Hoekwater
2001-01-30 13:42 ` Giuseppe Bilotta
2001-01-31 9:18 ` Hans Hagen
2001-01-28 19:13 ` Hans Hagen
2001-01-30 13:45 ` Giuseppe Bilotta
2016-08-31 20:39 Jose Luis Arellano
2016-10-16 14:17 ` Saša Janiška
2016-10-16 16:35 ` Otared Kavian
2016-10-16 17:35 ` Saša Janiška
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=3.0.6.32.20010128232827.00accb60@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).