Document use of alignAboveContext and alignBelowContext

Document use of alignAboveContext and alignBelowContext (2557)

[PhilEHolmes, 2012-07-06 11:21:13]

One suggestion, otherwise LGTM.  Thanks.

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

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.ite...
Documentation/notation/vocal.itely:1327: 
One for Graham really, but it strikes me as wrong to add an example showing what
is effectively incorrect output.  I would have thought it better to simply say
the lyrics go below the bottom staff unless you tell them explicitly where to go
like this...

[Graham Percival, 2012-07-08 04:02:42]

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

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/changing-...
Documentation/notation/changing-defaults.itely:1024: @code{\new Staff \with @{
alignAboveContext = #"main" @} }
remember that you're not supposed to have any initial spaces inside an @example.
 Your other patches made sense because those @examples were clearly smaller
parts of a longer @example so the extra spaces were ok, but here I think there
should be no spaces.

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/changing-...
Documentation/notation/changing-defaults.itely:1036: found elsewhere --- see the
@q{See also} section below.
where, exactly?  should I be looking in Installed files, or application usage,
or...?

I'd rather see an exact @rlearning{Nesting} or
@rlsr{Vocal,can-we-link-to-direct-snippet-names?} or something like that.

PS no wait, if there's an exact snippet that shows this, it should be included
directly on this page.

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

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.ite...
Documentation/notation/vocal.itely:1327: 
On 2012/07/06 11:21:14, PhilEHolmes wrote:
> One for Graham really, but it strikes me as wrong to add an example showing
what
> is effectively incorrect output.  I would have thought it better to simply say
> the lyrics go below the bottom staff unless you tell them explicitly where to
go
> like this...

I agree.  If you're deliberately showing wrong syntax, I suggest it should be in
@knownissues (which we could possibly rename to "known confusions" or something
like that)

Phil's suggestion has the added bonus of keeping this subsection more compact. 
:)

[Trevor Daniels, 2012-07-08 08:04:42]

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

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/changing-...
Documentation/notation/changing-defaults.itely:1024: @code{\new Staff \with @{
alignAboveContext = #"main" @} }
Done

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/changing-...
Documentation/notation/changing-defaults.itely:1036: found elsewhere --- see the
@q{See also} section below.
Done; it means the sentence ends with three references though.  One of them is a
snippet, but I don't want to include just one of them here, especially as the
explanation of it would be missing.

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

http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.ite...
Documentation/notation/vocal.itely:1327: 
On balance I think it would be best just to omit the example showing the wrong
layout.  We don't want to litter the NR with examples of how the user can
produce incorrect output - there are too many ways of doing that :)  Done.

[Graham Percival, 2012-07-09 04:55:20]

LGTM.  Ignore my other message that talked about using git-cl to upload an
edited patch; I hadn't noticed that you did that here.

http://codereview.appspot.com/6353079/diff/6001/Documentation/notation/changi...
File Documentation/notation/changing-defaults.itely (right):

http://codereview.appspot.com/6353079/diff/6001/Documentation/notation/changi...
Documentation/notation/changing-defaults.itely:1037: @ref{Modifying single
staves} and @ref{Techniques specific to lyrics}.
Personally, I'm fond of the Oxford comma, but this is fine.  Having the three
@refs is good.

[t.daniels_treda.co.uk, 2012-07-09 09:00:10]

<graham@percival-music.ca> wrote Monday, July 09, 2012 5:55 AM


> Ignore my other message that talked about using git-cl to upload
> an edited patch; I hadn't noticed that you did that here.

OK.  It was not worth the effort for a two-word change.

I uploaded a new patch-set here as the changes were more
extensive.  git-cl worked fine.  I even have a small working set of
vi commands now, too :)

http://codereview.appspot.com/6353079/

[Trevor Daniels, 2012-07-11 07:01:56]

Patch pushed
bcd9d85bfc1dd6cc2dd3e98901b4df33fd6d0989