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
18 @macro inputfileref{DIR,NAME}
26 With the new @code{tieWaitForNote} property, arpeggios may be written
27 out using ties, for example,
29 @lilypond[fragment,verbatim,relative=1,raggedright]
30 \set tieWaitForNote = ##t
31 \grace { c16[~ e~ g]~ } <c, e g>4
34 Thanks to Steve Doonan for funding development of this feature.
37 Individual objects may be assigned colors, for example,
39 @lilypond[fragment,relative=1,verbatim,raggedright]
40 \override NoteHead #'color = #red
45 The PostScript backend is now used by default. This backend requires
46 less machinery to run, and gives more consistent results.
48 Due bugs in GhostScript's PDF handling, it is recommended to upgrade
52 Separator slashes may be inserted between systems in a score. For an
53 example, see @inputfileref{input/regression,system-separator.ly}:
56 Locations of errors in the input are now calculated more precisely.
59 LilyPond now uses Pango and FontConfig for selecting and rendering
60 UTF-8 input in non-@TeX{} backends. A font may be selected by using a
64 \override TextScript #'font-name = #"Serif"
69 or using the classic font selection mechanism
72 \override TextScript #'font-family = #'roman
73 \override TextScript #'font-series = #'bold
76 Any Type1 and TrueType font recognized by FontConfig is available in
80 Metrics of blocks of text can be retrieved from (La)@TeX{} directly,
81 using the @code{-f texstr} output backend. This provides exact metrics
82 for texts, including kerning and accents.
85 LilyPond now uses FreeType read the Feta font as an OpenType
86 font. This is cleaner design and more robust. A recent version of
87 FontForge (11122004 or newer) and Freetype is required.
89 As a result, the SVG backend is now a fully functional backend.
92 A new script, @code{\espressivo} has been added, for a combination of
93 crescendo and decrescendo on a single note.
96 In markups, expressions stacked with @code{\column},
97 @code{\center-align}, etc, are not grouped with @code{< ... >} anymore,
98 but with @code{@{ ... @}}, eg:
101 \line @{ first line @}
102 \line @{ second line @}
107 LilyPond will now avoid line breaks that cause long texts to stick
108 outside of the page staff.
111 Grace notes following a main note, used to be entered by letting the
112 grace notes follow a skip in a parallel expression, for example,
116 { s2 \grace { c16[ d] } } >>
121 This can now be shortened by doing
124 \afterGrace @{ d1 @} @{ c16[ d] @}
128 Pagebreaks can now be forced or forbidden after title blocks. This is
129 achieved by setting @code{breakbefore} in the @code{\header} block to
133 Shaped note heads. This feature has been sponsored by Jonathan Walther,
135 @lilypond[relative=1,fragment,verbatim,raggedright]
136 \set shapeNoteStyles = ##(do re mi fa #f la ti)
137 c d e f g a b c d e f g a b c
141 Layout for titles, page header and footer can now be entered as
142 @code{\markup} commands.
144 @item Positioning of slurs can now be adjusted manually
146 @item Grace notes are correctly quoted and formatted when using cue notes.
148 @item Cue notes can now be created with
151 \cueDuring #@var{voice-name} #@var{direction} @{ @var{music} @}
155 This will set stem directions and put the cue notes in the @code{cue}
159 @item Stemlets, short stems over beamed rests, have been added.
161 @lilypond[relative=1,verbatim,fragment,raggedright]
162 \override Stem #'stemlet-length = #0.75
169 For older news, go to
170 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.