Re: lilypond.csh

[Han-Wen Nienhuys]

address@hidden writes:
> > > You could add font directories for lilypond, but please don't "add all
> > > available TeX Type1 fonts".
> 
> The basic problem is that the direct PS output of Lilypond
> doesn't embed any fonts, which means that we have to provide
> the search path not only to the Lilypond fonts but also to 
> the ordinary text fonts. We should check if it's easy to 
> add a more selective list. Another option would be to comment
> out the line by default and describe in the documentation how
> how to uncomment it, for the Kamikaze users who want to try
> lilypond -fps. (A third alternative would be to use the 
> predefined PS fonts instead of CMR by default.)

I think we should scrap the standard support for -f ps. Kamikaze users
get what they deserve :-) . Using PS fonts is a swell idea, but then
we should also implement that for the TeX backend.

(A more advanced trick would be to define fontpaths in the PS output
itself, but not load the fonts. I'm not sure how feasible this is, though.)

-- 

Han-Wen Nienhuys   |   address@hidden   |   http://www.cs.uu.nl/~hanwen