Re: Document <> and improve other simultanous music documentation. (issue 6248080)

[dak]

Reviewers: Ian Hulin (gmail),


http://codereview.appspot.com/6248080/diff/6001/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):

http://codereview.appspot.com/6248080/diff/6001/Documentation/notation/simultaneous.itely#newcode82
Documentation/notation/simultaneous.itely:82:
On 2012/06/01 17:08:19, Ian Hulin (gmail) wrote:
> @cindex placeholder events

I have my doubts that people will think of that keyword, but I don't
have a better candidate.

http://codereview.appspot.com/6248080/diff/6001/Documentation/notation/simultaneous.itely#newcode83
Documentation/notation/simultaneous.itely:83: A chord acts merely as
container for the notes inside and ornamentations
On 2012/06/01 17:08:19, Ian Hulin (gmail) wrote:
> "A chord merely acts as a container for notes inside it and and allows
> articulations or ornaments to be added consistently to all notes
inside."

No, that would be wrong.
<a-1 c-1 e-1> is different from <a c e>-1 and
<a\p c\p e\p> is different from <a c e>\p

http://codereview.appspot.com/6248080/diff/6001/Documentation/notation/simultaneous.itely#newcode84
Documentation/notation/simultaneous.itely:84: added to it.  As one
consequence, a chord without notes inside does not
On 2012/06/01 17:08:19, Ian Hulin (gmail) wrote:
> "As a consequence, a ..."
"As a consequence" ... "Furthermore" is not a pairing like "As one
consequence" ... "As another".  In this case, I'd likely just write
"Consequently," ...

Description:
Document <> and improve other simultanous music documentation.

This is a side issue of 2522: it improves the documentation dealing
with various ways of entering parallel music and gives the necessary
information to understand <> as a special case of chords.

Please review this at http://codereview.appspot.com/6248080/

Affected files:
  M Documentation/notation/simultaneous.itely


Index: Documentation/notation/simultaneous.itely
diff --git a/Documentation/notation/simultaneous.itely  
b/Documentation/notation/simultaneous.itely
index  
90669730a7f8682e0d43ae6f631d9cf43a8748fe..7d7592e4f032440b0dc8067b9ace991c04f81178  
100644
--- a/Documentation/notation/simultaneous.itely
+++ b/Documentation/notation/simultaneous.itely
@@ -78,6 +78,19 @@ they will not print.
 <a\f c( e>1 <a c) e>\f <a\< c e>( <a\! c e>) <a c e>\< <a c e> <a c e>\!
 @end lilypond

address@hidden chords, empty
+
+A chord acts merely as container for the notes inside and ornamentations
+added to it.  As one consequence, a chord without notes inside does not
+actually have a duration but can still be useful for attaching
+articulations.  As another, there is considerable leeway for arranging
+notes and articulations to happen at the same time without changing the
+result (for more possibilities, @pxref{Simultaneous expressions}):
+
address@hidden,quote,relative=2]
+<a c>2-.  <>-^ <a c>
address@hidden lilypond
+
 @cindex relative pitch, chords
 @cindex chords, relative pitch

@@ -244,8 +257,17 @@ a << { a4 b g } { d4 g c, } >>
 @end lilypond

 This can be useful if the simultaneous sections have identical
-rhythms, but attempts to attach notes with different durations
-to the same stem will cause errors.
+rhythms; but attempts to attach notes with different durations to
+the same stem will cause errors.  Notes, articulations, and property
+changes in a @emph{single} @samp{Voice} are collected and engraved in
+musical order:
+
address@hidden,verbatim,relative=2]
+<a c>4-.  <>-. << c a >>  << { c-. <c a> } { a s-. } >>
address@hidden lilypond
+
+Multiple stems or beams or different note durations or properties at
+the same musical time require the use of multiple voices.

 The following example shows how simultaneous expressions can
 generate multiple staves implicitly:
@@ -255,7 +277,8 @@ generate multiple staves implicitly:
 << { a4 b g2 } { d4 g2 c,4 } >>
 @end lilypond

-Here different rhythms cause no problems.
+Here different rhythms cause no problems because they are
+interpreted in different voices.

 @cindex collisions, clashing note columns
 @cindex collisions, ignoring