* lily/my-lily-lexer.cc: add \accacciatura and \appoggiatura

[lilypond.git] / Documentation / topdocs / NEWS.texi

diff --git a/Documentation/topdocs/NEWS.texi b/Documentation/topdocs/NEWS.texi
index 9dc10dc2aa913f966d31568205bb518d70a80099..60a6fa8bc4c26ece18fc7e9c97bd00eb2e80d9cf 100644 (file)
--- a/Documentation/topdocs/NEWS.texi
+++ b/Documentation/topdocs/NEWS.texi
@@ -5,8 +5,84 @@
 @node Top, , , 
 @top
 
+@chapter New features in 1.9 since 1.8
 
-@chapter        New features in 1.8 since 1.6
+@itemize
+
+@item
+Two new commands for grace note have been added, @code{\accacciatura}
+and @code{\appogiatura}. Both reflect the traditional meanings of
+accacciatura and ap
+
+
+
+@item
+The @code{\new} command will create a context with a unique
+name automatically. Hence, for multi-staff scores, it is no longer
+necessary to invent arbitrary context names. For example, a two-staff
+score may be created by
+
+@example
+  \simultaneous @{
+    \new Staff @{ @var{notes for 1st staff} @}
+    \new Staff @{ @var{notes for 2nd staff} @}
+  @}
+@end example
+
+
+
+@item
+Octave checks make octave errors easier to correct.
+The syntax is 
+
+@example
+  \octave @var{pitch}
+@end example
+
+This checks that @var{pitch} (without octave) yields @var{pitch} (with
+octave) in \relative mode. If not, a warning is printed, and the
+octave is corrected.
+
+@item
+All articulations must now be entered postfix. For example,
+
+@example
+       c8[( d8]) 
+@end example
+
+@noindent
+is a pair of beamed slurred eighth notes.
+
+@item
+The definition of @code{\relative} has been simplified.  Octaves are
+now always propagated in the order that music is entered. In the
+following example,  
+
+@example
+  PRE
+  \repeat "unfold" 3  BODY \alternative @{ ALT1 ALT2 @}
+  POST
+@end example
+
+@noindent
+the octave of BODY is based on PRE, the starting octave of ALT1 on
+BODY, the starting octave of ALT2 on ALT1, and the starting octave of
+POST on ALT2.
+
+The same mechanism is used for all other music expressions, except the
+chord. Backwards compatibility is retained through a special program option,
+which is set through 
+
+@example
+  #(ly:set-option 'old-relative)
+@end example
+
+@end itemize
+
+
+
+
+@chapter New features in 1.8 since 1.6
 
 @itemize
 
@@ -57,13 +133,13 @@ using LilyPond version 2.0.  In version 2.0, this syntax will be
 changed to
 
 @example
-  < PITCHES >  for chords
+       < PITCHES >
 @end example
 
-and
+for chords, and
 
 @example
-  \simultaneous @{ .. @} 
+       \simultaneous @{ .. @} 
 @end example
 
 for simultaneous music.
@@ -110,7 +186,7 @@ New algorithms for chord-name formatting have been installed. They
 can be tuned and have ergonomic syntax for entering exceptions.
 
 @item 
-Texts may now be put on multimeasure rests, eg.
+Texts may now be put on multimeasure rests, e.g.
 
 @example
        R1*20^\markup @{ "GP" @}
@@ -126,7 +202,7 @@ without the proper line breaking and horizontal spacing.
 Glissandi can now be printed using the zigzag style.
 
 @item 
-LilyPond can now print clusters. The syntax is:
+LilyPond can now print clusters. The syntax is
 
 @example
        \apply #notes-to-clusters @{ NOTE NOTE .. @}
@@ -142,7 +218,7 @@ syntax for this is
 
 
 @item 
-Nested horizontal brackets for music analysis can now be printed.
+Nested horizontal brackets for music analysis can now be printed:
 
 @example
        NOTE-\startGroup