Docs: LM: missing white space in lyrics error

diff --git a/Documentation/learning/tutorial.itely b/Documentation/learning/tutorial.itely
index bf3b4578da21da9e521d71890a5fc0541d74e641..ce9c6bcb76cc5a7854c7accf240b33e99554e0e1 100644 (file)
--- a/Documentation/learning/tutorial.itely
+++ b/Documentation/learning/tutorial.itely
@@ -887,8 +887,13 @@ separating each syllable with a space.
 >>
 @end lilypond
 
-Note the curly brackets delimiting both the music and the lyrics,
-and the double angle brackets @w{@code{<< ... >>}} around the
+Note the curly brackets delimiting both the music and the lyrics.
+It is essential that the final syllable is separated from the
+terminating curly bracket by a space or a newline, or it will be
+assumed to be part of the syllable, giving rise to an obscure
+error, see @ref{Apparent error in ../ly/init.ly}.
+
+Note also the double angle brackets @w{@code{<< ... >>}} around the
 whole piece to show that the music and lyrics are to occur at the
 same time.
 

diff --git a/Documentation/learning/working.itely b/Documentation/learning/working.itely
index 6285552264380e19dbfb4cbd46a4ca7622528c54..dd95cc548d92f0392db3c9b16066f8ed502b6960 100644 (file)
--- a/Documentation/learning/working.itely
+++ b/Documentation/learning/working.itely
@@ -357,6 +357,13 @@ of an input file is described in @ref{How LilyPond input files work}.
 Using an editor which automatically highlights matching brackets and
 braces is helpful to avoid such errors.
 
+A second common cause is no white space between the last syllable
+of a lyrics block and the terminating brace, (@code{@}}).  Without
+this separation the brace is taken to be part of the syllable.  It
+is always advisable to ensure there is white space before and after
+@emph{every} brace.  For the importance of this when using lyrics,
+see @ruser{Lyrics explained}.
+
 This error message can also appear if a terminating quote sign,
 (@code{"}), is omitted.  In this case an accompanying error message
 @c keep "-matching straight in fancy editors