hinterfleisch of natural
[EMAIL PROTECTED] writes: Thanks a lot for fixing the positioning of accidentals! It greatly improves the optical appearance. IMHO there is still a problem with naturals and sharps occurring in a chord at the same time (see attached image): They don't appear vertically aligned; the natural is That's because they are positioned independently. I don't consider this a high priority bug. (I remember that you contributed a better algorithm for accidental positioning... If you feel tempted, go ahead :-) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: hinterfleisch of natural
[EMAIL PROTECTED] writes: Implementing this in the metafont sources should be straightforward. except that MetaFont doesn't have facilities for computing the kerning regions, so the distances would have to be entered by hand. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
hinterfleisch of natural
[Until lilypond-devel works again I will CC all mails to Han-Wen and Janneke. If you know something better please tell me.] [CVS 2004-03-10 9:50 MET] Thanks a lot for fixing the positioning of accidentals! It greatly improves the optical appearance. IMHO there is still a problem with naturals and sharps occurring in a chord at the same time (see attached image): They don't appear vertically aligned; the natural is positioned too near to the note head. Werner PS: The problems with fontforge have been resolved. Since today, fontforge produces valid PFAs again for lilypond fonts. inline: acc.png___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
