[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doc: Adjusted CG Policy on @lilypond[] variables (issue4445070)
From: |
tdanielsmusic |
Subject: |
Re: Doc: Adjusted CG Policy on @lilypond[] variables (issue4445070) |
Date: |
Thu, 28 Apr 2011 22:40:39 +0000 |
A few more nitpicks; otherwise looks fine.
[I'm not convinced adding colons before @examples is a good
thing, especially when the sentence runs on after the
example, but for now that is the policy.]
http://codereview.appspot.com/4445070/diff/4001/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
http://codereview.appspot.com/4445070/diff/4001/Documentation/contributor/doc-work.itexi#newcode314
Documentation/contributor/doc-work.itexi:314: inlcude the
@code{papersize=X} variable, where @code{X} is a defined
typo, and a superfluous space
http://codereview.appspot.com/4445070/diff/4001/Documentation/contributor/doc-work.itexi#newcode327
Documentation/contributor/doc-work.itexi:327: \header{
\header {
http://codereview.appspot.com/4445070/diff/4001/Documentation/contributor/doc-work.itexi#newcode359
Documentation/contributor/doc-work.itexi:359: Inspirational headwords
are produced with
colon
http://codereview.appspot.com/4445070/diff/4001/Documentation/contributor/doc-work.itexi#newcode367
Documentation/contributor/doc-work.itexi:367: LSR snippets are linked
with
colon
http://codereview.appspot.com/4445070/