From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/114563
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
Newsgroups: gmane.comp.tex.context
Subject: Re: Make footnote/endnote number not superscript?
Date: Sun, 20 Mar 2022 17:18:43 -0400
Message-ID: <e2640941-e04e-e25b-c71a-f05d76236433@rik.users.panix.com>
References: <60E83795-BE21-45A8-A99E-D9A1CD7F9BED@scorecrow.com>
 <e150decf-554f-cb42-b634-05b2b23e09f2@gmail.com>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3919265169050886329=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="36725"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 Thunderbird/91.7.0
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Original-X-From: ntg-context-bounces@ntg.nl Sun Mar 20 22:19:20 2022
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1nW2xM-0009ML-5N
	for gctc-ntg-context-518@m.gmane-mx.org; Sun, 20 Mar 2022 22:19:20 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 2517528990D;
	Sun, 20 Mar 2022 22:18:55 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RVlVgURbtexc; Sun, 20 Mar 2022 22:18:53 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id DEECE289386;
	Sun, 20 Mar 2022 22:18:52 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id A48B0286DCA
 for <ntg-context@ntg.nl>; Sun, 20 Mar 2022 22:18:50 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id tnm8MTEdnzVT for <ntg-context@ntg.nl>;
 Sun, 20 Mar 2022 22:18:49 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.89;
 helo=mailbackend.panix.com; envelope-from=context@rik.users.panix.com;
 receiver=<UNKNOWN> 
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 2440A283647
 for <ntg-context@ntg.nl>; Sun, 20 Mar 2022 22:18:48 +0100 (CET)
Original-Received: from [192.168.1.106] (cpe-69-204-136-231.nycap.res.rr.com
 [69.204.136.231])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 4KM9bT2yTTz12pT
 for <ntg-context@ntg.nl>; Sun, 20 Mar 2022 17:18:45 -0400 (EDT)
Content-Language: en-US
In-Reply-To: <e150decf-554f-cb42-b634-05b2b23e09f2@gmail.com>
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:114563
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/114563>

This is a multi-part message in MIME format.
--===============3919265169050886329==
Content-Type: multipart/alternative;
 boundary="------------fHHc21aV1O8WU5ktGDNSD7Nb"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------fHHc21aV1O8WU5ktGDNSD7Nb
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 2022-03-20 17:07, Wolfgang Schuster via ntg-context wrote:
> Bruce Horrocks via ntg-context schrieb am 20.03.2022 um 21:10:
>> I'm editing a book that will be printed, however the authors have 
>> included URLs which will no doubt suffer from "bit rot" in no time at 
>> all. I think it will make the main text cleaner if I use endnotes 
>> rather than include the URL in-line in the text or as a (distracting) 
>> footnote. So when the author writes "See my video at <long Youtube 
>> URL>" I will print "See my video at link 1". At the back of the book, 
>> in an appendix somewhere, I then use \placenotes to display a table 
>> of the actual URLs for any readers that want to type them in.
>>
>> I want the "link 1" bit to be normal text rather than superscript so 
>> it's more visible. Using the \setupnote[textstyle=...] command I can 
>> change the style of the number but not the superscript placing.
>>
>> Is there a way to remove the superscript placing, please?
>
> \starttext
>
> First\footnote{Footnote one}
>
> \setupnote[footnote][textcommand=]
>
> First\footnote{Footnote two}
>
> \stoptext
>
> Wolfgang
>
You might want to define a separate set of notes, for example, 
linknotes, defined as Wolfgang suggests, so

    \setupnote[linknote][textcommand=]

so that they are a separate sequence. These would be used exclusively 
for the url links you describe and regular footnotes would continue to 
be superscript (or however else you choose to treat them). You can 
define multiple streams of footnotes and endnotes.

-- 
Rik

--------------fHHc21aV1O8WU5ktGDNSD7Nb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2022-03-20 17:07, Wolfgang Schuster
      via ntg-context wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:e150decf-554f-cb42-b634-05b2b23e09f2@gmail.com">Bruce
      Horrocks via ntg-context schrieb am 20.03.2022 um 21:10:
      <br>
      <blockquote type="cite">I'm editing a book that will be printed,
        however the authors have included URLs which will no doubt
        suffer from "bit rot" in no time at all. I think it will make
        the main text cleaner if I use endnotes rather than include the
        URL in-line in the text or as a (distracting) footnote. So when
        the author writes "See my video at &lt;long Youtube URL&gt;" I
        will print "See my video at link 1". At the back of the book, in
        an appendix somewhere, I then use \placenotes to display a table
        of the actual URLs for any readers that want to type them in.
        <br>
        <br>
        I want the "link 1" bit to be normal text rather than
        superscript so it's more visible. Using the
        \setupnote[textstyle=...] command I can change the style of the
        number but not the superscript placing.
        <br>
        <br>
        Is there a way to remove the superscript placing, please?
        <br>
      </blockquote>
      <br>
      \starttext
      <br>
      <br>
      First\footnote{Footnote one}
      <br>
      <br>
      \setupnote[footnote][textcommand=]
      <br>
      <br>
      First\footnote{Footnote two}
      <br>
      <br>
      \stoptext
      <br>
      <br>
      Wolfgang
      <br>
      <br>
    </blockquote>
    <p>You might want to define a separate set of notes, for example,
      linknotes, defined as Wolfgang suggests, so</p>
    <blockquote>
      <p>\setupnote[linknote][textcommand=]</p>
    </blockquote>
    <p>so that they are a separate sequence. These would be used
      exclusively for the url links you describe and regular footnotes
      would continue to be superscript (or however else you choose to
      treat them). You can define multiple streams of footnotes and
      endnotes.</p>
    <p>-- <br>
      Rik<br>
    </p>
  </body>
</html>

--------------fHHc21aV1O8WU5ktGDNSD7Nb--

--===============3919265169050886329==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============3919265169050886329==--