1 \input texinfo @c -*-texinfo-*-
7 @unnumbered New features in 2.5 since 2.4
12 With the new @code{tieWaitForNote} property, arpeggios may be written
13 out using ties, for example,
15 @lilypond[fragment,verbatim,relative=1,raggedright]
16 \set tieWaitForNote = ##t
17 \grace { c16[~ e~ g]~ } <c, e g>4
20 Thanks to Steve Doonan for funding development of this feature.
23 Individual objects may be assigned colors, for example,
25 @lilypond[fragment,relative=1,verbatim,raggedright]
26 \override Beam #'color = #cyan
27 \override NoteHead #'color = #darkyellow
32 The PostScript backend is now used by default. This backend requires
33 less machinery to run, and gives more consistent results.
35 Due bugs in GhostScript's PDF handling, it is recommended to upgrade
39 Separator slashes may be inserted between systems in a score. For an
41 @file{input/regression/system-separator.ly}:
43 @lilypondfile{system-separator.ly}
46 Locations of errors in the input are now calculated more precisely.
49 LilyPond now uses Pango and FontConfig for selecting and rendering
50 internationalized text in non-@TeX{} backends. A font may be selected
51 by using a FontConfig name,
54 \override TextScript #'font-name = #"Serif"
59 or using the classic font selection mechanism
62 \override TextScript #'font-family = #'roman
63 \override TextScript #'font-series = #'bold
66 Any Type1 and TrueType font recognized by FontConfig is available in
70 Input strings encoded in UTF-8 are then rendered through Pango.
73 Metrics of blocks of text can be retrieved from (La)@TeX{} directly,
74 using the @code{-f texstr} output backend. This provides exact metrics
75 for texts, including kerning and accents.
78 LilyPond now uses FreeType read the Feta font as an OpenType
79 font. This is cleaner design and more robust. A recent version of
80 FontForge (11122004 or newer) and Freetype is required.
82 As a result, the SVG backend is now a fully functional backend.
85 A new script, @code{\espressivo} has been added, for a combination of
86 crescendo and decrescendo on a single note.
89 In markups, expressions stacked with @code{\column},
90 @code{\center-align}, etc, are not grouped with @code{< ... >} anymore,
91 but with @code{@{ ... @}}, eg:
94 \line @{ first line @}
95 \line @{ second line @}
100 LilyPond will now avoid line breaks that cause long texts to stick
101 outside of the page staff.
104 Grace notes following a main note, used to be entered by letting the
105 grace notes follow a skip in a parallel expression, for example,
109 { s2 \grace { c16[ d] } } >>
114 This can now be shortened by doing
117 \afterGrace @{ d1 @} @{ c16[ d] @}
121 Pagebreaks can now be forced or forbidden after title blocks. This is
122 achieved by setting @code{breakbefore} in the @code{\header} block to
126 Shaped note heads. This feature has been sponsored by Jonathan Walther.
129 Layout for titles, page header and footer can now be entered as
130 @code{\markup} commands.
132 @item Positioning of slurs can now be adjusted manually
134 @item Grace notes are correctly quoted and formatted when using cue notes.
136 @item Cue notes can now be created with
139 \cueDuring #@var{voice-name} #@var{direction} @{ @var{music} @}
143 This will set stem directions and put the cue notes in the @code{cue}
146 @item Stemlets, short stems over beamed rests, have been added.
151 For older news, go to
152 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.