1 \input texinfo @c -*-texinfo-*-
4 @macro inputfileref{DIR,NAME}
5 @uref{../../../../\DIR\/out-www/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
10 @macro inputfileref{DIR,NAME}
15 @setfilename NEWS.info
20 @unnumbered New features in 2.5 since 2.4
25 With the new @code{tieWaitForNote} property, arpeggios may be written
26 out using ties, for example,
28 @lilypond[fragment,verbatim,relative=1,raggedright]
29 \set tieWaitForNote = ##t
30 \grace { c16[~ e~ g]~ } <c, e g>4
33 Thanks to Steve Doonan for funding development of this feature.
36 Individual objects may be assigned colors, for example,
38 @lilypond[fragment,relative=1,verbatim,raggedright]
39 \override NoteHead #'color = #red
44 The PostScript backend is now used by default. This backend requires
45 less machinery to run, and gives more consistent results.
47 Due bugs in GhostScript's PDF handling, it is recommended to upgrade
51 Separator slashes may be inserted between systems in a score. For an
52 example, see @inputfileref{input/regression/system-separator.ly}:
55 Locations of errors in the input are now calculated more precisely.
58 LilyPond now uses Pango and FontConfig for selecting and rendering
59 UTF-8 input in non-@TeX{} backends. A font may be selected by using a
63 \override TextScript #'font-name = #"Serif"
68 or using the classic font selection mechanism
71 \override TextScript #'font-family = #'roman
72 \override TextScript #'font-series = #'bold
75 Any Type1 and TrueType font recognized by FontConfig is available in
79 Metrics of blocks of text can be retrieved from (La)@TeX{} directly,
80 using the @code{-f texstr} output backend. This provides exact metrics
81 for texts, including kerning and accents.
84 LilyPond now uses FreeType read the Feta font as an OpenType
85 font. This is cleaner design and more robust. A recent version of
86 FontForge (11122004 or newer) and Freetype is required.
88 As a result, the SVG backend is now a fully functional backend.
91 A new script, @code{\espressivo} has been added, for a combination of
92 crescendo and decrescendo on a single note.
95 In markups, expressions stacked with @code{\column},
96 @code{\center-align}, etc, are not grouped with @code{< ... >} anymore,
97 but with @code{@{ ... @}}, eg:
100 \line @{ first line @}
101 \line @{ second line @}
106 LilyPond will now avoid line breaks that cause long texts to stick
107 outside of the page staff.
110 Grace notes following a main note, used to be entered by letting the
111 grace notes follow a skip in a parallel expression, for example,
115 { s2 \grace { c16[ d] } } >>
120 This can now be shortened by doing
123 \afterGrace @{ d1 @} @{ c16[ d] @}
127 Pagebreaks can now be forced or forbidden after title blocks. This is
128 achieved by setting @code{breakbefore} in the @code{\header} block to
132 Shaped note heads. This feature has been sponsored by Jonathan Walther.
135 Layout for titles, page header and footer can now be entered as
136 @code{\markup} commands.
138 @item Positioning of slurs can now be adjusted manually
140 @item Grace notes are correctly quoted and formatted when using cue notes.
142 @item Cue notes can now be created with
145 \cueDuring #@var{voice-name} #@var{direction} @{ @var{music} @}
149 This will set stem directions and put the cue notes in the @code{cue}
152 @item Stemlets, short stems over beamed rests, have been added.
157 For older news, go to
158 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.