@node Top, , ,
@top
-@chapter New features in 1.9 since 1.8
+@chapter New features in 2.0 since 1.8
@itemize
@item
-The @code{\newcontext} command will create a context with a unique
+@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,
+we see two versions of a piece of music, one for the full score, and
+one with cue notes for the instrumental part:
+
+@example
+< \tag #'part <
+ @{ c4 f2 g4 @} % in the part, we have cue-notes
+ \\ R1 >
+ \tag #'score R1 % in the score: only a rest
+>
+@end example
+
+The same can be applied to articulations, texts, etc.: they are
+made by prepending
+
+@example
+ -\tag #@var{your-tags}
+@end example
+
+to an articulation, for example,
+
+@example
+ c4-\tag #'with-fingerings -4 -\tag #'with-strings \6
+@end example
+
+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
+list where fingerings may be placed, eg.
+
+@example
+ \property Voice.fingeringOrientations = #'(left down)
+@end example
+
+This will put the fingering for the lowest note below the chord, and the
+rest to the left.
+
+@item
+The script previously known as @file{ly2dvi} has been renamed to
+@file{lilypond}. The binary itself is now installed as
+@file{lilypond-bin}.
+
+@item
+Markup text (ie. general text formatting) may now be used for lyrics too.
+
+@item
+Two new commands for grace notes have been added, @code{\acciaccatura}
+and @code{\appoggiatura},
+
+@example
+ \appoggiatura f8 e4
+ \acciaccatura g8 f4
+@end example
+
+Both reflect the traditional meanings of acciaccatura and appogiatura,
+and both insert insert a slur from the first grace note to the main
+note.
+
+@item
+Layout options for grace notes are now stored in a context property,
+and may now be set separately from musical content.
+
+@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 @{
- \newcontext Staff @{ @var{notes for 1st staff} @}
- \newcontext Staff @{ @var{notes for 2nd staff} @}
+ \new Staff @{ @var{notes for 1st staff} @}
+ \new Staff @{ @var{notes for 2nd staff} @}
@}
@end example
@example
PRE
- \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 ALT3 @}
+ \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, etc.
-
+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,
#(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
-@chapter New features in 1.8 since 1.6
+@chapter New features in 1.8 since 1.6
@itemize
projects / lilypond.git / blobdiff