On Friday, 19 June 1998, Jens Glaser writes:
> the following "bugs" :-) ought to be corrected in lilypond (as of 0.1.73)
> (again, without proper documentation it proves extremly hard to understand
> the source code):
Well, if there were more documentation, there would be less source code?
But you're right. We've been working quite hard on the documentation
the last couple of weeks. In fact, we'll mainly be doing documentation
before the 0.2 release (maybe we'll do some bugfixes too :-)
> - the "forte" \f looks strange (too wide); compare that with the \ff,
> which seems okay
It's a feature.
Were trying to mimic a tric that professional engravers seem
to use: slant the the single f a bit more to let it stand-out.
It's just a bit ugly when there's an ff nearby...
See tex/dyndefs.tex
> - multibar rests: it is valid and recommended to use them even in
> (multiple-voice) scores, but only if the rest appears in all voices
> at the same time! E.g., currently "R1*10" produces ten unnecessary
> measures in all voices.
This is a feature: the measures get *expanded* when the Score property
"SkipBars" = 0.
If you don't want this, override the default Score translator in your
paper block, and set SkipBars = "1", see init/part-paper.ly.
> - is it at all possible to put arbitrary text above the staff, e.g.
> a letter ("A","B"..) enclosed in a box or a circle (frequently used in
> orchestra and choir music)
In pl 71, i introduced
\mark "A" or \mark "1"
see input/test/mark.ly
but it's still a bit broken, i'm afraid.
Jan.
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The Music Typesetter
http://www.digicash.com/~jan | http://www.digicash.com/~jan/lilypond
