Re: lily 1.4.3

[Mats Bengtsson]

> > and I had to correct the two include paths on the next line to point
> > where the fonts and .ps files really are.
> 
> Hmm, that's hairy.  Could you try to undo that change again, and then
> try to fix it by setting environment variables, eg:
> 
>     export GS_LIB='c:\cygwin\usr\ ... '
>     export GS_FONTPATH='c:\ ... '
> 
> (please fill in the dots)  That way, it could be automated.
> The script /etc/profile.d/zlily-profile.sh makes an attempt at
> pointing these variable to the LilyPond tree...

The question is if it was the paths to the Lilypond fonts or 
to the standard fonts and .ps files of ghostscript. As long 
as you generate postscript files from Lilypond using 'ly2dvi -p'
or ly2dvi+dvips, there should be no need to set any extra paths, 
right?

> > Now...I have to figure out what I need to do to make my old .ly's work.
> > Maybe Convert-ly is up to this...

convert-ly -e file.ly should do the job. In some earlier version of
the Windows installation, it didn't work unless the file resided in
the working directory, but that's hopefully fixed by now.
Add the flag '--assume-old' if yo didn't insert \version statements
in your .ly file before.

      /Mats