From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Small caps problem/bug with some fonts
Date: Fri, 18 Sep 2009 20:42:48 +0200 [thread overview]
Message-ID: <4AB3D4A8.1020809@wxs.nl> (raw)
In-Reply-To: <20090918181528.GA28412@crud.chemoelectric.org>
Barry Schwartz wrote:
> Hans Hagen <pragma@wxs.nl> skribis:
>> could it be a bug in the font? i.e. a Th ligature showing up in
>> smallcaps? if so, then simplefonts should disable ligatures in smallcaps
>
> I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
> for small caps well above the lookup for ligatures. The software must
> be reading the lookup table out of order.
no, it's just that basemode gets two features and replacement and
ligatures are both applied due to the definition of the smallcaps
featureset, so it's expected behaviour
- either adapt the definition of the smallcaps featureset (i'll do that
in the next beta)
- or switch to nodemode (in your case nodemode applies smallcaps before
ligatures)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-09-18 18:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 12:57 Mika Ritola
2009-09-18 13:14 ` Hans Hagen
2009-09-18 17:35 ` Derek CORDEIRO
2009-09-18 17:54 ` Hans Hagen
2009-09-18 18:54 ` Derek CORDEIRO
2009-09-18 20:32 ` Barry Schwartz
2009-09-18 21:40 ` Hans Hagen
2009-09-18 22:05 ` Barry Schwartz
2009-09-19 16:32 ` Hans Hagen
2009-09-18 17:57 ` Hans Hagen
2009-09-18 20:35 ` Wolfgang Schuster
2009-09-18 18:01 ` Hans Hagen
2009-09-18 18:58 ` Derek CORDEIRO
2009-09-18 18:15 ` Barry Schwartz
2009-09-18 18:42 ` Hans Hagen [this message]
2009-09-18 20:19 ` Barry Schwartz
2009-09-18 21:39 ` Hans Hagen
2009-09-18 22:38 ` Barry Schwartz
2009-09-19 16:52 ` Hans Hagen
2009-09-22 4:15 ` Barry Schwartz
2009-09-22 7:18 ` 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=4AB3D4A8.1020809@wxs.nl \
--to=pragma@wxs.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).