ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <phg@phi-gamma.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [fontloader/old] mixed substitution / ligatures feature
Date: Mon, 21 Dec 2015 06:40:03 +0100	[thread overview]
Message-ID: <20151221054003.GA30245@phlegethon> (raw)
In-Reply-To: <56744404.7010702@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]

···<date: 2015-12-18, Friday>···<from: Hans Hagen>···
> On 12/18/2015 7:34 AM, Philipp Gesang wrote:
> > in the old loader, defining a feature containing mixed ligature /
> > substitution causes a crash. Here’s an example:
> >
> >      \enabletrackers [otf.loading]
> >      \startluacode
> >        fonts.handlers.otf.addfeature ("dunno", {
> >            {
> >                type      = "substitution",
> >                data      = { [0x0022] = 0x201D },
> >                prepend   = true,
> >            },
> >            {
> >                type     = "ligature",
> >                data     = { [0x2013] = {0x002D, 0x002D} },
> >                prepend  = true,
> >            },
> >        })
> >        fonts.handlers.otf.features.register {
> >            name        = "dunno",
> >            description = "bug demo",
> >        }
> >      \stopluacode
> >
> >      \definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node]
> >
> >      \definefont [somefont] [file:cmunrm.otf*myfeat]
> >      \starttext
> >        \somefont foo bar " baz
> >      \stoptext
> >
> > This crashes in font-otn on account of a number being indexed.
> > This used to work -- anything that can be done about it?
> 
> i'll see if i can fix it but don't expect all upcoming features in the 
> new loader to work in the old one

Thanks for fixing the crash. However, the substitution doesn’t
work as defined, even if there’s no ligature. It does work with
the TL 2015 version. As it doesn’t seem work with the new loader
either I guess this is related to the “em-dashes not working …”
issue :)

Best,
Philipp


[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2015-12-21  5:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  6:34 Philipp Gesang
2015-12-18 17:36 ` Hans Hagen
2015-12-21  5:40   ` Philipp Gesang [this message]

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=20151221054003.GA30245@phlegethon \
    --to=phg@phi-gamma.net \
    --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).