ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: activating font specific ligatures
Date: Thu, 01 Oct 2009 14:22:38 +0200	[thread overview]
Message-ID: <4AC49F0E.5060407@gmx.net> (raw)
In-Reply-To: <20091001113244.GB13582@phare.normalesup.org>


[-- Attachment #1.1: Type: text/plain, Size: 1672 bytes --]

Arthur Reutenauer schrieb:
>> Most ligature work with this setting, but
>>
>> ch ck ct ij IJ sp ss st
>>     
>
>   Those ligatures are usually not part of the liga feature that only activates
> the most common f-ligatures; try dlig (discretionary ligatures), or maybe hlig
> (historical ligatures), although it's more probably the former.
>
>   
>> Is there a way to manually select the ligatures of a font?
>>     
>
>   You can use a feature file to define your own OpenType features that would
> only activates the ligatures of your choice and associate it with a name, say
> plig for "Peter's ligatures" (rlig is already used for "required ligatures" in
> scripts like Arabic, better not to overwrite it).  See
> fonts/fea/context/texhistoric.fea in the ConTeXt distribution for how it's done
> for tlig (which is not a standard OpenType feature either).  Send it to Hans
> when you're over, so that he can use it too because he's been traumatised by
> the st and ct ligatures :-)
>
>   
:))

will do so

I have found the 'dlig'-feature in the font, but activating this feature 
doesn't work here.

Thanks Arthur and Thomas!

Best wishes,  Peter

> 	Arthur
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
>   


[-- Attachment #1.2: Type: text/html, Size: 2784 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-10-01 12:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 11:17 Peter Rolf
2009-10-01 11:32 ` Thomas A. Schmitz
2009-10-01 11:34   ` Arthur Reutenauer
2009-10-01 11:37     ` Thomas A. Schmitz
2009-10-01 11:32 ` Arthur Reutenauer
2009-10-01 12:22   ` Peter Rolf [this message]
2009-10-01 12:33     ` Thomas A. Schmitz
2009-10-01 12:54       ` Peter Rolf
2009-10-01 13:14         ` Thomas A. Schmitz
2009-10-01 17:49   ` Hans Hagen
2009-10-01 19:32     ` Peter Rolf

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=4AC49F0E.5060407@gmx.net \
    --to=indiego@gmx.net \
    --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).