X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fchanges.tely;h=e69766caccdd2b537760b52fe00e5fff873ae262;hb=41ea9977859eb47c59d79022609f0df536cbd81a;hp=058a0d5c0edfb29cba348b0f786727ec5b268c2e;hpb=743f0d4b067e76d591487f085240a7ff9ace85a7;p=lilypond.git

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index 058a0d5c0e..e69766cacc 100644
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,25 @@ which scares away people.
 
 @end ignore
 
+@item
+Use of @code{\tempo} specifications in @code{\midi} blocks (removed in
+2.9.16 in favor of explicit @code{tempoWholesPerMinute} settings) has
+seen a revival: now any kind of property-setting music is turned into
+context definitions within of output specifications, allowing for
+declarations like
+@example
+\layout @{ \accidentalStyle modern @}
+\midi @{ \tempo 4. = 66 @}
+@end example
+
+@item
+The LilyPond G clef has been redesigned - upper loop is now more balanced,
+bottom crook sticks out less and the "spine" (main vertical line) is more
+evenly curved. The old and new versions can be compared by looking at the
+documentation:
+@uref{http://lilypond.org/doc/v2.14/Documentation/notation/the-feta-font.html#clef-glyphs, old version},
+@uref{http://lilypond.org/doc/v2.15/Documentation/notation/the-feta-font.html#clef-glyphs, new version}.
+
 @item
 Lilypond's stencil commands have been simplified to allow for less code
 duplication and better height approximations of graphical objects.  The
@@ -119,33 +138,32 @@ the Scheme function @code{event-chord-wrap!}  converts to the old
 representation; using one of those might be easiest for keeping legacy
 code operative.
 
-The advantages of making input and music match more closely are
-numerous: music functions previously worked differently when used inside
-or outside of chords.  Now they are the same, including all the
-possibilities of argument parsing.  You can now use music variables
-inside of chords: a construct like
+The following three items are consequences of this change.
+
+@item
+Music functions now work the same when used inside or outside of chords,
+including all the possibilities of argument parsing.  Music variables
+can be used inside of chords: a construct like
 @lilypond[verbatim,quote,ragged-right]
 tonic=fis'
 { <\tonic \transpose c g \tonic> }
 @end lilypond
 @noindent
-would have been unthinkable previously.  You can use
-@code{#@{@dots{}#@}} for constructing chord constituents.  Music
-functions inside of chords are no longer specially treated and thus
-accept the same arguments as outside of chords.  @code{\tweak} now works
-on single notes without needing to wrap them in a chord.  In theory, it
-can also work on command events and lyrics now.  Since that was not
-possible before, it depends on luck on a case-by-case basis whether the
-tweak internals are already receiving the necessary information.  Users
-are asked to report those cases where they find @code{\tweak} not
-working according to reasonable expectations.
+now works as expected.  One can use @code{#@{@dots{}#@}} for
+constructing chord constituents.  @code{\tweak} now works on single
+notes without needing to wrap them in a chord.  Using it on command
+events and lyrics is now possible, but not likely to give results yet.
+
+@item
+The repetitive chord entry aid @code{q} has been reimplemented.
+Repeated chords are now replaced right before interpreting a music
+expression.  In case the user wants to retain some events of the
+original chord, he can run the repeat chord replacement function
+@code{\chordRepeats} manually.
 
 @item
-As one consequence, it was possible to reimplement the repetitive chord
-entry aid @code{q}.  Repeated chords are now replaced right before
-interpreting a music expression.  In case the user wants to retain
-some events of the original chord, he can run the repeat chord
-replacement function @code{\chordRepeats} manually.
+String numbers and right hand fingerings on single notes now appear
+without having to be written inside of chord brackets.
 
 @item
 Scheme expressions inside of embedded Lilypond (@code{#@{@dots{}#@}})
@@ -252,9 +270,8 @@ expression or just the music event itself, respectively.
 
 @item
 Pitches can be used on the right side of assignments.  They are
-distinguished from single note events by the absence of a duration by
-the absence of a duration or other information that can't be part of a
-pitch.
+distinguished from single note events by the absence of a duration or
+other information that can't be part of a pitch.
 
 @item
 New command-line option @option{--loglevel=@var{level}} to control how much output