Docs: state that LilyPond input is in terms of pitches

Docs: state that LilyPond input is in terms of pitches

[Keith, 2014-12-07 06:41:31]

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
File Documentation/learning/common-notation.itely (left):

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
Documentation/learning/common-notation.itely:108: @subsection Accidentals and
key signatures
This section doesn't tell us how to enter accidentals, but rather how to enter
pitches.

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
Documentation/learning/common-notation.itely:199: note's @notation{pitch}!  This
is a feature that often causes
Well, anyone who can read music knows that the key signature and accidentals do
affect the note's pitch.  'note' probably means the input to lilyPond and 'key
signature' probably means the \key command.

https://codereview.appspot.com/185140043/diff/20001/Documentation/notation/pi...
File Documentation/notation/pitches.itely (left):

https://codereview.appspot.com/185140043/diff/20001/Documentation/notation/pi...
Documentation/notation/pitches.itely:395: natural signs.
I don't know why naturals were singled out.  It implies that naturals are
somehow different from the other accidentals in LilyPond. 
The example below shows a natural, so no-one will be left wondering how to force
one to print.

[pkx166h, 2014-12-09 07:52:27]

Fails make.

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
Documentation/learning/common-notation.itely:119: @node Pitches
Problem with calling this node 'Pitches' is that it throws an error as it has
been previously defined in another @node in this doc. You'll need to change it.

[dak, 2014-12-09 09:18:08]

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
Documentation/learning/common-notation.itely:119: @node Pitches
On 2014/12/09 07:52:26, J_lowe wrote:
> Problem with calling this node 'Pitches' is that it throws an error as it has
> been previously defined in another @node in this doc. You'll need to change
it.

It's also not what this is about.  It's more like "black keys" informally. 
Formally possibly "The chromatic scale".  But that sounds more like composition
theory than note names.  So "Pitch alterations" might work better.

[Trevor Daniels, 2014-12-09 09:25:00]

Apart from the node name, LGTM.

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/co...
Documentation/learning/common-notation.itely:111: * Pitches::
The earlier section, Pitches, in LM 1.2.1, talked only about unaltered pitches. 
Maybe consider renaming this section "Pitch alterations"?

Trevor

[pkx166h, 2014-12-12 11:28:39]

https://codereview.appspot.com/185140043/diff/40001/Documentation/learning/co...
File Documentation/learning/common-notation.itely (right):

https://codereview.appspot.com/185140043/diff/40001/Documentation/learning/co...
Documentation/learning/common-notation.itely:184: \bar "||" key c \minor
\key not key.

This breaks make doc