ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Texfont map file.
Date: Thu, 06 Oct 2005 23:30:57 +0200	[thread overview]
Message-ID: <43459791.6030306@wxs.nl> (raw)
In-Reply-To: <200510061838.33625.john@wexfordpress.com>

John R. Culleton wrote:

>I always believed that when referring to a file in  a \font
>statement one should use the first name found in the appropriate
>line in the map file. This is supposedly the name of the tfm file
>for that particular font. However texfont produces a map file
>like this:  
>
>8r-raw-AGaramond-Italic AGaramond-Italic 4 < AGaramond-Italic.pfb 8r.enc
>8r-raw-AGaramond-Regular AGaramond-Regular 4 < AGaramond-Regular.pfb 8r.enc
>8r-raw-AGaramond-RegularSC AGaramond-RegularSC 4 < AGaramond-RegularSC.pfb 
>8r.enc
>
>...and texfont actually produces two tfm files per font. The
>correct name to use in a \font statement is the second name in
>the generated map file statement, not the first. Since not all
>map file statements have the second parameter this can be
>confusing.  
>
>Since texfont attempts to provide for both pdftex and Context
>users this little gotcha should be referenced in the texfont
>manual. I discovered it by accident. 
>  
>
texfont is doing it right -) 

what you observe is virtual font handling (which involves multiple tfm/vf metric files) 

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2005-10-06 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 18:38 John R. Culleton
2005-10-06 21:30 ` Hans Hagen [this message]
2005-10-06 23:27   ` John R. Culleton

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=43459791.6030306@wxs.nl \
    --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).