From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: next upload
Date: Wed, 21 Apr 2021 11:12:36 +0200 [thread overview]
Message-ID: <5800ec23-2d90-4cf4-c2bf-712216da08c1@xs4all.nl> (raw)
Hi,
The *next* upload will have the following change.
For a long time in mkiv and also lmtx, the tex habit of turning -- and
--- into endash and emdash has been handled at the font level by a
injecting a font feature. This works okay.
This tlig feature is currently part of the defaults but that will
change. If you want to retain that, you can add this to a cont-loc.mkxl
file
\definefontfeature
[default]
[default]
[tlig=yes,
trep=yes]
but it should not be needed (and only introduces overhead). When it's a
font feature it kicks in after hyphenation but because we're in the
process of enhancing that, this traditional -- and --- replacement now
kicks in before hyphenation.
It can be disabled by \nohyphencollapsing, which actually happens in for
instance verbatim and it can be applied locally if needed. There might
be places where you expect this to happen so let me know if I missed
these. The (intended) effect is that
somefirst- and secondpart\blank
firstpart\char"002D secondpart\blank
firstpart---secondpart\blank
firstpart\char"002D\char"002D secondpart\blank
firstpart\char"002D\char"002D\char"002D secondpart\blank
firstpart\char"2010 secondpart\blank
firstpart\char"2013 secondpart\blank
firstpart\char"2014 secondpart
\type{firstpart---secondpart}
all work as I expect (both words get hyphenated).
The trep feature was already stripped to only ' replacment but in these
unicode times that artifact has no place. We anyway expect users to use
\quote and \quotation as it's a language dependent feature. You can of
course enable it any time, but it will no longer be default, just like "
already gives an upright double quote, and `` was never enabled in mkiv,
from now on ' will give a single upright quote.
So, when this is uploaded, keep an eye on it and let me know where
things misbehave, you're warned,
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2021-04-21 9:12 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=5800ec23-2d90-4cf4-c2bf-712216da08c1@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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).