4th Draft posted. Still to do:
Showing how 'breakbefore' works, as it was evident from recent mails that I need to go back and read the LM to see how to show this in an @lilypond. Also the last third of this patch still needs to be 'done' - we've left this until we get the first parts sorted. Just check the comments - I have done all of them (except breakbefore) but have also take the opportunity to make some more edits to make this section even less wordy. http://codereview.appspot.com/4124056/diff/9001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/4124056/diff/9001/Documentation/notation/input.itely#newcode707 Documentation/notation/input.itely:707: @end example On 2011/02/15 01:28:04, Graham Percival wrote:
I'd rather have a @lilypond.
Although I've now used the new papersize we have defined in the @lilypond option and the paper.scm file, until I better understand the breakbefore option (I need to go back evidently and re-read how it should be used properly), so have for now not done this. http://codereview.appspot.com/4124056/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
