Merge branch 'master' into lilypond/translation

[lilypond.git] / Documentation / es / user / templates.itely

diff --git a/Documentation/es/user/templates.itely b/Documentation/es/user/templates.itely
index 43f26c177ab622dd47318a7e2e8943c139ec48b2..2861410054f6471cd560982149612df2ab4938da 100644 (file)
--- a/Documentation/es/user/templates.itely
+++ b/Documentation/es/user/templates.itely
@@ -1,7 +1,7 @@
 @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*-
 @c This file is part of lilypond-learning.tely
 @ignore
-    Translation of GIT committish: 0646758d26f727fc27fc13a87df2362388909e5d
+    Translation of GIT committish: 19841b86e54ac60d93af1150c31b7c246741ce1c
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  See TRANSLATION for details.
@@ -22,6 +22,7 @@ unas hermosas partituras impresas!
 * Piano templates::
 * String quartet::
 * Vocal ensembles::
+* Orchestral templates::
 * Ancient notation templates::
 * Jazz combo::
 * lilypond-book templates::
@@ -110,6 +111,14 @@ unas hermosas partituras impresas!
 {vocal-ensemble-template-with-lyrics-aligned-below-and-above-the-staves.ly}
 
 
+@node Orchestral templates
+@appendixsec Orchestral templates
+
+@appendixsubsec Orchestra, choir and piano
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
+{orchestra,-choir-and-piano-template.ly}
+
+
 @c bad node name to avoid node name conflict
 @node Ancient notation templates
 @appendixsec Ancient notation templates