I'd rather drop the first two examples illustrating the problem. It is stated clearly enough, and bad examples shouldn't appear in the docs. Otherwise it looks OK to me.
Trevor http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely File Documentation/notation/rhythms.itely (right): http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely#newcode2089 Documentation/notation/rhythms.itely:2089: @code{Score} context. This means that a setting the time signature that setting (no "a") http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely#newcode2092 Documentation/notation/rhythms.itely:2092: beaming for 3/4 time, because the time signature setting in the Thus, in the following example, standard 3/4 beaming will be used in both staves, because ... http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely#newcode2129 Documentation/notation/rhythms.itely:2129: To avoid this problem, the time signature can be set in only one should be set http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely#newcode2147 Documentation/notation/rhythms.itely:2147: changed, so that when the time signature is set the desired whenever http://codereview.appspot.com/4160048/diff/1/Documentation/notation/rhythms.itely#newcode2158 Documentation/notation/rhythms.itely:2158: #'() % beamExceptions tabs http://codereview.appspot.com/4160048/ _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
