From: Trevor Daniels Date: Fri, 7 Aug 2009 08:24:55 +0000 (+0100) Subject: Docs: LM: missing white space in lyrics error X-Git-Tag: release/2.13.4-1~179^2~172 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=1e8c439588ff227a8df70806682c5f9dd6327758;p=lilypond.git Docs: LM: missing white space in lyrics error --- diff --git a/Documentation/learning/tutorial.itely b/Documentation/learning/tutorial.itely index bf3b4578da..ce9c6bcb76 100644 --- 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 6285552264..dd95cc548d 100644 --- 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