[EMAIL PROTECTED] writes: > Hi! > > Attached is a patch that should fix some problems of the time signature > engraver. Some problems still survive. I also renamed
ok, added to cvs. > I think these changes are necessary, because the implementation so far was > a rather arbitrary, incomplete collection of time signature symbols. I am > trying to orthogonalize all the different styles and to make combinations > of them possible. This will also require the introduction of new > properties that qualify the style in more detail. Note that I also > started to move program logic to scheme to simplify manipulation of the > logic. OK. Please be careful with adding properties. We already have too many of them, and I'd like them to be as orthogonal as possible. > See input/test/time.ly for comprehensive usage examples. > ok. > > +% IMPORTANT NOTE: The current selection scheme for time signature > +% symbols is not flexible enough for future extensions such as various > +% flavours of early mensural notation or complex signatures as in > +% contemporary music. Therefore, the semantics of time-signature > +% properties will quite definitely change, and maybe the syntax of the > +% \time request will possibly be extended. The following TODOs give > +% two examples what might be expected. -- jr > + > +% TODO: The former "old6/8alt" is currently not addressable. This will > +% be fixed by introducing an additional style property that switches > +% between various mensural diminution styles. -- jr > + > +% TODO: Style "1xxx" really should be a special case of style > +% "numbered". In other words, style "1xxx" should be removed, and a new > +% property "denominator-style" should be introduced, with values > +% "numbered" (which should be equivalent to the current "numbered" > +% style), "none" (which should be equivalent to the current "1xxx" > +% style), and "notehead" (which should place a proper notehead to the > +% right side of the nominator). -- jr > + Nitpick: we currently dump all files to on the webpage as well, so a texidoc would be more appropriate. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen/ _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
