1 \input texinfo @c -*-texinfo-*-
6 @macro inputfileref{DIR,NAME}
7 @uref{../../../\DIR\/out-www/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
9 @macro usermanref{NAME}
10 @inforef{\NAME\,,../../user/out-www/lilypond/lilypond}@c
15 @macro inputfileref{DIR,NAME}
18 @macro usermanref{NAME}
19 See user manual, \NAME\
24 @documentencoding utf-8
31 @unnumbered New features in 2.5 since 2.4
37 Grid lines, vertical lines synchronized with notes, can be drawn across
38 staves, by adding suitable engravers.
39 An example is in @inputfileref{input/regression,grid-lines.ly},
41 @lilypondfile[]{grid-lines.ly}
44 Lines, such as glissandi or Text-spanner lines, can have arrows at the
47 @lilypond[verbatim,fragment]
48 \override Glissando #'arrow = ##t
53 Chord names may now be rendered in Italian and French.
56 @file{lilypond-book} now makes @file{lilypond} print line numbers
57 relative to the input file for every error message.
60 The command @code{\epsfile} allows inclusion of EPS graphics into
64 There is a music function @code{\musicDisplay}, which will display a
65 music expression as indented Scheme code.
68 Automatic beaming is now specified explicitly for each moment
69 throughout a measure, which enables automatic beaming in compound
70 measures, as demonstrated in the following item.
73 A plus sign was added to the number font. This enables printing of
74 compound time signatures
76 @lilypondfile[]{compound-time.ly}
79 A new @code{\circle} markup command allows for all kinds of circled
82 @lilypondfile[]{circle.ly}
85 String numbers are now printed on chords as well
87 @lilypond[relative,relative=1,raggedright,fragment,verbatim]
91 See also @inputfileref{input/regression,string-number.ly}.
93 This feature was sponsored by Gunther Strube.
96 Notes with ledger lines will be kept at a distance, so they never
100 Clefs that are below notes of other staves are now spaced according to
101 engraving conventions.
104 Markup texts can be appended to a @code{\score} block or toplevel
105 music expression, for example,
108 \relative @{ c' d e @}
109 \markup @{ first text @}
110 \markup @{ second text @}
112 @c FIXME, cannot use toplevel music examples in lilypond-book,
113 @c but it works at toplevel too, as shown.
114 @lilypond[quote,raggedright]
119 printpagenumber = ##f
128 \markup { first text }
129 \markup { second text }
134 See @inputfileref{input/regression,score-text.ly}.
138 @TeX{}'s @code{kpathsea} library is loaded dynamically, so installing
139 LilyPond does not require installing @TeX{} anymore.
142 Point and click editing is now supported in the PS/PDF backend as
146 @uref{../../user/out-www/lilypond/Point-and-click.html,Point and click}.
149 the section Point and click in he user manual.
153 White mensural ligatures now conform more closely to Renaissance
158 With the new @code{tieWaitForNote} property, arpeggios may be written
159 out using ties, for example,
161 @lilypond[fragment,verbatim,relative=1,raggedright]
162 \set tieWaitForNote = ##t
163 \grace { c16[~ e~ g]~ } <c, e g>4
166 Thanks to Steve Doonan for funding development of this feature.
169 Individual objects may be assigned colors, for example,
171 @lilypond[fragment,relative=1,verbatim,raggedright]
172 \override NoteHead #'color = #red
177 The PostScript backend is now used by default. This backend requires
178 less machinery to run, and gives more consistent results.
181 GhostScript 8.x is required for PDF output. Earlier versions may hang
182 while converting PostScript to PDF.
185 Separator slashes may be inserted between systems in a score. For an
186 example, see @inputfileref{input/regression,system-separator.ly}:
189 Locations of errors in the input are now calculated more precisely.
192 LilyPond now uses Pango and FontConfig for selecting and rendering
193 UTF-8 input in non-@TeX{} backends. A font may be selected by using a
197 \override TextScript #'font-name = #"Serif"
202 or using the classic font selection mechanism
205 \override TextScript #'font-family = #'roman
206 \override TextScript #'font-series = #'bold
209 Any Type1 and TrueType font recognized by FontConfig is available in
213 Metrics of blocks of text can be retrieved from (La)@TeX{} directly,
214 using the @code{-f texstr} output backend. This provides exact metrics
215 for texts, including kerning and accents.
218 LilyPond now uses FreeType read the Feta font as an OpenType font. This
219 is a cleaner design and more robust. Recent versions of FontForge (2004
220 1211 or newer) and Freetype are required. As a result,
223 the SVG backend is now a fully functional backend.
226 A new script, @code{\espressivo} has been added, for a combination of
227 crescendo and decrescendo on a single note.
230 In markups, expressions stacked with @code{\column},
231 @code{\center-align}, etc, are not grouped with @code{< ... >} anymore,
232 but with @code{@{ ... @}}, eg:
235 \line @{ first line @}
236 \line @{ second line @}
241 LilyPond will now avoid line breaks that cause long texts to stick
242 outside of the page staff.
245 Grace notes following a main note, used to be entered by letting the
246 grace notes follow a skip in a parallel expression, for example,
250 { s2 \grace { c16[ d] } } >>
255 This can now be shortened by doing
258 \afterGrace @{ d1 @} @{ c16[ d] @}
262 Pagebreaks can now be forced or forbidden after title blocks. This is
263 achieved by setting @code{breakbefore} in the @code{\header} block to
267 Shaped note heads. This feature has been sponsored by Jonathan Walther,
269 @lilypond[relative=1,fragment,verbatim,raggedright]
270 \set shapeNoteStyles = ##(do re mi fa #f la ti)
271 c d e f g a b c d e f g a b c
275 Layout for titles, page header and footer can now be entered as
276 @code{\markup} commands.
278 @item Positioning of slurs can now be adjusted manually
280 @item Grace notes are correctly quoted and formatted when using cue notes.
282 @item Cue notes can now be created with
285 \cueDuring #@var{voice-name} #@var{direction} @{ @var{music} @}
289 This will set stem directions and put the cue notes in the @code{cue}
292 @item Stemlets, short stems over beamed rests, have been added.
294 @lilypond[relative=1,verbatim,fragment,raggedright]
295 \override Stem #'stemlet-length = #0.75
302 For older news, go to
303 @uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.