ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Marcel Krüger" <tex@2krueger.de>
To: "ntg-context" <ntg-context@ntg.nl>
Subject: em-dash ligature is converted to en-dash in the generic fontloader
Date: Thu, 28 Feb 2019 12:38:54 +0100	[thread overview]
Message-ID: <16933e6728e.123a80716120657.793480406127173845@2krueger.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

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.

Best regards,
Marcel Krüger

[-- Attachment #2: 0001-Fix-ligature-followed-by-disc.diff --]
[-- Type: application/octet-stream, Size: 653 bytes --]

diff --git a/tex/context/base/mkiv/font-ots.lua b/tex/context/base/mkiv/font-ots-fixed.lua
index 563094f..b1068f7 100644
--- a/tex/context/base/mkiv/font-ots.lua
+++ b/tex/context/base/mkiv/font-ots-fixed.lua
@@ -841,7 +841,7 @@ function handlers.gsub_ligature(head,start,dataset,sequence,ligature,rlmode,skip
                 local prev   = getprev(start)
                 if stop then
                     setnext(stop)
-                    local tail = getprev(stop)
+                    local tail = stop
                     local copy = copy_node_list(start)
                     local liat = find_node_tail(copy)
                     if pre then

[-- Attachment #3: Type: text/plain, Size: 493 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
___________________________________________________________________________________

             reply	other threads:[~2019-02-28 11:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 11:38 Marcel Krüger [this message]
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
  -- 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=16933e6728e.123a80716120657.793480406127173845@2krueger.de \
    --to=tex@2krueger.de \
    --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).