From: Graham Percival Date: Wed, 8 Feb 2006 18:53:23 +0000 (+0000) Subject: Clarifications. X-Git-Tag: release/2.7.34~28 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=dcd8203180c35f6d4b6cc96e0ee2abb08f690e11;p=lilypond.git Clarifications. --- diff --git a/ChangeLog b/ChangeLog index 3d8c777ba3..754226876d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -4,6 +4,8 @@ * Documentation/user/basic-notation.itely: add stem-neutral example. + * Documentation/user/putting.itely: clarifications. + 2006-02-08 Han-Wen Nienhuys * Documentation/topdocs/NEWS.tely (Top): remove internal cleanup diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely index c95dff598d..c0fa477a43 100644 --- a/Documentation/user/putting.itely +++ b/Documentation/user/putting.itely @@ -47,7 +47,7 @@ it quicker. How often is ``every so often''? It depends on the complexity of the music. For very simple music, perhaps just once or twice. For very complex music, every bar. -@item One bar per line. If there is anything complicated, either in the music +@item One bar per line of text. If there is anything complicated, either in the music itself or in the output you desire, it's often good to write only one bar per line. Saving screen space by cramming eight bars per line just isn't worth it if you have to `debug' your files. @@ -65,12 +65,13 @@ in the number of @code{@{} and @code{@}}. @end itemize If you are entering music from an existing score (ie typesetting a -piece of public domain music), +piece of existing sheet music), @itemize @bullet -@item Enter one manuscript (the physical copy) line at a time, and -check each line when you finish it. You may use the +@item Enter one manuscript (the physical copy) system at a time (but still +only one bar per line of text), and +check each system when you finish it. You may use the @code{showLastLength} command to speed up processing -- see @ref{Skipping corrected music}.