[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond can't find its fonts
From: |
Matthias Neeracher |
Subject: |
Re: Lilypond can't find its fonts |
Date: |
Sun, 1 Aug 2004 15:08:29 -0700 |
In article <address@hidden>,
Benjamin Esham <address@hidden> wrote:
> (This is being cross-posted to both lilypond-user and fink-users.
> Please reply to only one of these lists.)
Actually, I believe it has some relevance to both.
> I'm using LilyPond 2.3.8 (package lilypond-unstable 2.3.8-1) with fink
> 0.20.6 and the latest package descriptions,
The latest package descriptions, as of yesterday, are 2.3.9-2, but this
should have no bearing on your issues.
> | paper output to `newworld.ps'...
> | warning: lily-guile: Can't find PFA font "ecbx10"
> | warning: lily-guile: Can't find PFA font "ecbx12"
> | warning: lily-guile: Can't find PFA font "eccc10"
> | warning: lily-guile: Can't find PFA font "ecrm10"
> | warning: lily-guile: Can't find PFA font "ecti7"
Hmm. All of these are in ec-fonts-mftraced. Can you make sure that your
version of this is up-to-date and installed?
> The next oddity is the kerning of the fonts in the PDF output. All of
> the text in the header, as well as textual dynamic markings, is
squished
> together and is mostly unreadable. Oddly, a space character still
seems
> to produce the same amount of white space; it's just the letters
within
> a word that are compacted together.
>
> I think one or more of fink's TeX-related packages may be at fault for
> this next part (and hence the cross-posting). The PDF is only
squished
> like this when the PostScript output is run through ps2pdf (either
> automatically by Lily or manually). If I open the PostScript file in
> Preview (and the system converts it to PDF), the letter spacing is
> normal.
I've noticed this recently myself, and this is where fink-users and
Jeffrey Whitaker come in: It seems that the ps2pdf in the ghostscript
(8.x) package exhibits this bug, but not the one in ghostscript6. I had
allowed both as alternatives because I thought they were equivalent,
but it seems they are not. Is this a known issue, and is there a known
fix?
> I then tried to install lilypond-unstable-2.3.9-2, and when I tried to
> process a file I got this:
>
> | parts.ly:1:23: error: parse error, expecting `DOUBLE_ANGLE_OPEN' or
> | `SEQUENTIAL' or `SIMULTANEOUS' or `'{'':
> | brass = \notes \relativ
> | e c' {
>
> I assumed that this was just a change in syntax causing problems,
Yes, you'll need to run convert-ly
> but there was also this line at the end:
>
> | Interpreting music... error: can't find `feta20.afm'
> | Music font has not been installed properly. Aborting
That file should be in:
/sw/share/lilypond/2.3.9/fonts/afm/feta20.afm
but combined with your first problem above, it looks to me like some
TeX related environment variables may have been scrambled. Could it be
that your shell is not running /sw/bin/init.{sh,csh} properly?
Matthias