Re: lilypond 1.5.60

[Laura Conrad]

>>>>> "Han-Wen" == Han-Wen  <address@hidden> writes:

    Han-Wen> 1.5.60 fixes  the last issues that I consider real things that hold
    Han-Wen>     back the 1.6 release. After this, we'll give the manual another
    Han-Wen>     round of editing, and then hopefully, we can release 1.6

I have to go back to 1.4 if style baroque doesn't get fixed.  I looked
at fixing it, and I don't understand enough about grobs and molecules
to do it.  I don't want to clutter up my lilypond with font changing
commands every time I need a note longer than a whole note.
Especially if they're going to have to be removed soon, anyway.

I also looked at changing abc2ly and convert-ly to clutter up the
lilypond for me, and there isn't a nice clean way to do it.  If we're
really going to break  baroque style, convert-ly has to know how to fix
it, though.

I haven't gotten around to looking at it, but is it really impossible
to put a neo-mensural longa, breve, and ideally maxima notehead into
the standard font?  That seems like the cleanest thing to do to me.
The fact that longa and  maxima don't print unless you
specify baroque style always seemed like a bug to me, anyway.

I've been doing a lot of performing, and putting the publishing on
hold until that's over, but the last performance is this afternoon,
and there's a lot of music that has to get printed by Tuesday.  So on
Monday morning, I need a working publishing system that knows how to print
longas and breves.  I don't want to roll back the 1.5 changes in my
scripts and figure out how to clean up the fonts, and go back to 1.4,
but I'd rather do that than have my group members not have all the
printed notes in front of them.

-- 
Laura (mailto:address@hidden , http://www.laymusic.org/ )
(617) 661-8097  fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139