From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/7189 Path: main.gmane.org!not-for-mail From: Bill McClain Newsgroups: gmane.comp.tex.context Subject: Re: more on missing ligatures Date: Sat, 09 Mar 2002 14:38:23 -0600 Sender: owner-ntg-context@let.uu.nl Message-ID: <3C8A72BF.50D70FA7@salamander.com> References: <3C88ED45.72C4F737@salamander.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035397669 17158 80.91.224.250 (23 Oct 2002 18:27:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:27:49 +0000 (UTC) Original-To: "ntg-context@ntg.nl" Xref: main.gmane.org gmane.comp.tex.context:7189 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:7189 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