Re: Doc: NR Added new node for Custom Footnotes (issue 5315053)

[graham]

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1019
Documentation/notation/input.itely:1019:
technically there should be a 1-2 sentence introduction here.  Something
useless and uninformative, but making the pdf (and the rare person who
clicks on this in html) look a little bit friendlier.

you can add this after it's pushed, or just before it's pushed.

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1067
Documentation/notation/input.itely:1067: @example
move this @example up to immediately after the first paragraph.

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1072
Documentation/notation/input.itely:1072:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
what does this example show?  could we have a 1-2 sentence introduction?

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1074
Documentation/notation/input.itely:1074: \header { copyright = \markup {
"Copyright" \char ##x00A9 "1970" } }
why do you want the tagline visible here?  and why do you want the
copyright symbol?  does that seriously aid in demonstrating how
footnotes work?

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1101
Documentation/notation/input.itely:1101: case use the manual
@code{\footnote} command below.
replace with "in this case, use @ref{Manual footnotes}." since we might
possibly want to reorder the chapters/sections/etc.

highly unlikely in this case, but you still shouldn't assume that
material is "above" or "below" anything else.  not in Notation, at
least; you can do that in Learning if you must.

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1119
Documentation/notation/input.itely:1119:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
1-2 intro for this @lilypond?  even if it's obvious, we want a visual
division between the @example and the verbatim commands.

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1121
Documentation/notation/input.itely:1121: \markup {
why do you want a tagline in this @lilypond?

http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1156
Documentation/notation/input.itely:1156:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
introduce this @lilypond as well

http://codereview.appspot.com/5315053/