ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bill McClain <wmcclain@salamander.com>
Subject: Re: Emdedding Acrobat Reader fonts (CORRECTION)
Date: Mon, 23 Sep 2002 07:01:35 -0500	[thread overview]
Message-ID: <20020923070135.4c913f7d.wmcclain@salamander.com> (raw)
In-Reply-To: <20020919062450.2dbb1f05.wmcclain@salamander.com>

On Thu, 19 Sep 2002 06:24:50 -0500
Bill McClain <wmcclain@salamander.com> wrote:

> (1) The first field in this line:
> 
>     ec-raw-phvb Arial-BoldMT 4 < phvb8a.pfb ec.enc
> 
> and the second parameter in this line:
> 
>     \definefontsynonym[Helvetica][phvr][encoding=ec]
> 
> must be the same. That is, both should be either "ec-raw-phvb" or
> "phvr". Same for the three other font files.

I wrote the above last week and I now think it is wrong. It is a mistake
I have made before: confusing the context front-end with the pdftex
backend.

In the above, "phvr" does NOT refer to an entry in a map file, but
rather to a .tfm file which is located by tex magic. The .tfm file
contains an internal identifier (viewable with tftopl) which will be
"ec-raw-phvb" and this is what pdftex uses to locate the actual .pfb
font files for embedding.

What I meant to say was that "ec-raw-phvb" ALSO has a .tfm file, so that
it is possible to specify it in the \definefontsynonym declaration, but
that would be an error. It "sort of works" but you lose some
functionality and see strange behavior. 

The reason: phvr.tfm most likely refers to a virtual font file (.vf)
which adds tex magic that we need. Specifying the raw .tfm bypasses the
virtual font.

-Bill
-- 
Sattre Press                                      Pagan Papers
http://sattre-press.com/                    by Kenneth Grahame
info@sattre-press.com              http://pp.sattre-press.com/ 


  reply	other threads:[~2002-09-23 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 10:11 Emdedding Acrobat Reader fonts peter.rolf
2002-09-19 11:24 ` Bill McClain
2002-09-23 12:01   ` Bill McClain [this message]
2002-09-20  9:37 ` Jens-Uwe Morawski

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=20020923070135.4c913f7d.wmcclain@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).