From: Bill McClain <wmcclain@salamander.com>
Subject: Re: more on missing ligatures
Date: Sat, 09 Mar 2002 14:38:23 -0600 [thread overview]
Message-ID: <3C8A72BF.50D70FA7@salamander.com> (raw)
In-Reply-To: <3C88ED45.72C4F737@salamander.com>
Bill McClain wrote:
>
> I'm back to investigating why Context is not displaying ligatures from
> my new Adobe Sabon font. I've discovered something else which may be a
> clue: Context and plain pdftex differ in the glyphs they generate from
> the same font file. I presume this is caused by some improper definition
> at my end, but I don't know how to diagnose it.
More info: the map file which texfont produces references the newly
created tfm files. However, it looks to me as if there is no ligature
information in those files. The virtual font files do have ligature
info, and when I change my font declarations to use the vf files (for
example, "texnansi-sar" instead of "texnansi-raw-sar"), then Context
produces the ligatures properly.
I'm not sure how that can be, because "texnansi-sar" is not even listed
in the map file.
Is there some automatic linkage between the tfm and vf files which I am
missing? Or should the map file reference the vf files directly?
-Bill
next prev parent reply other threads:[~2002-03-09 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 16:56 Bill McClain
2002-03-09 20:38 ` Bill McClain [this message]
2002-03-11 0:34 ` Hans Hagen
2002-03-11 13:29 ` Bill McClain
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=3C8A72BF.50D70FA7@salamander.com \
--to=wmcclain@salamander.com \
/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).