From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: no liga with Brill font
Date: Tue, 07 Feb 2012 22:20:55 +0100 [thread overview]
Message-ID: <4F3195B7.6030100@web.de> (raw)
Hi there,
there is a zero-cost font (not available for commercial works without
previous permission) from Brill (http://www.brill.nl/news/brill-typeface).
Standard ligatures such as fi and fl don't work:
\usemodule[simplefonts]
\definefontfeature[default][default][script=latn]
\setmainfont[Brill]
\starttext
fi fl ff ffi ffl
\stoptext
The glyphs are defined (ff, fi, fl, ffi, ffl), but when I test ligatures with
FontForge (Ctrl+K) these glyphs aren't used and single substitution
lookups in different subtables are performed for the different ligatures
(actually no ligatures are used).
Sorry, my explanation isn't as accurate as it should. I'm not a font
expert, but Substitutions can be browsed in FontForge selecting the
glyph info (Ctrl+I).
Is there something to report to the font designer or is there something
not yet implemented in ConTeXt?
Thanks for your help,
Pablo
--
http://www.oudeis.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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2012-02-07 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 21:20 Pablo Rodríguez [this message]
2012-02-07 22:10 ` Khaled Hosny
2012-02-07 22:41 ` Pablo Rodríguez
2012-02-07 23:19 ` Khaled Hosny
2012-02-08 20:12 ` Pablo Rodríguez
2012-02-08 9:16 ` 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=4F3195B7.6030100@web.de \
--to=oinos@web.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).