lilypond-devel
[Top][All Lists]
Advanced

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

Re: Doc: NR Pitches.itely - added 2 new snippets (issue 110240044 by add


From: Keith OHara
Subject: Re: Doc: NR Pitches.itely - added 2 new snippets (issue 110240044 by address@hidden)
Date: Mon, 30 Jun 2014 23:56:29 -0700
User-agent: Opera Mail/12.16 (Win32)

On Mon, 30 Jun 2014 14:40:17 -0700, <address@hidden> 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/pitches.itely#newcode1325
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.




reply via email to

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