ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: Make footnote/endnote number not superscript?
Date: Sun, 20 Mar 2022 17:18:43 -0400	[thread overview]
Message-ID: <e2640941-e04e-e25b-c71a-f05d76236433@rik.users.panix.com> (raw)
In-Reply-To: <e150decf-554f-cb42-b634-05b2b23e09f2@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]


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

[-- Attachment #1.2: Type: text/html, Size: 2317 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-03-20 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20 20:10 Bruce Horrocks via ntg-context
2022-03-20 20:52 ` jbf via ntg-context
2022-03-20 21:07 ` Wolfgang Schuster via ntg-context
2022-03-20 21:18   ` Rik Kabel via ntg-context [this message]
2022-03-21 18:25     ` Pablo Rodriguez via ntg-context
2022-03-21 23:20       ` Bruce Horrocks via ntg-context

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=e2640941-e04e-e25b-c71a-f05d76236433@rik.users.panix.com \
    --to=ntg-context@ntg.nl \
    --cc=ConTeXt@rik.users.panix.com \
    /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).