Graham Percival wrote:
I was hoping that the new fontforge would fix this, but it didn't. This problem first occurred about a week ago -- I'm exactly certain; since then, I've been
opps, see 2.6.0-2 or current cvs. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
