ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: em-dash ligature is converted to en-dash in the generic fontloader
Date: Sat, 23 Feb 2019 15:55:53 +0100	[thread overview]
Message-ID: <a9bf815c-8153-3e1a-1689-cd01e1bc5fe7@xs4all.nl> (raw)
In-Reply-To: <15b5h3wyahlvy$.dlg@nililand.de>

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.

in context we set:

\automatichyphenmode=1

i'll do the same in luatex-plain

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:[~2019-02-23 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 12:50 Ulrike Fischer
2019-02-23 14:55 ` Hans Hagen [this message]
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
2019-02-28 11:38 Marcel Krüger
2019-03-01 10:17 ` Hans Hagen
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

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=a9bf815c-8153-3e1a-1689-cd01e1bc5fe7@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).