Style: clarify "do nothing" macro with {};

[lilypond.git] / Documentation / snippets / displaying-grob-ancestry.ly

diff --git a/Documentation/snippets/displaying-grob-ancestry.ly b/Documentation/snippets/displaying-grob-ancestry.ly
index 3484a7f9b21120769c6bab8e778e82a12e7dfa77..a13e95523076ba8c793960de077766e35d07aae3 100644 (file)
--- a/Documentation/snippets/displaying-grob-ancestry.ly
+++ b/Documentation/snippets/displaying-grob-ancestry.ly
@@ -2,12 +2,12 @@
 % generated from Documentation/snippets/new
 % This file is in the public domain.
 %% Note: this file works from version 2.13.10
-\version "2.13.18"
+\version "2.13.31"
 
 \header {
-%% Translation of GIT committish: ee2fdacf2ff3acd7e6fb7c4005dfe698b1cc4eed
+%% Translation of GIT committish: 0b55335aeca1de539bf1125b717e0c21bb6fa31b
 
-  texidoc = "
+  texidoces = "
 Al trabajar con los callbacks de un grob, puede ser de mucha ayuda
 entender el @qq{árbol genealógico} de un grob.  La mayor parte de los
 grobs tienen @qq{padres} que influyen en el posicionamiento del grob.
@@ -73,7 +73,7 @@ NoteHead X,Y: NoteColumn
 
 "
 
-  doctitle = "Imprimir el árbol genealógico de un grob"
+  doctitlees = "Imprimir el árbol genealógico de un grob"
 
   lsrtags = "tweaks-and-overrides"
 
@@ -107,8 +107,7 @@ The concept of @qq{generations} is misleading.
 
 
 For example, the @code{System} grob can be both parent (on the Y-side)
-and grandparent (twice on the X-side) to a @code{VerticalAlignment} % begin verbatim
-
+and grandparent (twice on the X-side) to a @code{VerticalAlignment}
 grob.
 
 
@@ -147,7 +146,8 @@ NoteHead X,Y: NoteColumn
 
 "
   doctitle = "Displaying grob ancestry"
-}
+} % begin verbatim
+
 
 #(define (grob-name grob)
    (if (ly:grob? grob)