Third Draft. Thanks so far. James
http://codereview.appspot.com/5315053/diff/5001/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/5315053/diff/5001/Documentation/notation/input.itely#newcode1020 Documentation/notation/input.itely:1020: There are two types of footnotes that can be used; automatic footnotes On 2011/10/27 01:56:26, Graham Percival wrote:
people don't read stuff in @subsection in html. Move this into
@unnumbered
Footnote overview
Done. I hope this was what you meant. http://codereview.appspot.com/5315053/diff/5001/Documentation/notation/input.itely#newcode1064 Documentation/notation/input.itely:1064: \autoFootnoteGrob #'@var{Layout Object} #'@var{(x . y)} On 2011/10/27 01:56:26, Graham Percival wrote:
what is this @example doing here? don't the @lilypond[]s show how to
use it? Yes they do. Although personally I don't think unless I pepper the @lilypond examples with '\markup' as well which might make them look messy/complicated, that it is that clear. If you take the @lilypond above you can see I have avoided the \markup function as it is implied (?) by the \autoFootnote however I *could* have one if I wanted (as shown by using the \bold markup which requires \markup to be explicitly stated. So that was why I put the whole command syntax in. So what do you think? http://codereview.appspot.com/5315053/diff/5001/Documentation/notation/input.itely#newcode1097 Documentation/notation/input.itely:1097: case use the manual @code{\footnote} command below. NB: Still waiting on mike to show me an example that I use in the \footnote command below that I can use for top-level markup with \autoFootnote. As I cannot seem to be able to reconstruct the example I use with manual footnotes for automatic footnotes. http://codereview.appspot.com/5315053/diff/5001/Documentation/notation/input.itely#newcode1107 Documentation/notation/input.itely:1107: for top-level @code{\markup} & chorded notes, and @code{\footnoteGrob} On 2011/10/27 01:56:26, Graham Percival wrote:
avoid & since non-english speakers might think it's input syntax.
Write out
"and" in full.
Done. Left the comma in after the 'list' so that the other 'and' doesn't look to cumbersome to non-non English speakers. :) http://codereview.appspot.com/5315053/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
