[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with fonts

From: Mats Bengtsson
Subject: Re: Help with fonts
Date: Wed, 08 Oct 2003 14:02:59 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

Robert de Vries wrote:
On Wednesday 08 October 2003 11:16, Mats Bengtsson wrote:

The .map file is probably OK, but the critical thing is that the
feta*.pfa files really belong to your current LilyPond version.

What does
grep CreationDate `kpsewhich feta20.pfa`

%%CreationDate: Mon Sep 29 03:59:26 2003

Seems reasonable for a version 2.0.1 package!

The flag -u tells dvips to use the scalable fonts
*.pfa instead of bitmap fonts *.*pk in the Postscript.
You won't see much of a difference in the .ps file unless you
magnify it but it makes a huge difference in how PDF files
appear on screen.

By the way, could you clarify more exactly what you mean by
"look dreadful".

The notes only have stems, no note heads or flags (or what do you call them in English).

Then, it seems that dvips doesn't find the font file at all.

I noticed you mentioning -u, the lilypond script uses -u

Sorry, just a misprint.

The commandline used to generate ps output looks like this:
dvips  -ta4 -Ppdf -G0 -u Franc_berger.dvi
I cannot find the -G and the -u option in the dvips I have. dvips tells me that it is:
This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (

Maybe I need a higher version of dvips?

That shouldn't be necessary.

It would be interesting to see the lines printed out by dvips.
On my machine, it says something like

This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (
' TeX output 2003.10.07:1249' ->
<><><>. <cmr10.pfb><cmr8.pfb>

where the <feta20.pfa> shows that the font file feta20.pfa is
embedded in the Postscript.

If it's not included in the printouts, you have to find out why dvips
doesn't find the file. It should find using exactly the same library
call as 'kpsewhich feta20.pfa'. You can get lots of debugging
information to help you track down the problem if you run
dvips -d -1 -Ppdf -G0 -u Franc_berger.dvi
and look at the printouts sent to stderr.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]