Merge remote-tracking branch 'origin/stable/2.16' into translation

[lilypond.git] / Documentation / changes.tely

diff --git a/Documentation/changes.tely b/Documentation/changes.tely
index e1c05e52c8befbc4c9cf4c9068c71af828995596..83db4ea85980a7ba7bc1dc1b0d02b5ec5e8b3917 100644 (file)
--- a/Documentation/changes.tely
+++ b/Documentation/changes.tely
@@ -60,6 +60,43 @@ which scares away people.
 * only show user-visible changes.
 
 @end ignore
+@item
+Support for cross-staff stems on chords, using @code{crossStaff}
+and the @code{Span_stem_engraver}.  This calculates the length of
+cross-staff stems automatically.
+@lilypondfile[quote]
+{cross-staff-stems.ly}
+
+@item
+The syntax of words (character sequences recognized without enclosing
+quotes) and commands (now always a backslash @samp{\} followed by a
+word) has been unified across all modes: it now consists of alphabetic
+characters, possibly enclosing isolated dashes @samp{-} and underlines
+@samp{_}.
+
+As one consequence, using unquoted text scripts like (literally!)
+@example
+@{ c-script c\f_script @}
+@end example
+will now tend to result in invalid music.  Omitting quote marks
+for arbitrary text rather than keywords has never been good practice or
+even documented, and it is unlikely to have seen significant use.
+
+Staying with established conventions (like not using dashes or
+underlines for command names intended to be used inside of music)
+remains advisable.  The reason for this change is more robust
+recognition of LilyPond's lexical units for LilyPond itself as well as
+external tools interpreting its syntax.
+
+@item
+Support for Kievan square notation:
+@lilypond[quote,relative=1,verbatim]
+\new KievanVoice {
+  \cadenzaOn
+  c d e f g a bes
+  \bar "kievan"
+}
+@end lilypond
 
 @item
 Augmentation dots now avoid the other voice in two-voice polyphony
@@ -219,6 +256,11 @@ reduces the containing expression, greatly reducing the potential for
 premature evaluation.  There are also @q{splicing} operators @code{$@@}
 and @code{#@@} for interpreting the members of a list individually.
 
+@item
+To reduce the necessity for using @code{$}, Scheme expressions written
+with @code{#} are interpreted as music inside of music lists, and as
+markups or markup lists inside of markups.
+
 @item
 Support for jazz-like chords has been improved: Lydian and altered
 chords are recognised; separators between chord modifiers are now