From: Hans Hagen <pragma@wxs.nl>
Cc: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: more on missing ligatures
Date: Mon, 11 Mar 2002 01:34:45 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020311012551.02bcecb0@server-1> (raw)
In-Reply-To: <3C8A72BF.50D70FA7@salamander.com>
At 02:38 PM 3/9/2002 -0600, Bill McClain wrote:
>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?
If you use virtual fonts, as far as i know, tex itself uses the font:
somefont.tfm
which is accompanied by a virtual companion
somefont.vf
which can construct glyphs from multiple font files, in our case at least
it uses the raw file, which is
somefont-raw.tfm
Now, tex itself only needs the tfm file but dvips and the pdftex backend
need the vf file in order to construct composed or manipulated glyphs. So,
when vf was introduced, tex was not adapted, but dvips was,
I must admit that this model is not that clear -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-ade.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-03-11 0:34 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
2002-03-11 0:34 ` Hans Hagen [this message]
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=5.1.0.14.1.20020311012551.02bcecb0@server-1 \
--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).