@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
changed to
@example
- < PITCHES > for chords
+ < PITCHES >
@end example
-and
+for chords, and
@example
- \simultaneous @{ .. @}
+ \simultaneous @{ .. @}
@end example
for simultaneous music.
@example
\applyoutput #SCHEME-FUNCTION
@end example
+
+@noindent
SCHEME-FUNCTION takes a single argument, and is called for every grob
that is created in the current context.
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" @}
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 .. @}
@item
-Nested horizontal brackets for music analysis can now be printed.
+Nested horizontal brackets for music analysis can now be printed:
@example
NOTE-\startGroup
@chapter New features in 1.6 since 1.4
+@itemize @bullet
+@item
Support for figured bass and tablature.
+@item
Completely rewritten beam formatting: provides much better output
now.
+
+@item
Completely revised and improved music font.
+
+@item
Completely rewritten MIDI import support.
+@item
Completely rewritten grace note support. Practically speaking this
means that grace notes can be slurred to normal normal notes.
+
+@item
Improved accidental handling and formatting: styles for producing
cautionaries may vary, and complex collisions between accidentals of a
chord are handled much better.
+@item
Better spacing: both globally and locally. This includes subtle
details like optical stem spacing.
+@item
More support for ancient notation: mensural ligatures, ambitus
(pitch range) of voices, more shapes, etc.
+@item
More support for piano notation: bracket pedals, directed arpeggios,
arpeggio brackets.
+@item
Easier music polyphonic music entry.
+@item
More extensibility, many speedups and bugfixes
+@item
The manual has been thoroughly revised.
+@item
Development is now hosted at http://savannah.gnu.org, and sources
can be downloaded through anonymous CVS.
+@item
Support for windows: LilyPond is part of the cygwin distribution,
which comes with a user-friendly installer.
+@end itemize