On 10/3/2021 1:34 AM, Bruce Horrocks via ntg-context wrote:
On 2 Oct 2021, at 00:46, Hans Hagen <j.ha...@xs4all.nl> wrote:

On 10/2/2021 12:35 AM, Bruce Horrocks via ntg-context wrote:
On 21 Sep 2021, at 02:47, Bruce Horrocks via ntg-context <ntg-context@ntg.nl> 
wrote:

I'm using a TTF file that has no ligature capability as a built-in feature. It 
does however have glyphs for fi and fl but ConTeXt isn't substituting them.

So the question is: what do I need to do to persuade ConTeXt to do fi & fl 
ligature substitution?
Any suggestions please? Is a font features file the 'right' way? I would have 
thought that there was a more traditional solution
you can write your own feature (examplex in test suite and manuals) where you 
map f + f onto ff

Thanks Hans - I keep forgetting about the test suite.

For the benefit of those coming here via the mail archive, I found what I 
needed in the cont-tst.zip test suite in the file fonts/extensions-001.tex
<http://www.pragma-ade.com/context/latest/cont-tst.zip>

Now my problem is that the font only has ligatures for fi and fl which is making my 
life di-ffi-cult. <groan>
Then forget abnout the ligatures ... these two were probably only added because of 'habbit'. Most people won't notice.

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to