Set the sequence name in MIDI using title information from \header block

Documentation/changes.tely

 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
 @setfilename lilypond-changes.info
 @settitle LilyPond Changes
 
 @include macros.itexi
 
 @ifhtml
 @macro inputfileref{DIR,NAME}
 @uref{../../\DIR\/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
 @end macro
@@ skipping 42 matching lines @@
 * try to be as brief possible in those cases
 
 * don't try to provide real-world examples, they often get too big,
 which scares away people.
 
 * Write complete sentences.
 
 * only show user-visible changes.
 
 @end ignore
+
+@item
+When outputting MIDI, LilyPond will now store the @code{title}
+defined in a score's @code{\header} block (or, if there is no
+such definition on the @code{\score} level, the first such
+definition found in a @code{\header} block of the score's
+enclosing @code{\bookpart}, @code{\book}, or top-level scope)
+as the name of the MIDI sequence in the MIDI file.  Optionally,
+the name of the MIDI sequence can be overridden using the new
+@code{midititle} @code{\header} field independently of
+@code{title} (for example, in case @code{title} contains markup
+code which does not render as plain text in a satisfactory way
+automatically).
 
 @item
 Music (and scheme and void) functions and markup commands that
 just supply the final parameters to a chain of overrides, music
 function and markup command calls can now be defined in the form
 of just writing the expression cut short with @code{\etc}.
 
 @lilypond[verbatim,quote]
 bold-red-markup = \markup \bold \with-color #red \etc
 highlight = \tweak font-size 3 \tweak color #red \etc
@@ skipping 590 matching lines @@
 @ifhtml
 For older news, go to
 @uref{http://lilypond.org/doc/v2.18/Documentation/changes/},
 @uref{http://lilypond.org/doc/v2.16/Documentation/changes/},
 or @uref{../,go back} to the Documentation index.
 
 
 @end ifhtml
 
 @bye