From: Mark Polesky <markpolesky@yahoo.com>
Date: Fri, 7 May 2010 21:31:24 +0000 (-0700)
Subject: Doc: LM: Mention barcheck warnings in song example; nitpicks.
X-Git-Tag: release/2.13.21-1~20
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=bb3052f000e2e511369bec5e15361e0a5c3c8b9f;p=lilypond.git

Doc: LM: Mention barcheck warnings in song example; nitpicks.
---

diff --git a/Documentation/learning/common-notation.itely b/Documentation/learning/common-notation.itely
index a483362b90..fd2be002f0 100644
--- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -163,7 +163,7 @@ signature only affects the @emph{printed} accidentals, not the
 note's @notation{pitch}!  This is a feature that often causes
 confusion to newcomers, so let us explain it in more detail.
 
-LilyPond makes a sharp distinction between musical content and
+LilyPond makes a clear distinction between musical content and
 layout.  The alteration (@notation{flat}, @notation{natural sign} or
 @notation{sharp}) of a note is part of the pitch, and is therefore
 musical content.  Whether an accidental (a @emph{printed} flat,
@@ -973,12 +973,25 @@ shine as bright as day}.  Let's extend it:
 >>
 @end lilypond
 
-We see the extra lyrics do not align properly with the notes.  The
-word @notation{shine} should be sung on two notes, not one.  This
-is called a @notation{melisma}, a single syllable sung to more
-than one note.  There are several ways to spread a syllable over
-multiple notes, the simplest being to add a slur across them, for
-details, see @ref{Ties and slurs}:
+If you compile the code in the example above, you should see some
+warnings in the console output:
+
+@example
+song.ly:12:29: warning: barcheck failed at: 5/8
+    The | moon doth shine as
+                             | bright as day; |
+song.ly:12:46: warning: barcheck failed at: 3/8
+    The | moon doth shine as | bright as day;
+                                              |
+@end example
+
+This is a good example of the usefulness of bar checks.  Now,
+looking at the music, we see that the extra lyrics do not align
+properly with the notes.  The word @notation{shine} should be sung
+on two notes, not one.  This is called a @notation{melisma}, a
+single syllable sung to more than one note.  There are several
+ways to spread a syllable over multiple notes, the simplest being
+to add a slur across them, for details, see @ref{Ties and slurs}:
 
 @lilypond[verbatim,quote]
 <<
diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely
index 14901a3b36..0965b5a562 100644
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -235,13 +235,13 @@ melody = \relative c' @{
 When LilyPond looks at this file, it takes the value of
 @code{melody} (everything after the equals sign) and inserts it
 whenever it sees @code{\melody}.  There's nothing special about
-the names -- it could be @code{melody}, @code{global},
-@code{keyTime}, @code{pianorighthand}, or @code{foofoobarbaz}.
-For more details, see @ref{Saving typing with variables and
-functions}.  Remember that you can use almost any name you like as
-long as it contains just alphabetic characters and is distinct
-from LilyPond command names.  The exact limitations on variable
-names are detailed in @ruser{File structure}.
+the name -- it could be @code{melody}, @code{global},
+@code{keyTime}, @code{pianorighthand}, or something else.
+Remember that you can use almost any name you like as long as it
+contains just alphabetic characters and is distinct from LilyPond
+command names.  For more details, see @ref{Saving typing with
+variables and functions}.  The exact limitations on variable names
+are detailed in @ruser{File structure}.
 
 
 @seealso