lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doc: NR Moved Appendix C to CG (issue 6948070)


From: tdanielsmusic
Subject: Re: Doc: NR Moved Appendix C to CG (issue 6948070)
Date: Wed, 26 Dec 2012 10:09:45 +0000

LGTM, apart from a couple of nitpicks which
I missed earlier.  No need to post a new
patch-set.


https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (left):

https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely#oldcode1545
Documentation/notation/notation-appendices.itely:1545: (BNF) in
@ref{LilyPond grammar}.  This file is used to build the
Our standard is two spaces after full stops in
mono-spaced text.

https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (right):

https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely#newcode1534
Documentation/notation/notation-appendices.itely:1534: @cindex grammar,
for LilyPond
I think the comma is wrong here.  "grammar for Lilypond"
is perfectly sensible.

https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely#newcode1547
Documentation/notation/notation-appendices.itely:1547: parser during the
program build by the parser generator, Bison. It is
Same here.

https://codereview.appspot.com/6948070/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]