From: Rik Kabel <context@rik.users.panix.com>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Issue with ligatures before dashes
Date: Tue, 30 Oct 2018 12:32:29 -0400 [thread overview]
Message-ID: <8928b6cb-2676-5429-5af7-129298f0af6f@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1872 bytes --]
This was reported on the LuaLatex list yesterday, and I extended the
example to include ConTeXt compounds. From my test folder:
%% No ligatures before dashes! Reported as: “ligatures before
%% dashes not working with LuaLaTeX 1.07.0” on comp.tex.luatex,
%% 2018-10-29 by Toni Dietze. This is also a problem with ConTeXt,
%% and is a problem with compounds as well. The problem is worse
%% with 1.09.0: With 1.07.0 (6686) it fails with the bare hyphen
%% but had no problem with en-dash, em-dash, and the compounds
%% shown below. With luatex 1.09.0 (6930) it fails with bare
%% hyphen and all shown compounds except |=|.
\starttext
\setupTABLE[c][1,3][align=left]
\setupTABLE[c][2,4][loffset=1em,roffset=1em]
\setupTABLE[r][each][offset=0pt]
\bTABLE[frame=off]
\bTABLEhead
\bTR[align=center,bottomframe=on]
\bTH[nc=2] Non-compound\eTH
\bTH[nc=2] Compound\eTH
\eTR
\eTABLEhead
\bTABLEbody
\bTR
\bTD - \eTD \bTD off-course\eTD
\bTD \|-\| \eTD \bTD off|-|course\eTD
\eTR
\bTR
\bTD – \eTD \bTD off–course\eTD
\bTD \|–\| \eTD \bTD off|–|course\eTD
\eTR
\bTR
\bTD — \eTD \bTD off—course\eTD
\bTD \|—\| \eTD \bTD off|—|course\eTD
\eTR
\bTR
\bTD \eTD \bTD \eTD
\bTD \|_\| \eTD \bTD off|_|course\eTD
\eTR
\bTR
\bTD \eTD \bTD \eTD
\bTD \|=\| \eTD \bTD off|=|course\eTD
\eTR
\eTABLEbody
\eTABLE
\stoptext
In one 300-page book, this hits a few times (off-course,
oft-repeated,...). Not the worst problem, but clearly a regression.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 1938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2018-10-30 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 16:32 Rik Kabel [this message]
2018-10-30 17:34 ` Wolfgang Schuster
2018-10-30 17:58 ` Hans Hagen
2018-10-30 19:34 ` Rik Kabel
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=8928b6cb-2676-5429-5af7-129298f0af6f@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).