From: Hans Hagen <j.hagen@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Marcel Krüger" <tex@2krueger.de>
Subject: Re: em-dash ligature is converted to en-dash in the generic fontloader
Date: Fri, 1 Mar 2019 11:17:56 +0100 [thread overview]
Message-ID: <fb9ad6ed-5a0b-77e0-6268-9a871da743a4@xs4all.nl> (raw)
In-Reply-To: <16933e6728e.123a80716120657.793480406127173845@2krueger.de>
On 2/28/2019 12:38 PM, Marcel Krüger wrote:
> On 2/23/2019 1:50 PM, Ulrike Fischer wrote:
>> As reported on the dev-luatex list --- is converted to an en-dash
>> (instead of em-dash) if there are no spaces around the ---.
>>
>> We could now reproduce the problem also with the generic fontloader:
>> it appears only with mode=node. I'm using the files from 2019-02-14,
>> but the problem appeared first in the files from 2018-11-18):
>>
>> \font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test
>>
>> dashes-these % gives dash
>>
>> dashes--these % gives en-dash
>>
>> dashes---these % gives en-dash WRONG
>>
>> dashes --- these % gives em-dash
>>
>> em-dashes---these % gives em-dash
>>
>> \bye
>>
>> context is not affected, there the code works fine.
>
> This issue can be fixed in the fontloader with the attached patch.
Hm, I don't see those lines here and it looks ok in context so ... no
patches applied (and definitely not in the tex live code freeze window)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-03-01 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 11:38 Marcel Krüger
2019-03-01 10:17 ` Hans Hagen [this message]
2019-03-01 11:29 ` Marcel Krüger
2019-03-01 12:09 ` Hans Hagen
2019-03-01 12:15 ` Ulrike Fischer
2019-03-01 13:49 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 12:50 Ulrike Fischer
2019-02-23 14:55 ` Hans Hagen
2019-02-23 15:30 ` Ulrike Fischer
2019-02-23 16:11 ` Hans Hagen
2019-02-25 14:55 ` Ulrike Fischer
2019-02-25 20:45 ` Henri Menke
2019-02-26 1:14 ` Rik Kabel
2019-02-25 20:46 ` Henri Menke
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=fb9ad6ed-5a0b-77e0-6268-9a871da743a4@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=tex@2krueger.de \
/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).