James
Looks pretty good.  I've made a couple of suggested additions.  Could
you please make a new patch with these changes in, and then I'll give it
a more careful check over.
Trevor


http://codereview.appspot.com/4839061/diff/3001/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):

http://codereview.appspot.com/4839061/diff/3001/Documentation/notation/changing-defaults.itely#newcode935
Documentation/notation/changing-defaults.itely:935: @cindex contexts,
layout order
@funindex \accepts
@funindex \denies

http://codereview.appspot.com/4839061/diff/3001/Documentation/notation/changing-defaults.itely#newcode954
Documentation/notation/changing-defaults.itely:954: To places chord
names on a stave e.g.,
Replace the previous two paras with:

The @qq{accepts} list of a context can be changed with the
@code{\accepts} and @code{\denies} commands.  @code{\accepts} adds a
context to the @qq{accepts} list and @code{\denies} removes a context
from the list.  For example, it would not normally be desirable for
chord names to be nested within a @{Staff} context, so the
@code{ChordNames} context is not included by default in the @qq{accepts}
list of the @code{Staff} context, but if this were to be required it can
be done:

http://codereview.appspot.com/4839061/diff/3001/Documentation/notation/changing-defaults.itely#newcode964
Documentation/notation/changing-defaults.itely:964:
Add here:

@code{\denies} is mainly used when a new context is being based on
another, but the required nesting differs.  For example, the
@code{VaticanaStaff} context is based on the @code{Staff} context, but
with the @code{VaticanaVoice} context substituted for the @code{Voice}
context in the @qq{accepts} list.

http://codereview.appspot.com/4839061/diff/3001/Documentation/notation/changing-defaults.itely#newcode967
Documentation/notation/changing-defaults.itely:967: @rprogram{An extra
staff appears}.
Add:

Installed Files:
@file{ly/engraver-init.ly}.

http://codereview.appspot.com/4839061/

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to