doc: add G clef change to Changes

[lilypond.git] / Documentation / changes.tely

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index b35850445f77f86ae89c3dfa430e1c923a63ee5f..b3fe430955eb778f9f8f932c832d8945d433ec8a 100644 (file)
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -61,6 +61,14 @@ which scares away people.
 
 @end ignore
 
+@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
@@ -114,11 +122,16 @@ representation: Rhythmic events like @code{LyricEvent} and
 @code{NoteEvent} are no longer wrapped in @code{EventChord} unless they
 have been actually entered as part of a chord in the input.  If you
 manipulate music expressions in Scheme, the new behavior may require
-changes in your code.  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
+changes in your code.  Calling the music function @code{\eventChords} or
+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
 @lilypond[verbatim,quote,ragged-right]
 tonic=fis'
 { <\tonic \transpose c g \tonic> }
@@ -247,9 +260,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