Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement, which is
mentioned there.
I think a better place would be in a new @subsection at the
top of 2.1 "Single staff notation", just before 2.1.1
"Accidentals and key signatures". Here's my proposed text:
* * * * * * * * * *
@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}.
* * * * * * * * * *
- Mark