CG: explain what big staff size means in regtests

[lilypond.git] / Documentation / snippets / demo-midiinstruments.ly

diff --git a/Documentation/snippets/demo-midiinstruments.ly b/Documentation/snippets/demo-midiinstruments.ly
index e5182b49796337d3e2737f1391c0d8ca918a58b7..fffa4acb54a6914feacfebe12a68b84501afdab9 100644 (file)
--- a/Documentation/snippets/demo-midiinstruments.ly
+++ b/Documentation/snippets/demo-midiinstruments.ly
@@ -1,10 +1,21 @@
-%% Do not edit this file; it is automatically
+%% 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.48"
+\version "2.14.2"
 
 \header {
-  lsrtags = "midi"
+  lsrtags = "specific-notation, midi, real-music"
+
+%% Translation of GIT committish: 30339cb3706f6399c84607426988b25f79b4998c
+  texidocfr = "
+Partant du problème que l'on ignore quel @code{midiInstrument} serait le
+plus adapté à sa composition, voici un fichier LilyPond de démonstration.
+
+"
+  doctitlefr = "Démonstration de MidiInstrument"
 
   texidoc = "
 Problem: How to know which @code{midiInstrument} would be best for your
@@ -16,6 +27,7 @@ composition? Solution: A LilyPond demo file.
   doctitle = "Demo MidiInstruments"
 } % begin verbatim
 
+
 \header {
   title = "Demo of all midi sounds"
   arranger = "Myself "