Merge branch 'stable/2.16' into staging

[lilypond.git] / Documentation / snippets / creating-real-parenthesized-dynamics.ly

diff --git a/Documentation/snippets/creating-real-parenthesized-dynamics.ly b/Documentation/snippets/creating-real-parenthesized-dynamics.ly
index 6095e1cec33bdc6ee7a1a691931c13e8247f4c76..8f43bbff62eba84b0a0be51295af0d490a6178d2 100644 (file)
--- a/Documentation/snippets/creating-real-parenthesized-dynamics.ly
+++ b/Documentation/snippets/creating-real-parenthesized-dynamics.ly
@@ -1,28 +1,13 @@
-%% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
+%% DO NOT EDIT this file manually; it is automatically
+%% generated from LSR http://lsr.dsi.unimi.it
+%% Make any changes in LSR itself, or in Documentation/snippets/new/ ,
+%% and then run scripts/auxiliar/makelsr.py
+%%
 %% This file is in the public domain.
-\version "2.13.1"
+\version "2.16.0"
 
 \header {
-  lsrtags = "expressive-marks, text"
-
-%% Translation of GIT committish: b2d4318d6c53df8469dfa4da09b27c15a374d0ca
-  texidoces = "
-Aunque la manera más fácil de añadir paréntesis a una indicación
-de dinámica es utilizar un bloque @code{\\markup}, este método
-tiene un inconveniente: los objetos que se crean se comportarán
-como elementos de marcado de texto y no como indicaciones
-dinámicas.
-
-Sin embargo, es posible crear un objeto similar utilizando el
-código de Scheme equivalente (como se explica en \"Interfaz del
-programador de elementos de marcado\"), en combinación con la
-función @code{make-dynamic-script}. De esta forma, el elemento de
-marcado se tratará como una indicación dinámica, y por tanto
-seguirá siendo compatible con instrucciones como
-@code{\\dynamicUp} o @code{\\dynamicDown}.
-
-"
-  doctitlees = "Crear indicaciones dinámicas \"verdaderas\" entre paréntesis"
+  lsrtags = "expressive-marks, text, workaround"
 
   texidoc = "
 Although the easiest way to add parentheses to a dynamic mark is to use
@@ -30,9 +15,9 @@ a @code{\\markup} block, this method has a downside: the created
 objects will behave like text markups, and not like dynamics.
 
 However, it is possible to create a similar object using the equivalent
-Scheme code (as described in \"Markup programmer interface\"), combined
-with the @code{make-dynamic-script} function. This way, the markup will
-be regarded as a dynamic, and therefore will remain compatible with
+Scheme code (as described in the Notation Reference), combined with the
+@code{make-dynamic-script} function. This way, the markup will be
+regarded as a dynamic, and therefore will remain compatible with
 commands such as @code{\\dynamicUp} or @code{\\dynamicDown}.
 
 
@@ -41,13 +26,11 @@ commands such as @code{\\dynamicUp} or @code{\\dynamicDown}.
   doctitle = "Creating \"real\" parenthesized dynamics"
 } % begin verbatim
 
-\paper { ragged-right = ##t }
 
 parenF = #(make-dynamic-script (markup #:line (#:normal-text #:italic
            #:fontsize 2 "(" #:hspace -0.8 #:dynamic "f" #:normal-text
-           #:italic #:fontsize 2 ")"
-          )))
+           #:italic #:fontsize 2 ")")))
+
 \relative c'' {
   c4\parenF c c \dynamicUp c\parenF
 }
-