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

[k-ohara5a5a]

The issue was that s1*0 can affect the default duration of the next
note, while <> does not, but the solution of <> was tempered by opinions
that <> is cryptic.

s1*0 is rarely used.  The uses I find, in documentation and
mutopiaproject, are to attach a post-fix notation to an object where it
is inconvenient or impossible to postfix the notation.

This patch fails to explain how <> solves the difficulty for with people
have used s1*0.  Instead, it demonstrates the considerable leeway to
transform clear input to cryptic input, without changing the resulting
output.


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

http://codereview.appspot.com/6248080/diff/11001/Documentation/notation/simultaneous.itely#newcode86
Documentation/notation/simultaneous.itely:86: duration but can still be
useful for attaching articulations.
The text implies that <> is useful for placing articulations where there
are no notes, such as a delayed turn,
  \relative c'' \new Staff {g2. <>\turn a4}
but <> is not useful here, since we need parallel spacer rests anyway,
  \relative c'' \new Staff<<{g2. a4} {s2 s2\turn}>>

http://codereview.appspot.com/6248080/