Re: Doc: NR rewrite of 3.2 Titles and Headers (issue4124056)

[pkx166h]

Reviewers: Graham Percival, lilyfan_orange.fr, Trevor Daniels,  
t.daniels_treda.co.uk, james.lowe_datacore.com, graham_percival-music.ca,

Message:
Second draft been posted. I couldn't work out how to do one request so
this has not been changed.

Putting the tagline in an @lilypond without having the need for a whole
page to print.


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

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode526
Documentation/notation/input.itely:526: @subsection Creating titles,
headers, and footers
On 2011/02/06 03:21:33, Graham Percival wrote:
> I get nervous when the @subsection doesn't match the @node, but I
can't think of
> a definitely alternative after a few seconds.  The only serious
alternative at
> the moment is "Creating titles and headers and footers".  :(

Done.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode548
Documentation/notation/input.itely:548:
@lilypond[quote,verbatim,noragged-right,staffsize=17,indent=13\mm]
On 2011/02/06 03:21:33, Graham Percival wrote:
> First - it's ok to be more "creative" with [options] when we're
talking about
> spacing stuff.  However, are you certain you need staffsize=17 and
indent=13\mm
> ?  If you experimented with a few values and decided this looked best,
that's a
> perfectly acceptable answer!

> That said, could you standardize on indent=15\mm, instead of switching
between
> 13 and 15 ?

I've done no experimenting - this was lifted from Mark's patch. I
assumed he had. I'll standardize on 13mm indent for now.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode555
Documentation/notation/input.itely:555: \new Staff \relative g, {
On 2011/02/06 03:21:33, Graham Percival wrote:
> I think the doc policy officially calls for { between the Staff and
\relative,
> but IMO this is ok syntax.
> (you might want to look at the CG, and prepare a patch saying
"sometimes it's ok
> not to strictly add { everywhere, such as in NR 3, but always do it in
the LM
> and NR 1+2)

I'll revert to Doc Policy again if you think it looks worse I can put it
back and make a CG addendum. It's better to be consistent throughout if
we can though.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode584
Documentation/notation/input.itely:584: @example
On 2011/02/06 03:21:33, Graham Percival wrote:
> Do you really need an @example ?  I think this material could be
worked into the
> following @lilypond.

Done.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode592
Documentation/notation/input.itely:592: #(set-default-paper-size "a5")
Again I don't know, this was done by Mark so I assumed he had a reason.
I will take this out in the meantime.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode597
Documentation/notation/input.itely:597: indent = 0\mm
Again, not me. I will remove these as I was unsure why they were here
also.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode661
Documentation/notation/input.itely:661: The default settings for
@code{bookTitleMarkup}:
Done. and also removed 'Default' from all the @node and @numbered...

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode681
Documentation/notation/input.itely:681: \header {
Evidently. Although would it 'improve' things, do you think if we had a
line of music underneath to give these context - just a thought.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode752
Documentation/notation/input.itely:752: The default tagline is a
clickable link (to
I'm not sure how to do this within an @lilypond without having a huge
blank space of staff and the tagline at the bottom.

http://codereview.appspot.com/4124056/diff/1/Documentation/notation/input.itely#newcode759
Documentation/notation/input.itely:759: The default tagline can be
changed by adding a @code{tagline =} in the
On 2011/02/06 03:21:33, Graham Percival wrote:
> Holy "talking through the code", batman!  Can we revise this?

Done.

Description:
Doc: NR rewrite of 3.2 Titles and Headers

This is an edited verion of Mark Polesky's patch
http://codereview.appspot.com/3667041/

No new information has been added from the original patch,
but the text has been edited so that it is more suitable to the Notation
Reference Style.

Please review this at http://codereview.appspot.com/4124056/

Affected files:
  M Documentation/notation/input.itely
  M ly/titling-init.ly