From b578d2ca94ad6a6f7d6d54cd2f33592451b7eb05 Mon Sep 17 00:00:00 2001 From: Mark Polesky Date: Tue, 4 May 2010 18:24:00 -0700 Subject: [PATCH] Doc: LM: Add new node to introduce bar checks. --- Documentation/learning/common-notation.itely | 21 ++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/Documentation/learning/common-notation.itely b/Documentation/learning/common-notation.itely index 4039e26577..7c3a2cc270 100644 --- a/Documentation/learning/common-notation.itely +++ b/Documentation/learning/common-notation.itely @@ -51,6 +51,7 @@ This section introduces common notation that is used for one voice on one staff. @menu +* Bar checks:: * Accidentals and key signatures:: * Ties and slurs:: * Articulation and dynamics:: @@ -60,6 +61,26 @@ on one staff. @end menu +@node Bar checks +@subsection Bar checks + +Though not strictly necessary, @emph{bar checks} should be +used in the input code to show where bar lines are expected +to fall. They are entered using the bar symbol, @code{|}. +With bar checks, the program can verify that you've entered +durations that make each measure add up to the correct +length. Bar checks also make your input code easier to +read, since they help to keep things organized. + +@lilypond[verbatim,quote,relative=2] +g1 | e1 | c2. c'4 | g4 c g e | c4 r r2 | +@end lilypond + +@seealso +Notation Reference: +@ruser{Bar and bar number checks}. + + @node Accidentals and key signatures @subsection Accidentals and key signatures -- 2.39.2