Doc: NR Pitches.itely - Clef - updated snippets and text

Issue 3976

Added 2 new snippets:
1 snippet added to NR
1 snippet added just to Snippets

Modified 1 existing snippet:
This was already (and still is) included in the NR

Deleted 2 snippets (and incorporated them in the
main text in @lilyponds)

Added new @lilypond example that was originally
described (but not show)n in the 'Tweaking Clef
Properties' snippet to show how to remove
the clef glyph from the end of a line. As this
'tweak' is relatively simple (a single \set and
\unset) and more than likely to be used (IMHO) by
the general user than the listed items in the
snippet, I thought it better to be in the NR than
another example in either an already long snippet
or by creating yet another snippet.

Some minor linelength formatting as per CG.

[pkx166h, 2014-06-27 23:13:34]

WIth Pierre's suggestion and some texidoc edits

[pkx166h, 2014-06-28 10:33:14]

Used correct 'comment' symbol in Scheme

[Keith, 2014-06-29 03:17:00]

Is it worth making the Notation Reference longer?

https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
File Documentation/notation/pitches.itely (right):

https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
Documentation/notation/pitches.itely:1325: \override
Staff.KeySignature.flat-positions = #'((-5 . 5))
This already shows how to print key signatures over a different or wider range
of the staff.  You might consider this good enough.

https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/ne...
File Documentation/snippets/new/creating-custom-key-signatures.ly (right):

https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/ne...
Documentation/snippets/new/creating-custom-key-signatures.ly:26: \musicglyph
#"clefs.F"
But F is not 3 staff-spaces below C, only 2.
You could \translate #'(-3 . -2) \musicglyph #"clefs.F" to avoid the overlap.
Or you could use a G clef \translate #'(0. +2) \musicglyph #"clefs.G"

[pkx166h, 2014-06-30 21:40:17]

> Is it worth making the Notation Reference longer?

What do you suggest?

https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
File Documentation/notation/pitches.itely (right):

https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
Documentation/notation/pitches.itely:1325: \override
Staff.KeySignature.flat-positions = #'((-5 . 5))
On 2014/06/29 03:17:00, Keith wrote:
> This already shows how to print key signatures over a different or wider range
> of the staff.  You might consider this good enough.

I don't understand what you mean. Good enough compared to what?

https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/ne...
File Documentation/snippets/new/creating-custom-key-signatures.ly (right):

https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/ne...
Documentation/snippets/new/creating-custom-key-signatures.ly:26: \musicglyph
#"clefs.F"
On 2014/06/29 03:17:00, Keith wrote:
> But F is not 3 staff-spaces below C, only 2.
> You could \translate #'(-3 . -2) \musicglyph #"clefs.F" to avoid the overlap.
> Or you could use a G clef \translate #'(0. +2) \musicglyph #"clefs.G" 

Thanks, I went for the 'avoiding overlap'.

[Keith, 2014-07-01 06:56:42]

On Mon, 30 Jun 2014 14:40:17 -0700, <pkx166h@gmail.com> wrote:

>> Is it worth making the Notation Reference longer?
>
> What do you suggest?

Depending on your opinion about the NR length, maybe leaving these examples in
lsr only.

>
https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
> Documentation/notation/pitches.itely:1325: \override
> Staff.KeySignature.flat-positions = #'((-5 . 5))
> On 2014/06/29 03:17:00, Keith wrote:
>> This already shows how to print key signatures over a different or
> wider range
>> of the staff.  You might consider this good enough.
>
> I don't understand what you mean. Good enough compared to what?

Good enough alone, without the creating-custom-key-signatures.ly snippet.
The double-clef would fit in tweaking-clef-properties.ly

Or, the double-clef might be a better example for \translate in appendix A.10.2
\markup {
    \combine
      \musicglyph #"clefs.C"
      \translate #'(2.5 . 2) \musicglyph #"clefs.G"
}

If you don't mind the NR length, this all looks good as it is.

[pkx166h, 2014-07-01 07:34:26]

On 2014/07/01 06:56:42, Keith wrote:
> On Mon, 30 Jun 2014 14:40:17 -0700, <mailto:pkx166h@gmail.com> wrote:
> 
> >> Is it worth making the Notation Reference longer?
> >
> > What do you suggest?
> 
> Depending on your opinion about the NR length, maybe leaving these examples in
> lsr only.
> 
> >
>
https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pi...
> > Documentation/notation/pitches.itely:1325: \override
> > Staff.KeySignature.flat-positions = #'((-5 . 5))
> > On 2014/06/29 03:17:00, Keith wrote:
> >> This already shows how to print key signatures over a different or
> > wider range
> >> of the staff.  You might consider this good enough.
> >
> > I don't understand what you mean. Good enough compared to what?
> 
> Good enough alone, without the creating-custom-key-signatures.ly snippet.
> The double-clef would fit in tweaking-clef-properties.ly
> 
> Or, the double-clef might be a better example for \translate in appendix
A.10.2
> \markup {
>     \combine
>       \musicglyph #"clefs.C"
>       \translate #'(2.5 . 2) \musicglyph #"clefs.G"
> }
> 
> If you don't mind the NR length, this all looks good as it is.
> 

Oh I see.

I had reduced the NR's 'Clef' section slightly in a previous check-in - where I
deleted the list of 'here are some other examples of different clefs' and
referred it to a newly created Appendix listing all the clefs there. Then I saw
your email (regarding this changing the clef engraver) and the reaction it got
and wondered if perhaps others had been wanting something like this a lot; but
if this isn't something people really would use that much then I have no
problems leaving it in the LSR/Snippets doc.

I prefer only having snippets in the NR where they are the most often called for
tweaks/overrides etc. Than just for the sake of showing something elegant if
unused. It is very easy to want to fill up the NR with snippets.

I'll make another patch and remove it from the NR directly.

Thank you for the explanation.

James

[pkx166h, 2014-08-27 11:50:58]

rebase of patch (still work to do)

[pkx166h, 2014-08-29 17:53:09]

Rebased with master and made some adjustments to the description.

[pkx166h, 2014-09-12 08:23:24]

author	James Lowe <pkx166h@gmail.com>	
	Thu, 26 Jun 2014 21:37:04 +0000 (22:37 +0100)
committer	James Lowe <pkx166h@gmail.com>	
	Fri, 12 Sep 2014 08:20:11 +0000 (09:20 +0100)
commit	a1c9c3d285a2f3e59cf79a375b67cfb58ceca7ba