Re: Clarify notation for slurs and beams (issue 343060043 by address@hidden)

[Carl . D . Sorensen]

Reviewers: Be-3, Trevor Daniels,

Message:
On 2018/04/30 11:37:09, Be-3 wrote:
> Hi Carl,

> Concise, comprehensible, - LGTM!

> Perhaps it should be explicitly pointed out that the duration
shorthand does not
> work for rests.
> There have been some misconceptions lately on the user list, and so I
think this
> detail probably deserves special attendance.

I've added a sentence that should clarify.


https://codereview.appspot.com/343060043/diff/1/Documentation/learning/fundamental.itely#newcode487
> Documentation/learning/fundamental.itely:487: \absolute
{c'8-1--(~^\markup{"text
> annotationi"} c' d')}
> Shouldn't it be "text annotation"?
Yes.  Now you know which editor I was using to create the patch -- it's
vim leftovers.

Thanks for the catch.



Description:
Clarify notation for slurs and beams

Note that the opening code for slurs and beams comes after
the first note of the slur or beam.

Also, add a section about notes containing pitches, durations,
and post-events.

Please review this at https://codereview.appspot.com/343060043/

Affected files (+41, -2 lines):
  M Documentation/learning/common-notation.itely
  M Documentation/learning/fundamental.itely


Index: Documentation/learning/common-notation.itely
diff --git a/Documentation/learning/common-notation.itely  
b/Documentation/learning/common-notation.itely
index  
b9b62cf3b321452ec117290c7f9b68cf4246e39b..a6136a421a0b84f854d793a060e17b8551ee5eb6  
100644
--- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -275,6 +275,7 @@ Notation Reference:
 @funindex ( ... )
 @funindex \( ... \)

+
 @menu
 * Ties::
 * Slurs::
@@ -318,7 +319,8 @@ Music Glossary: @rglos{slur}.

 A @notation{slur} is a curve drawn across many notes.  The
 starting note and ending note are marked with @code{(} and
address@hidden)} respectively.
address@hidden)} respectively. Note that the @code{(} comes after
+the first note of the slur.

 @lilypond[verbatim,quote]
 \relative { d''4( c16) cis( d e c cis d) e( d4) }
@@ -369,6 +371,9 @@ Notation Reference:
 @node Articulation and dynamics
 @subsection Articulation and dynamics

+Articulations and dynamics are indicated by adding special codes
+after the notes to which they apply,
+
 @menu
 * Articulations::
 * Fingerings::
@@ -526,6 +531,7 @@ All @notation{beams} are drawn automatically:
 If you do not like the automatic beams, they may be overridden
 manually.  To correct just an occasional beam mark the first note
 to be beamed with @code{[} and the last one with @code{]}.
+Note that @code{[} comes after the first beamed note.

 @lilypond[verbatim,quote]
 \relative { a'8[ ais] d[ ees r d] c16 b a8 }
@@ -597,7 +603,7 @@ Music Glossary: @rglos{note value}, @rglos{triplet}.

 @notation{Tuplets} are made with the @code{\tuplet} keyword.  It
 takes two arguments: a fraction and a piece of music.  The
-fraction is the number of tuplet notes over the number
+fraction is the number of tuplet notes over the number
 of notes normally filling the same duration.
 For triplets, there are three notes instead of two, so
 @notation{triplets} have 3/2 as their fraction.
Index: Documentation/learning/fundamental.itely
diff --git a/Documentation/learning/fundamental.itely  
b/Documentation/learning/fundamental.itely
index  
40efc3777ab567d7f440a360839e4a3d1570fa25..fc8290a14314c2b916393e414373aad305a2e301  
100644
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -40,6 +40,7 @@ description of the input format, see @ruser{File  
structure}.
 * Introduction to the LilyPond file structure::
 * Score is a (single) compound musical expression::
 * Nesting music expressions::
+* Structure of a note entry::
 * On the un-nestedness of brackets and ties::
 @end menu

@@ -457,6 +458,38 @@ These require further commands which
 have not yet been introduced.  See @ref{Size of objects},
 and @ruser{Ossia staves}.

address@hidden Structure of a note entry
address@hidden Structure of a note entry
+
+A note entry in LilyPond consists of a pitch, followed by a duration,
+optionally followed by one or more post-events.  Post-events add
+things such as articulations, fingerings, string numbers, slurs, ties
+and explanatory text.
+
+The pitch may be explicitly defined using the current LilyPond input
+language as described in @ruser{Note names in other languages}.  The
+pitch may be omitted.  If the pitch is omitted, the pitch of a current
+note will be the same as the pitch of the previous note in the input
+file, see @ruser{Durations}.
+
+The duration includes a number and optionally one or more dots.  If a
+duration is not explicitly defined, the duration of a current note will
+be the same as the duration of the previous note, chord, rest, or spacer
+rest, see @ruser{Durations}.
+
+Post-events follow the note to which they are attached.  Suppose we
+want to have an eighth note c' with a fingering of 1, a tenuto
+articulation, a slur beginning with the note, a tie beginning with
+the note, and a text annotation.  This can be accomplished as
+shown.
+
address@hidden,quote]
+\absolute {c'8-1--(~^\markup{"text annotationi"} c' d')}
address@hidden lilypond
+
address@hidden @ruser{Pitches},
address@hidden,
address@hidden marks},

 @node On the un-nestedness of brackets and ties
 @subsection On the un-nestedness of brackets and ties