Re: Viewing direct PS output?

[Mats Bengtsson]

> address@hidden writes:
> > Am I the only one who fail to view the output of
> > 'lilypond -fps' now that we have Type1 .pfa files
> > instead of the old Type3 ones? 
> 
> install the latest PKtrace -- older versions insert a TeX- prefix
> into the font name, confusing ghostscript. You can also edit the .ps
> changing /feta to /TeX-feta 

Of course, I should have realized. If you changed the naming
strategy in PKtrace, we have to make the corresponding change
also when generating the lilypond.map file. Wasn't there a 
reason that they used the TeX-* naming convention in textrace?

There's another font naming problem in the generated .ps files
namely the CMR fonts used in text scripts, bar numbers and so on.
First of all, I had to add also .../texmf/fonts/type1/bluesky to 
GS_FONTPATH. Secondly, the Bluesky fonts use capital letters
for the font names, so the .ps file should call for CMR10, 
CMTI8 and so on. 

Even when I managed to set all the paths and font names correctly, 
the result looks grotesque since the font scaling completely wrong,
see the attached example. Have I done something else wrong or ...?

   /Mats

clefs.pdf
Description: clefs.pdf