Split WWW target in two stages WWW-1 and WWW-2

[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 df5a0713d5590e5db401a87986146cc56e7e5b59..f27b5673f45c0f3e6fb12a58ca81eb71c61c2e7f 100644 (file)
--- a/input/lsr/non-traditional-key-signatures.ly
+++ b/input/lsr/non-traditional-key-signatures.ly
@@ -1,31 +1,39 @@
 %% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
-%% Tags: pitches, staff-notation
-\version "2.11.35"
+\version "2.11.46"
 
-\header { texidoc = "
+\header {
+  lsrtags = "pitches, staff-notation"
+
+  texidoc = "
 The commonly used @code{\\key} command sets the @code{keySignature}
-property, in the @code{Staff} context. However, non-standard key
-signatures can be specified by setting 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, octave specifies the octave (0 being the
-octave from middle C to the B above), step specifies the note within
-the octave (0 means C and 6 means B), and alter is ,SHARP ,FLAT
-,DOUBLE-SHARP etc. (Note the leading comma.)
+property, in the @code{Staff} context.
+
+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 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.)
 
-However, for each item in the list, you can also use the alternative
-format (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))
-  c d e fis aes bes c2
+  \set Staff.keySignature = #`(((0 .  3) . ,SHARP) ((0 . 5) . ,FLAT) ((0 . 6) . ,FLAT))
+  c4 d e fis
+  aes4 bes c2
 }