1 \input texinfo @c -*-texinfo-*-
9 @unnumbered New features in 2.5 since 2.4
12 @macro inputfileref{DIR,NAME}
13 @uref{../../../\DIR\/out-www/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
15 @macro usermanref{NAME}
16 @inforef{\NAME\,,../../user/out-www/lilypond/lilypond}@c
21 @macro inputfileref{DIR,NAME}
24 @macro usermanref{NAME}
25 See user manual, \NAME\
34 Point and click editing is now supported in the PS/PDF backend as
38 @uref{../../user/out-www/lilypond/Point-and-click.html,Point and click}
41 the section Point and click in he user manual.
46 With the new @code{tieWaitForNote} property, arpeggios may be written
47 out using ties, for example,
49 @lilypond[fragment,verbatim,relative=1,raggedright]
50 \set tieWaitForNote = ##t
51 \grace { c16[~ e~ g]~ } <c, e g>4
54 Thanks to Steve Doonan for funding development of this feature.
57 Individual objects may be assigned colors, for example,
59 @lilypond[fragment,relative=1,verbatim,raggedright]
60 \override NoteHead #'color = #red
65 The PostScript backend is now used by default. This backend requires
66 less machinery to run, and gives more consistent results.
68 Due bugs in GhostScript's PDF handling, it is recommended to upgrade
72 Separator slashes may be inserted between systems in a score. For an
73 example, see @inputfileref{input/regression,system-separator.ly}:
76 Locations of errors in the input are now calculated more precisely.
79 LilyPond now uses Pango and FontConfig for selecting and rendering
80 UTF-8 input in non-@TeX{} backends. A font may be selected by using a
84 \override TextScript #'font-name = #"Serif"
89 or using the classic font selection mechanism
92 \override TextScript #'font-family = #'roman
93 \override TextScript #'font-series = #'bold
96 Any Type1 and TrueType font recognized by FontConfig is available in
100 Metrics of blocks of text can be retrieved from (La)@TeX{} directly,
101 using the @code{-f texstr} output backend. This provides exact metrics
102 for texts, including kerning and accents.
105 LilyPond now uses FreeType read the Feta font as an OpenType
106 font. This is cleaner design and more robust. A recent version of
107 FontForge (11122004 or newer) and Freetype is required.
109 As a result, the SVG backend is now a fully functional backend.
112 A new script, @code{\espressivo} has been added, for a combination of
113 crescendo and decrescendo on a single note.
116 In markups, expressions stacked with @code{\column},
117 @code{\center-align}, etc, are not grouped with @code{< ... >} anymore,
118 but with @code{@{ ... @}}, eg:
121 \line @{ first line @}
122 \line @{ second line @}
127 LilyPond will now avoid line breaks that cause long texts to stick
128 outside of the page staff.
131 Grace notes following a main note, used to be entered by letting the
132 grace notes follow a skip in a parallel expression, for example,
136 { s2 \grace { c16[ d] } } >>
141 This can now be shortened by doing
144 \afterGrace @{ d1 @} @{ c16[ d] @}
148 Pagebreaks can now be forced or forbidden after title blocks. This is
149 achieved by setting @code{breakbefore} in the @code{\header} block to
153 Shaped note heads. This feature has been sponsored by Jonathan Walther,
155 @lilypond[relative=1,fragment,verbatim,raggedright]
156 \set shapeNoteStyles = ##(do re mi fa #f la ti)
157 c d e f g a b c d e f g a b c
161 Layout for titles, page header and footer can now be entered as
162 @code{\markup} commands.
164 @item Positioning of slurs can now be adjusted manually
166 @item Grace notes are correctly quoted and formatted when using cue notes.
168 @item Cue notes can now be created with
171 \cueDuring #@var{voice-name} #@var{direction} @{ @var{music} @}
175 This will set stem directions and put the cue notes in the @code{cue}
179 @item Stemlets, short stems over beamed rests, have been added.
181 @lilypond[relative=1,verbatim,fragment,raggedright]
182 \override Stem #'stemlet-length = #0.75
189 For older news, go to
190 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.