Doc: 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 b3e7d618e93dd74e22be3d7870901a091e838306..e413f01940b69e92fae839b672143547515ae331 100644 (file)
--- a/Documentation/snippets/tweaking-clef-properties.ly
+++ b/Documentation/snippets/tweaking-clef-properties.ly
@@ -1,12 +1,12 @@
 %% 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.4"
+\version "2.13.16"
 
 \header {
   lsrtags = "pitches, staff-notation, tweaks-and-overrides"
 
-%% Translation of GIT committish: b2d4318d6c53df8469dfa4da09b27c15a374d0ca
+%% Translation of GIT committish: 00ef2ac3dd16e21c9ffdffaa4d6d043a3f1a76e6
   doctitlees = "Trucaje de las propiedades de clave"
   texidoces = "
 La instrucción @code{\\clef \"treble_8\"} equivale a un ajuste de
@@ -140,7 +140,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"
@@ -188,7 +188,7 @@ line, they do not.
   \set Staff.clefOctavation = #0
   \set Staff.clefPosition = #0
   c'1
-  
+
   % Return to the normal clef:
 
   \set Staff.middleCPosition = #0