From: Andreas Ulbrich <andreas.ulbrich@gmx.net>
Subject: Re: another example of fonts (pk files not found)
Date: Sun, 27 Jan 2002 02:00:07 +0100 [thread overview]
Message-ID: <3C535117.2020403@gmx.net> (raw)
Hi,
I know that the font situation has been explained quite often and I have
also read the according manuals, but I didn't manage to install a font
properly. Hopefully some of came along the same problem and can offer a
quick solution.
At first I thought the problem arise from the fact that I use a font
converted from TTF. But I tried the procedure with an arbitrary Type1
font (Bitstream Charter ripped out of ghostscript) with the same result.
I installed the fonts with the following command
texfont --vendor=bitstream --collection=charter --make --install
This runs as expected. Then I instruct MikTeX to refresh its file
databases because texfont failes to do so (usage message is printed).
When trying to run texexec over the generated sample file context spits
out following messages:
Warning: pdfetex (file texnansi-raw-bchri): Font texnansi-raw-bchri at
600 not found
name: texnansi-raw-bchr, dpi=600, bdpi=600, mag=magstep(0.0)
makemf --verbose texnansi-raw-bchr
cannot find texnansi-raw-bchr source file.
ttf2pk -q -n texnansi-raw-bchr 600
hbf2gf -q -p texnansi-raw-bchr 600
Consulting F:\texmf\miktex\config\config.makepk...
Consulting F:\texmf\dvips\config\config.ps...
makepk: don't know how to make texnansi-raw-bchr.pk!
And the .log contains such lines:
Warning: pdfetex (file texnansi-raw-bchri): Font texnansi-raw-bchbi at
600 not found
So obviously pdfetex cannot build .pk files. As far as I (I'm a
(context|latex) user only, never really cared how it works behind the
scenes) understand these are rasterised versions of the font.
My questions are:
1. Why does pdfetex need rasterised font. I thought it uses vector fonts
only?
2. How can I get this working?
Ah yes: MikTex 2.6, latest context beta, Windows XP
Many thanks,
Andreas
next reply other threads:[~2002-01-27 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 1:00 Andreas Ulbrich [this message]
2002-01-27 14:13 ` Bill McClain
2002-01-28 11:07 ` Hans Hagen
2002-01-27 18:37 ` Hans Hagen
[not found] <200202010047.BAA22628@smail.let.uu.nl>
2002-02-01 9:05 ` Hans Hagen
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=3C535117.2020403@gmx.net \
--to=andreas.ulbrich@gmx.net \
/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).