From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: (bug?) itlc removes liga
Date: Fri, 28 Jul 2017 19:25:03 +0200 [thread overview]
Message-ID: <8aec51da-f7e7-7aa7-a03a-1a05b7a6ccac@gmx.es> (raw)
Dear list,
using latest beta (2017.07.28 14:24), I have the following sample:
\definefontfeature
[default]
[default]
[script=latn,
itlc=yes]
\setupitaliccorrection
[global, always]
\definefontfamily
[mainfont]
[rm]
[EB Garamond]
\startbuffer[words]
office final floor affliction
\stopbuffer
\startbuffer[ligatures]
{\em \getbuffer[words]}\\
{\bi \getbuffer[words]}\\
{\getbuffer[words]}\\
{\bf \getbuffer[words]}\\
\stopbuffer
\starttext
\startTEXpage[offset=1em]
\getbuffer[ligatures]
\setupbodyfont[pagella]
\getbuffer[ligatures]
\setupbodyfont[mainfont]
\getbuffer[ligatures]
\stopTEXpage
\stoptext
In Latin Modern italics (and TeX Gyre typefaces), the “ffi” ligature
isn’t added.
With EB Garamond, italics don’t get the “ffl” ligature.
The previous beta from 2017.07.27 16:17 doesn’t have the issue that I
describe.
Could anyone be so kind to confirm the bug with latest beta?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2017-07-28 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:25 Pablo Rodriguez [this message]
2017-07-29 13:00 ` Jan U. Hasecke
2017-07-29 15:40 ` Jean-Pierre Delange
2017-07-29 19:51 ` Hans Hagen
2017-07-30 8:33 ` Jan U. Hasecke
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=8aec51da-f7e7-7aa7-a03a-1a05b7a6ccac@gmx.es \
--to=oinos@gmx.es \
--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).