ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: no liga with Brill font
Date: Wed, 8 Feb 2012 00:10:40 +0200	[thread overview]
Message-ID: <20120207221040.GA14314@khaled-laptop> (raw)
In-Reply-To: <4F3195B7.6030100@web.de>

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

On Tue, Feb 07, 2012 at 10:20:55PM +0100, Pablo Rodríguez wrote:
> 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).

The font seems to be using contextual substitution instead of regular
ligatures (so the ligature glyphs are not really used, but alternate f’s
and i’s etc. are used instead to give the same effect, quite helpful if
you want to color only part of the ligature), so you may node to set
mode to node:

\definefontfeature[default][default][script=latn,mode=node]

However, your example works here without any modifications (I added
color commands just to showcase the usefulness of this approach).

\usemodule[simplefonts]
\definefontfeature[default][default][script=latn]
\setmainfont[Brill]
\def\r#1{\color[red]{#1}}
\def\b#1{\color[blue]{#1}}
\starttext
\r{f}\b{i} \r{f}\b{l} \b{f}\r{f} \b{f}f\r{i} \r{f}\b{f}\r{l}
\stoptext

Regards,
 Khaled

[-- Attachment #2: b.pdf --]
[-- Type: application/pdf, Size: 5153 bytes --]

[-- Attachment #3: 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:[~2012-02-07 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 21:20 Pablo Rodríguez
2012-02-07 22:10 ` Khaled Hosny [this message]
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=20120207221040.GA14314@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --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).