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] issue with \xmlinlineprettyprinttext
Date: Wed, 20 Mar 2024 19:52:09 +0100 [thread overview]
Message-ID: <ef949201-bc37-2e96-28bb-f4cf32d65b58@gmx.es> (raw)
Dear list,
I have the following sample:
\startbuffer[demo]
<doc>
<code>a --b c</code>
<inlinecode>a --b c</inlinecode>
</doc>
\stopbuffer
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{doc|code|inlinecode}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:code
\xmlprettyprinttext{#1}{none}
\stopxmlsetups
\startxmlsetups xml:inlinecode
\xmlinlineprettyprinttext{#1}{none}
\stopxmlsetups
\definefontfamily[mainface][tt][TeX Gyre Cursor]
[features={default, quality}]
\setupbodyfont[mainface]
\starttext
\xmlprocessbuffer{main}{demo}{}
\type{a --b c}
\stoptext
Using current latest (from 2024.03.11 09:34), LMTX transforms "--" in
"–" (en-dash) only with \xmlinlineprettyprinttext (LuaTeX writes the
en-dash in the three cases).
This issue has been driving me crazy, since it took me a while what was
different here.
Is there something I can do to get \xmlinlineprettyprinttext as
\xmlprettyprinttext in this point?
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
___________________________________________________________________________________
reply other threads:[~2024-03-20 18:54 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=ef949201-bc37-2e96-28bb-f4cf32d65b58@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).