From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] weird \inlinetypebuffer interaction
Date: Mon, 6 May 2024 20:06:30 +0200 [thread overview]
Message-ID: <f0615456-80fa-23a5-b1e0-ecea47b8e564@gmx.es> (raw)
Dear list,
I have the following sample:
\definefontfamily[mainface][tt][TeX Gyre Termes]
\setupbodyfont[mainface]
\starttext
\startbuffer
context --purgeall
\stopbuffer
inline \typeinlinebuffer
block:
\typebuffer
\stoptext
As long as there is no defined font family for mono, \typeinlinebuffer
doesn’t convert -- into an en-dash (the same way as \typebuffer behaves).
But as in the sample above, when a font is defined for mono (at least
with \definefontfamily), \typeinlinebuffer converts -- into en-dashes
(different from \typebuffer).
Sorry, but how could I fix this \typeinlinebuffer?
This is important for me, since two hyphens is one of the most common
ways to marks options when invoking programs (which I try to explain to
others).
BTW, \sciteinlinebuffer seems have the same problem (in the scite module).
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 reply other threads:[~2024-05-06 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 18:06 Pablo Rodriguez via ntg-context [this message]
2024-05-06 20:45 ` [NTG-context] " Wolfgang Schuster
2024-05-07 17:40 ` Pablo Rodriguez via ntg-context
2024-05-07 20:37 ` Wolfgang Schuster
2024-05-08 16:05 ` Pablo Rodriguez via ntg-context
2024-05-09 10:57 ` Wolfgang Schuster
2024-05-09 13:18 ` Pablo Rodriguez via ntg-context
2024-05-14 14:07 ` 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=f0615456-80fa-23a5-b1e0-ecea47b8e564@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).