From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Ligature color is not reliable
Date: Mon, 11 Apr 2016 22:35:49 +0200 [thread overview]
Message-ID: <570C0AA5.2030002@wxs.nl> (raw)
In-Reply-To: <01fe01d19425$3987ffd0$ac97ff70$@tosovsky@email.cz>
On 4/11/2016 9:06 PM, Jan Tosovsky wrote:
> On 2016-04-09 Jan Tosovsky wrote:
>>
>> for an illustration I wanted to colorize all ligatures, but the
>> following method is not reliable for three character ligatures
>> - which ends up black.
>>
>> While tested with Palatino, it can be simulated even with
>> a default font (however there are missing ffi and ffl ligatures).
>>
>> \definefontfamily[palatino][rm][Palatino Linotype]
>> [features={default, quality}]
>> \setupbodyfont[palatino]
>>
>> \starttext
>> Je{\red ff}, the o{\red ffi}ce on the {\red fi}rst {\red fl}oor
>> is o{\red ffl}ine.
>> \stoptext
>>
>> What is happening here?
>>
>
> Any idea how to properly colorize those ligatures?
update
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-04-11 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <003e01d19267$9b0e7dc0$d12b7940$@tosovsky@email.cz>
2016-04-11 19:06 ` Jan Tosovsky
[not found] ` <01fe01d19425$3987ffd0$ac97ff70$@tosovsky@email.cz>
2016-04-11 20:35 ` Hans Hagen [this message]
2016-04-11 20:45 ` Jan Tosovsky
2016-04-09 13:56 Jan Tosovsky
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=570C0AA5.2030002@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).