Re: Doc: Various to LM and NR from user email threads (issue3581041)

[pkx166h]

http://codereview.appspot.com/3581041/diff/1/Documentation/learning/fundamental.itely
File Documentation/learning/fundamental.itely (right):

http://codereview.appspot.com/3581041/diff/1/Documentation/learning/fundamental.itely#newcode2115
Documentation/learning/fundamental.itely:2115: no note heads are
produced and so no Stem or Beams are created either.}
On 2010/12/11 22:56:02, Neil Puttock wrote:
> stems or beams

Leaving this file unedited for another patch until those other files
that have
consensus have been pushed.

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/editorial.itely
File Documentation/notation/editorial.itely (right):

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/editorial.itely#newcode145
Documentation/notation/editorial.itely:145: using the @code{fontSize}
property.
On 2010/12/11 22:56:02, Neil Puttock wrote:
> This is a problem in markup only, thus applies to the \fontsize markup
command
> (not the context property fontSize).

> I suggested changing the definitions of the named commands to remove
the
> inconsistency (via \abs-fontsize), but if we'd rather leave them as
they are
> this knowissue should be moved to text.itely.

Done.

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/repeats.itely
File Documentation/notation/repeats.itely (right):

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/repeats.itely#newcode153
Documentation/notation/repeats.itely:153: number of endings.  If you
must use bar checks then put
On 2010/12/10 23:41:50, Trevor Daniels wrote:
> If you do use bar checks ...

Leaving this file unedited for another patch until those other files
that have consensus have been pushed.

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/spacing.itely#newcode928
Documentation/notation/spacing.itely:928: @warning{Odd page numbers are
always on the right.  If you want the
On 2010/12/11 14:01:10, Graham Percival wrote:
> On 2010/12/11 00:36:29, Carl wrote:
> > I think that this should be a known issue, rather than a warning.

> Agreed, this is definitely better as a known issue.

Done.

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/staff.itely
File Documentation/notation/staff.itely (right):

http://codereview.appspot.com/3581041/diff/1/Documentation/notation/staff.itely#newcode278
Documentation/notation/staff.itely:278: @code{PianoStaff} does not, by
default, accept @code{ChordNames}.
On 2010/12/11 14:01:10, Graham Percival wrote:
> This should be a known issue, instead of a warn... oh, oops, sorry,
it's already
> a known issue.  :)

Done.

http://codereview.appspot.com/3581041/