4th Draft. Thanks Graham.
@Mike Solomon:
I'd still like an example on how to autofootnote top-level markup if you
can, so I can remove that technically inaccurate statement.
Just in case you missed it, I'd like to use the same example as I use
for \footnote in this patch but for \autofootnote as I cannot get it
working after trying a few permutations, without error.
Merci B.
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:
On 2011/10/31 06:37:05, Graham Percival wrote:
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.
I took the first sentence of the next following para below and put it
here.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1067
Documentation/notation/input.itely:1067: @example
On 2011/10/31 06:37:05, Graham Percival wrote:
move this @example up to immediately after the first paragraph.
Done.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1072
Documentation/notation/input.itely:1072:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
On 2011/10/31 06:37:05, Graham Percival wrote:
what does this example show? could we have a 1-2 sentence
introduction?
Done.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1074
Documentation/notation/input.itely:1074: \header { copyright = \markup {
"Copyright" \char ##x00A9 "1970" } }
On 2011/10/31 06:37:05, Graham Percival wrote:
why do you want the tagline visible here?
This is the first time that users would see a footnote and see how it
fits in relation to the tagline and copyright (i.e. above it not below
as might be expected - if we're having to use \book (because we need to
use 'papersize=', might as well use tagline.
and why do you want the copyright symbol? does that seriously aid in
demonstrating how footnotes work?
I guess not, it's just if I am using 'copyright' field in the example it
seemed appropriate. But I'll remove the \char as it does look extraneous
now you mention it.
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.
On 2011/10/31 06:37:05, Graham Percival wrote:
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.
Done.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1119
Documentation/notation/input.itely:1119:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
On 2011/10/31 06:37:05, Graham Percival wrote:
1-2 intro for this @lilypond? even if it's obvious, we want a visual
division
between the @example and the verbatim commands.
Done.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1121
Documentation/notation/input.itely:1121: \markup {
On 2011/10/31 06:37:05, Graham Percival wrote:
why do you want a tagline in this @lilypond?
No particular reason. Just less lines in the @lilypond. I have removed
it though as there is no need now that we have showed this in the first
@lilypond of this section and tagline = ##f has been discussed at length
elsewhere.
http://codereview.appspot.com/5315053/diff/8001/Documentation/notation/input.itely#newcode1156
Documentation/notation/input.itely:1156:
@lilypond[verbatim,quote,ragged-right,papersize=a8]
On 2011/10/31 06:37:05, Graham Percival wrote:
introduce this @lilypond as well
Done.
http://codereview.appspot.com/5315053/
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
