LSR: update.

[lilypond.git] / input / lsr / non-traditional-key-signatures.ly

diff --git a/input/lsr/non-traditional-key-signatures.ly b/input/lsr/non-traditional-key-signatures.ly
index dd350da1dade83357803ec7da2de1c743b730171..0d614ba8d14856e3b11e0fc7989a71766d52870e 100644 (file)
--- a/input/lsr/non-traditional-key-signatures.ly
+++ b/input/lsr/non-traditional-key-signatures.ly
@@ -1,15 +1,16 @@
 %% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
-\version "2.11.38"
+\version "2.11.48"
 
 \header {
   lsrtags = "pitches, staff-notation"
- texidoc = "
+
+  texidoc = "
 The commonly used @code{\\key} command sets the @code{keySignature}
 property, in the @code{Staff} context.
 
-For non-standard key signatures, you can set this property directly.
-The format of this command is a list:
+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,
@@ -19,18 +20,20 @@ C and 6 means B), and @code{alter} is @code{,SHARP ,FLAT ,DOUBLE-SHARP}
 etc. (Note the leading comma.)
 
 
-However, for each item in the list, you can also use the alternative
-format @code{(step . alter)}, which specifies that the same alteration
-should hold in all octaves.
+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.
 
 
 Here is an example of a possible key signature for generating a
 whole-tone scale: 
-" }
-% begin verbatim
+
+"
+  doctitle = "Non-traditional key signatures"
+} % begin verbatim
 \relative c' {
   \set Staff.keySignature = #`(((0 .  3) . ,SHARP) ((0 . 5) . ,FLAT) ((0 . 6) . ,FLAT))
   c4 d e fis
-  aes bes c2
+  aes4 bes c2
 }