From: "Rudd, Kevin via ntg-context" <ntg-context@ntg.nl>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Cc: "Rudd, Kevin" <kevin@lps.umd.edu>
Subject: separators between non-instantiantiated (foot)notes
Date: Mon, 3 Apr 2023 21:44:46 +0000 [thread overview]
Message-ID: <1680558286256.15418@lps.umd.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1651 bytes --]
Is there a better (automatic, consistent) way to insert separators between non-instantiated (foot)notes (i.e., where there is at least one \note involved with an immediately preceeding/following \footnote or \note? looking at the source, the obvious hack was apparent but ... not ideal. Maybe I'm missing something obvious, but from what I see:
\starttext
something that works
\footnote[a]{AAAA}
\footnote[b]{BB}
something that doesn't
\footnote[c]{CCCCCC}
\note[b]
something else that doesn't
\footnote[d]{DDDDDDDD}
\unprotect\strc_notes_inject_separator\protect
\note[b]
but can be made to work, but does not adapt to \quotation{normal} \type{\footnote} style/format customizations
\footnote[e]{E E E E}%
\high{\tx{,}}
\note[a]
\stoptext
It would be great if there were a command that treated a (some command like) \note as a \footnote-equivalent command for typesetting purposes but I'm not sure how/where the appropriate template that could produce this command might go. (And I don't know if there are? footnote-state subtleties that I'm missing that would make this kind of thing non-trivial to implement.)'
Many thanks,
-K
Kevin W. Rudd, Ph.D.
CAPT, USN (Ret)
Computing Systems Researcher
Computer Architecture & Computer Engineering (CACE)
Advanced Computing Systems (ACS) Research Program
Laboratory for Physical Sciences (LPS)
kevin@lps.umd.edu
Visiting Research Professor
Electrical and Computer Engineering
United States Naval Academy
rudd@usna.edu
Adjunct Faculty
Secure, Trusted, and Assured Microelectronics (STAM) Center
Arizona State University
kevin.rudd@asu.edu
[-- Attachment #1.2: Type: text/html, Size: 5089 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2023-04-03 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1680558286256.15418@lps.umd.edu \
--to=ntg-context@ntg.nl \
--cc=kevin@lps.umd.edu \
/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).