LSR: Update.

[lilypond.git] / Documentation / snippets / tweaking-clef-properties.ly

diff --git a/Documentation/snippets/tweaking-clef-properties.ly b/Documentation/snippets/tweaking-clef-properties.ly
index 24ebee018ee5af25cab13c9dc36240f7b21e0801..a68e83363c109982a0345fc5f0edc00b33061c7b 100644 (file)
--- a/Documentation/snippets/tweaking-clef-properties.ly
+++ b/Documentation/snippets/tweaking-clef-properties.ly
@@ -1,6 +1,7 @@
-%% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
+%% Do not edit this file; it is automatically
+%% generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
-\version "2.13.1"
+\version "2.13.4"
 
 \header {
   lsrtags = "pitches, staff-notation, tweaks-and-overrides"
@@ -39,7 +40,8 @@ ajustan estas propiedades manualmente.  En la primera línea, los
 cambios manuales preservan el posicionamiento relativo estándar de
 las claves y las notas, pero no lo hacen en la segunda línea.
 "
-  
+
+
 %% Translation of GIT committish: d96023d8792c8af202c7cb8508010c0d3648899d
   doctitlede = "Eigenschaften des Schlüssels optimieren"
   texidocde = "
@@ -101,7 +103,7 @@ with  @code{\\unset Staff.explicitClefVisibility}.
 The following examples show the possibilities when setting these
 properties manually. On the first line, the manual changes preserve the
 standard relative positioning of clefs and notes, whereas on the second
-line, they do not. 
+line, they do not.
 
 "
   doctitle = "Tweaking clef properties"
@@ -149,7 +151,7 @@ line, they do not.
   \set Staff.clefOctavation = #0
   \set Staff.clefPosition = #0
   c'1
-  
+
   % Return to the normal clef:
 
   \set Staff.middleCPosition = #0