Issue 5167/6: Changes: show \markup xxx = ... \etc assignments

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

diff --git a/Documentation/snippets/demo-midiinstruments.ly b/Documentation/snippets/demo-midiinstruments.ly
index d0e33381d6e7c808bfc7146844fed9805730905e..44199d8fd9f40b78a02714d5e84cfd0f57bb8f93 100644 (file)
--- a/Documentation/snippets/demo-midiinstruments.ly
+++ b/Documentation/snippets/demo-midiinstruments.ly
@@ -1,21 +1,13 @@
 %% DO NOT EDIT this file manually; it is automatically
-%% generated from LSR http://lsr.dsi.unimi.it
+%% generated from LSR http://lsr.di.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.14.2"
+\version "2.18.0"
 
 \header {
-%% 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"
-
-  lsrtags = "specific-notation, real-music, midi"
+  lsrtags = "midi, real-music, specific-notation"
 
   texidoc = "
 Problem: How to know which @code{midiInstrument} would be best for your
@@ -27,7 +19,6 @@ composition? Solution: A LilyPond demo file.
   doctitle = "Demo MidiInstruments"
 } % begin verbatim
 
-
 \header {
   title = "Demo of all midi sounds"
   arranger = "Myself "
@@ -185,4 +176,3 @@ melody = {
   >>
   \midi { }
 }
-