[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doc: NR rewrite of 3.2 Titles and Headers (issue4124056)
From: |
pkx166h |
Subject: |
Re: Doc: NR rewrite of 3.2 Titles and Headers (issue4124056) |
Date: |
Sun, 05 Jun 2011 10:28:31 +0000 |
On 2011/05/04 17:08:39, Carl wrote:
Looks mostly good to me.
Carl
http://codereview.appspot.com/4124056/diff/32001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4124056/diff/32001/Documentation/notation/input.itely#newcode667
Documentation/notation/input.itely:667: Text fields left unset in a
@code{\header} block are replaced with
This paragraph has three different ideas -- null markups, piece and
opus, and
forcing titles to start on a new page.
They should probably be separated into three different paragraphs.
http://codereview.appspot.com/4124056/diff/32001/Documentation/notation/input.itely#newcode937
Documentation/notation/input.itely:937:
Need @seealso for the @ref in this node -- Title blocks explained,
Default
layout of book and score title blocks,.
http://codereview.appspot.com/4124056/diff/32001/Documentation/notation/input.itely#newcode987
Documentation/notation/input.itely:987: @end lilypond
Need @seealso here, with all of the @ref in this node (Default layout
of book
and title blocks).
Carl, I have done this now (and the one above). We only really focused
on the 'first half' of the text that Mark did (and also hammer out all
the @lilypond settings too).
I am going to close this issue - I left it open only because I
remembered you wanted some additions that were not going to be in the
main patch, and open a new one with these and other changes. I also
wanted to make some more 'edits' to this text once the major changes
were done to keep some layout and style consistency.
http://codereview.appspot.com/4124056/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Doc: NR rewrite of 3.2 Titles and Headers (issue4124056),
pkx166h <=