New version of LSR upgrade

[lilypond.git] / Documentation / snippets / non-traditional-key-signatures.ly

diff --git a/Documentation/snippets/non-traditional-key-signatures.ly b/Documentation/snippets/non-traditional-key-signatures.ly
index 1c6b5c0f37b0a6121550ebe49d20de166791713b..270d1ce6847901a24ab26c292cdbe363d65be503 100644 (file)
--- a/Documentation/snippets/non-traditional-key-signatures.ly
+++ b/Documentation/snippets/non-traditional-key-signatures.ly
@@ -1,13 +1,14 @@
-% DO NOT EDIT this file manually; it is automatically
-% generated from Documentation/snippets/new
-% Make any changes in Documentation/snippets/new/
-% and then run scripts/auxiliar/makelsr.py
-%
-% This file is in the public domain.
-%% Note: this file works from version 2.14.0
-\version "2.14.0"
+%% DO NOT EDIT this file manually; it is automatically
+%% generated from LSR http://lsr.dsi.unimi.it
+%% Make any changes in LSR itself, or in Documentation/snippets/new/ ,
+%% and then run scripts/auxiliar/makelsr.py
+%%
+%% This file is in the public domain.
+\version "2.14.2"
 
 \header {
+  lsrtags = "version-specific, really-cool, pitches, contemporary-notation, staff-notation"
+
 %% Translation of GIT committish: 6977ddc9a3b63ea810eaecb864269c7d847ccf98
   doctitlees = "Armaduras de tonalidad no tradicionales"
   texidoces = "
@@ -114,27 +115,34 @@ Voici, par exemple, comment générer une gamme par ton :
   doctitlefr = "Armures inhabituelles"
 
 
-  lsrtags = "pitches, staff-notation"
   texidoc = "
 The commonly used @code{\\key} command sets the @code{keySignature}
 property, in the @code{Staff} context.
 
-To create non-standard key signatures, set this property directly.  The
+To create non-standard key signatures, set this property directly. The
 format of this command is a list:
 
-@code{\\set Staff.keySignature = #`(((octave . step) . alter) ((octave
-. step) . alter) ...)} where, for each element in the list,
-@code{octave} specifies the octave (0@tie{}being the octave from
-middle@tie{}C to the B above), @code{step} specifies the note within the
-octave (0@tie{}means@tie{}C and 6@tie{}means@tie{}B), and @code{alter} is
-@code{,SHARP ,FLAT ,DOUBLE-SHARP} etc.  (Note the leading comma.)
+@code{ \\set Staff.keySignature = #`(((octave . step) . alter) ((octave
+. step) . alter) ...) } where, for each element in the list,
+@code{octave} specifies the octave (0 being the octave from middle C to
+the B above), @code{step} specifies the note within the octave (0 means
+C and 6 means B), and @code{alter} is @code{,SHARP ,FLAT ,DOUBLE-SHARP}
+etc. (Note the leading comma.) The accidentals in the key signature
+will appear in the reverse order to that in which they are specified.
+
 
 Alternatively, for each item in the list, using the more concise format
-@code{(step . alter)} specifies that the same alteration should hold in all
-octaves.
+@code{(step . alter)} specifies that the same alteration should hold in
+all octaves.
+
+
+For microtonal scales where a @qq{sharp} is not 100 cents, @code{alter}
+refers to the alteration as a proportion of a 200-cent whole tone.
+
+
+Here is an example of a possible key signature for generating a
+whole-tone scale:
 
-Here is an example of a possible key signature for generating a whole-tone
-scale:
 "
   doctitle = "Non-traditional key signatures"
 } % begin verbatim