ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Culleton <john@wexfordpress.com>
Cc: ntg-context@ntg.nl
Subject: Re: Installing with texfonts.pl
Date: Sun, 22 Sep 2002 09:59:01 -0400	[thread overview]
Message-ID: <200209220959.01406.john@wexfordpress.com> (raw)
In-Reply-To: <20020921154433.5f30ddbf.wmcclain@salamander.com>

On Saturday 21 September 2002 04:44 pm, Bill McClain wrote:
> On Sat, 21 Sep 2002 14:44:37 -0400
>
> John Culleton <john@wexfordpress.com> wrote:
> >  am trying to install a variation of Palatino under anther name.
> >  I copied and renamed the pfa and pfb files. When I pull the
> > renamed file up in pfaedit it says that the encoding is Standard
> > Adobe. Which is what in tex-talk, default, ec, or a player to
> > named later?
>
> Looking at the *.enc files, 8a.enc claims to be Adobe Standard
> Encoding, but several others including the defaul texnansi.enc are
> close.
>
> When using texfont I'm not sure it matters. You new versions will
> be reencoded to whatever spec you want.
>
> I say this one who maintains the right to be ignorant of encodings.
> I've used the default texnansi for my font installs are all has
> worked well.
>
> -Bill
Another test:

I copied the pfm and pfb files for urw palatino to my home directory
and
renamed them uculr8a.pfm and uculr8a.pfb.  I then ran the following
script:

texfont.pl  --fontroot=/usr/TeX/texmf \
--vendor=urw \
--collection=ucul \
--sourcepath=/home/safer \
--install --makepath --show 

It ran to completion with error messages. The resultant test pdf had
errors when loading into Acrobat Reader.

Here is an interesting comment from the log file:

Warning: pdfetex (file /usr/TeX/texmf-var/pdftex/config/pdftex.cfg): 
invalid pa
rameter name in config file: `test.map'

It is interesting because I don't have a file called test.map and
neither of my psfonts.map files refer to test.map.

I don't have a pdftex.map file on my current texmf distro.

I created an empty test.map file and this time I got more output. The
system still couldn't find the file. Here is the message from the log
file:
/
Warning: pdfetex (file texnansi-raw-cul): Font texnansi-raw-cul at 600 
not foun
d

-------------------------------
There were a huge number of messages in the log file about missing
glyphs.
-----------------------------------------------
The resulting pdf file could be read by xpdf but Acrobat Reader found
error messages and would not display it properly.

For this particular test I did not attempt to edit the font file to
change its name internally. I use pfaedit for a font file editor. 
Previous runs with the name change to ucul did not
succeed either. 
------------------------------------------------
Summary:
Here is a font that is known to work.  I only changed its name and
location and tried to install it with texfonts.pl and it would not
install. Where did I go wrong?

John Culleton


  reply	other threads:[~2002-09-22 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 18:44 John Culleton
2002-09-21 20:44 ` Bill McClain
2002-09-22 13:59   ` John Culleton [this message]
2002-09-23 12:03     ` Bill McClain
2002-09-22 20:25   ` Hans Hagen
2002-09-23 14:37     ` John Culleton
2002-09-24  6:36     ` Peter Sojan
2002-09-27  9:06       ` Hans Hagen
2002-09-23 21:19   ` John 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=200209220959.01406.john@wexfordpress.com \
    --to=john@wexfordpress.com \
    --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).