Merge branch 'master' of carldsorensen@git.sv.gnu.org:/srv/git/lilypond

[lilypond.git] / input / lsr / adding-beams,-slurs,-ties-etc.-when-using-tuplet-and-non-tuplet-rythms..ly

diff --git a/input/lsr/adding-beams,-slurs,-ties-etc.-when-using-tuplet-and-non-tuplet-rythms..ly b/input/lsr/adding-beams,-slurs,-ties-etc.-when-using-tuplet-and-non-tuplet-rythms..ly
index 899d2503f5583fe6b9d9b7a2e0111610b1df5f48..8b071c58e099fbf8d27ce4a4024a3351ef62f887 100644 (file)
--- a/input/lsr/adding-beams,-slurs,-ties-etc.-when-using-tuplet-and-non-tuplet-rythms..ly
+++ b/input/lsr/adding-beams,-slurs,-ties-etc.-when-using-tuplet-and-non-tuplet-rythms..ly
@@ -1,10 +1,27 @@
 %% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
 %% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.

-\version "2.11.38"
+\version "2.11.62"

 
 \header {
   lsrtags = "rhythms, expressive-marks"
 
 \header {
   lsrtags = "rhythms, expressive-marks"

- texidoc = "
+
+  texidoces = "
+La sintaxis de LilyPond puede implicar muchas colocaciones poco
+comunes para los paréntesis, corchetes, etc, que a veces se tienen
+que intercalar. Por ejemplo, al introducir una barra manual, el
+corchete izquierdo de apertura se debe escribir después de la nota
+inicial y de su duración, no antes. De forma similar, el corchete
+derecho de cierre debe seguir inmediatamente a la nota que se
+quiere situar al final del barrado, incluso si esta nota resulta
+estar dentro de un grupo de valoración especial. Este fragmento de
+código muestra cómo combinar el barrado manual, las ligaduras de
+expresión y de unión y las ligaduras de fraseo, con secciones de
+valoración especial (encerradas entre llaves).
+
+"
+  doctitlees = "Añadir barras, ligaduras de expresión y de unión, etc. cuando se usan ritmos con y sin grupos de valoración especial."
+
+  texidoc = "

 LilyPond syntax can involve many unusual placements for parentheses,
 brackets etc., which might sometimes have to be interleaved. For
 example, when entering a manual beam, the left square bracket has to be
 LilyPond syntax can involve many unusual placements for parentheses,
 brackets etc., which might sometimes have to be interleaved. For
 example, when entering a manual beam, the left square bracket has to be


@@ -14,11 +31,14 @@ at the end of the requested beaming, even if this note happens to be
 inside a tuplet section. This snippet demonstrates how to combine
 manual beaming, manual slurs, ties and phrasing slurs with tuplet
 sections (enclosed within curly braces). 
 inside a tuplet section. This snippet demonstrates how to combine
 manual beaming, manual slurs, ties and phrasing slurs with tuplet
 sections (enclosed within curly braces). 

-" }
-% begin verbatim
+
+"
+  doctitle = "Adding beams, slurs, ties etc. when using tuplet and non-tuplet rythms."
+} % begin verbatim

 {
   r16[ g16 \times 2/3 { r16 e'8] }
   g16( a \times 2/3 { b d e') }
   g8[( a \times 2/3 { b d') e']~ }
 {
   r16[ g16 \times 2/3 { r16 e'8] }
   g16( a \times 2/3 { b d e') }
   g8[( a \times 2/3 { b d') e']~ }

+  \time 2/4

   \times 4/5 { e'32\( a b d' e' } a'4.\)
 }
   \times 4/5 { e'32\( a b d' e' } a'4.\)
 }