* mf/GNUmakefile: always trace pfa fonts.

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

diff --git a/Documentation/topdocs/NEWS.texi b/Documentation/topdocs/NEWS.texi
index 016a325b0722430076ade16e65b568149d9e37c0..bae8da8d130bd2b6d4cf942c4592702e169db74f 100644 (file)
--- a/Documentation/topdocs/NEWS.texi
+++ b/Documentation/topdocs/NEWS.texi
@@ -5,10 +5,75 @@
 @node Top, , , 
 @top
 
-@chapter New features in 1.9 since 1.8
+@chapter New features in 2.0 since 1.8
 
 @itemize
 
+@item
+@c dotted or dashed?
+Crescendos can now be drawn dotted or stippled.
+
+@item
+Quarter tones are now supported. They are entered by suffixing
+@code{ih} for a half-sharp and @code{eh} for a half-flat. Hence, the
+following is an ascending list of pitches:
+
+@example
+  ceses ceseh ces ceh c cih cis cisih cisis
+@end example
+
+@item
+The following constructs have been removed from the syntax:
+
+@example
+  \duration #SCHEME-DURATION
+  \pitch #SCHEME-PITCH
+  \outputproperty @var{func} @var{symbol} = @var{value}
+@end example
+
+For @code{\outputproperty}, the following may be substituted:
+
+@example
+   \applyoutput #(outputproperty-compatibility @var{func}
+                  @var{symbol} @var{value}) 
+@end example 
+
+@item
+Clefs may now be transposed arbitrarily, for example
+
+@example
+  \clef "G_8"
+  \clef "G_15"
+  \clef "G_9"
+@end example
+
+
+@item
+The syntax for chords and simultaneous music have changed.
+Chords are entered as
+
+@example
+   <@var{pitches}>
+@end example
+
+while simultaneous music is entered as
+
+@example
+   <<@var{..music list..}>>
+@end example
+
+In effect, the meanings of both have been swapped relative to their 1.8
+definition.  The syntax for lists in @code{\markup} has changed
+alongside, but figured bass mode was not  changed, i.e.:
+
+@example
+  \markup @{ \center <@var{..list of markups..}> @}
+  \figure @{ <@var{figures> @}
+@end example
+
+As chords the more often used than simultaneous music, this change will
+save keystrokes.
+
 @item
 Each music expression can now be tagged, to make different printed
 versions from the same music expression.  In the following example,
@@ -17,7 +82,7 @@ one with cue notes for the instrumental part:
 
 @example
 < \tag #'part <
-  @{ c4 f2 g @}      % in the part, we have cue-notes  
+  @{ c4 f2 g4 @}      % in the part, we have cue-notes  
   \\ R1 >
   \tag #'score R1  % in the score: only a rest
 >
@@ -36,8 +101,8 @@ to an articulation, for example,
         c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
 @end example
 
-This defines a note, which has a fingering and a string-number
-indication. 
+This defines a note, which has a conditional fingering and a
+string-number indication.
 
 @item
 The settings for chord-fingering are more flexible. You can specify a
@@ -136,6 +201,10 @@ which is set through
   #(ly:set-option 'old-relative)
 @end example
 
+@item
+Windows users can double click a @code{.ly} file to process and view
+it automagically through the new @code{lily-wins} frontend.
+
 @end itemize