From: Stef Schoonderwoerd <saschoonderwoerd@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: non-unicode glyphs in ttf fonts
Date: Tue, 21 Jun 2011 13:34:15 +0200 [thread overview]
Message-ID: <BANLkTinpEgBF0-20WPvRJEyaawsWxMiYDw@mail.gmail.com> (raw)
In-Reply-To: <4E007E50.2040307@wxs.nl>
Yes, I guess it is a naming error, though I got the names from Fontlab
Studio.. When I opened the font in fontforge instead and got the names
from there everything just worked.
Thanks!
On Tue, Jun 21, 2011 at 1:19 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 21-6-2011 12:16, Stef Schoonderwoerd wrote:
>>
>> I made a minimal testing file for this case, and tested again. For
>> Palatino Linotype it seems that most (all?) ligatures in fact do not
>> work, but I don't get why..
>> Included are all the files I used for testing.
>
> as there is no f_b you get an error
>
> sub f b by f_b.liga ;
>
> works for me
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________
prev parent reply other threads:[~2011-06-21 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 8:03 Stef Schoonderwoerd
2011-06-21 8:15 ` Hans Hagen
[not found] ` <BANLkTikvrRZYVaA+8D3VNt8vfytiUAMKpQ@mail.gmail.com>
2011-06-21 11:19 ` Hans Hagen
2011-06-21 11:34 ` Stef Schoonderwoerd [this message]
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=BANLkTinpEgBF0-20WPvRJEyaawsWxMiYDw@mail.gmail.com \
--to=saschoonderwoerd@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).