Minor fixes (comments from -devel).

diff --git a/ChangeLog b/ChangeLog
index ea03e8d04453486bff36bbc63429058b5486d3f3..8620b8b7d322e841c191cdb3ba5bed8edf058d16 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2006-01-29  Graham Percival  <gpermus@gmail.com>
+
+       * Documentation/user/putting.itely: minor fixes (comments on -devel).
+
 2006-01-29  Nicolas Sceaux  <nicolas.sceaux@free.fr>
 
        * Documentation/topdocs/NEWS.tely (Top): add \parallelMusic news.

diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely
index de8a1a3cbcc39673669ae92e3153162fb647297b..bc0b16799fd78b0d441138a01e1ecec44c7e407a 100644 (file)
--- a/Documentation/user/putting.itely
+++ b/Documentation/user/putting.itely
@@ -64,6 +64,26 @@ 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),
+
+@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
+@code{showLastLength} command to speed up processing -- see
+@ref{Skipping corrected music}.
+
+@item Define @code{mBreak = @{ \break @}} and insert @code{\mBreak}
+in the input file whenever the manuscript has a line break.  This
+makes it much easier to compare the LilyPond music to the original
+music.  When you are finished proofreading your score, you may
+define @code{mBreak = @{ @}} to remove all those line breaks.  This
+will allow LilyPond to place line breaks wherever it feels are
+best.
+
+@end itemize
+
 
 @node Extending the templates
 @section Extending the templates
@@ -550,7 +570,9 @@ lower = @{ @}
 @end example
 
 @noindent
-Remember that you can use any names you like.
+Remember that you can use almost any name you like.  The
+limitations on identifier names are detailed in
+@ref{File structure}.
 
 When writing a @code{\score} section, or when reading
 one, just take it slowly and carefully.  Start with
@@ -569,8 +591,9 @@ compile.  The messages that LilyPond gives may help
 you find the error, but in many cases you need to do some
 investigation to determine the source of the problem.
 
-The most powerful tool for this purpose is the
-comment (@code{%} and @code{%@{ ... %@}}).  If you don't
+The most powerful tools for this purpose are the
+single line comment (indicated by @code{%}) and the block
+comment (indicated by @code{%@{ ... %@}}).  If you don't
 know where a problem is, start commenting out huge portions
 of your input file.  After you comment out a section, try
 compiling the file again.  If it works, then the problem