From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: different type in footnote
Date: Fri, 4 Oct 2024 18:44:26 +0200 [thread overview]
Message-ID: <d1bc2b4a-0872-4e8f-9d51-6624e6b8617e@gmx.es> (raw)
In-Reply-To: <6ff590da-959d-0973-739d-ec2acfc16267@gmail.com>
On 10/4/24 18:06, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 04.10.2024 um 17:28:
>> [...]
>> \type{\a.bc}\footnote{\type{\a.bc}}
>
> \type{\a.bc}\footnote{\type[compact=absolute]{\a.bc}}
Many thanks for your help, Wolfgang.
I wonder why I have just discovered it.
Given this sample:
\setuppapersize[A9]
\starttext
\setuptype[compact=all]
\footnote{\type{\a.b c} \type{\a .b c}}
\setuptype[compact=absolute]
\footnote{\type{\a.b c} \type{\a .b c}}
\stoptext
There seems not to be a way to disable space compacting (or showing
spaces as they were typed). What is the rationale behind this?
I mean, this is verbatim and in some cases it is essential to be able to
display spaces as they are in the source.
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-10-04 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 15:28 [NTG-context] " Pablo Rodriguez via ntg-context
2024-10-04 16:03 ` [NTG-context] " Rik Kabel
2024-10-04 16:06 ` Wolfgang Schuster
2024-10-04 16:44 ` Pablo Rodriguez via ntg-context [this message]
2024-10-04 17:01 ` Wolfgang Schuster
2024-10-05 9:38 ` Pablo Rodriguez via ntg-context
2024-10-04 21:55 ` Aditya Mahajan
2024-10-05 9:44 ` Pablo Rodriguez 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=d1bc2b4a-0872-4e8f-9d51-6624e6b8617e@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).