Merge branch 'lilypond/translation' of ssh://git.sv.gnu.org/srv/git/lilypond into...

[lilypond.git] / Documentation / snippets / changing-midi-output-to-one-channel-per-voice.ly

diff --git a/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly b/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
index fe187f48c6e070f293f89be85b933641e25bd0b3..fc44d16399c5b39c2b92278900f615bfbb011dd8 100644 (file)
--- a/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
+++ b/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
@@ -1,11 +1,12 @@
-%% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
+%% 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.1"
+\version "2.13.20"
 
 \header {
   lsrtags = "contexts-and-engravers, midi"
 
-%% Translation of GIT committish: b2d4318d6c53df8469dfa4da09b27c15a374d0ca
+%% Translation of GIT committish: 0b55335aeca1de539bf1125b717e0c21bb6fa31b
   texidoces = "
 Al producir una salida MIDI, el comportamiento predeterminado es
 que cada pentagrama representa un canal MIDI, con todas las voces
@@ -33,7 +34,7 @@ However, by moving the @code{Staff_performer} to the @code{Voice}
 context, each voice on a staff can have its own MIDI channel, as is
 demonstrated by the following example: despite being on the same staff,
 two MIDI channels are created, each with a different
-@code{midiInstrument}. 
+@code{midiInstrument}.
 
 "
   doctitle = "Changing MIDI output to one channel per voice"
@@ -68,7 +69,7 @@ two MIDI channels are created, each with a different
     }
     \context {
       \Voice
-      \consists "Staff_performer"      
+      \consists "Staff_performer"
     }
     \context {
       \Score