@setfilename NEWS.info
@settitle NEWS
-
-
-@node Top, , ,
-@top
-@unnumbered New features in 2.5 since 2.4
-
@ifhtml
@macro inputfileref{DIR,NAME}
@uref{../../../\DIR\/out-www/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
@end macro
+@macro usermanref{NAME}
+@inforef{\NAME\,,../../user/out-www/lilypond/lilypond}@c
+@end macro
@end ifhtml
@ifnothtml
@macro inputfileref{DIR,NAME}
@file{\DIR\/\NAME\}@c
@end macro
+@macro usermanref{NAME}
+See user manual, \NAME\
+@end macro
@end ifnothtml
+
+
+@node Top, , ,
+@top
+@unnumbered New features in 2.5 since 2.4
+
+
@itemize @bullet
+@item
+String numbers are now printed on chords as well,
+
+@lilypond[relative,relative=1,raggedright]
+<c\1 e\2 g\3>
+@end lilypond
+
+See also @inputfileref{input/regression,string-number.ly}.
+
+@item
+Notes with ledger lines will be kept at a distance, so they never
+disappear.
+
+@item
+Clefs that are below notes of other staves are now spaced according to
+engraving conventions.
+
+@item
+Markup texts can be appended to a @code{\score} block or toplevel
+music expression, for example,
+
+@example
+\relative @{ c' d e @}
+\markup @{ first text @}
+\markup @{ second text @}
+@end example
+@c FIXME, cannot use toplevel music examples in lilypond-book,
+@c but it works at toplevel too, as shown.
+@lilypond[quote,raggedright]
+\paper {
+ vsize = 60\mm
+ hsize = 60\mm
+ %% FIXME?
+ printpagenumber = ##f
+}
+\header {
+ tagline = ""
+}
+\book {
+ \score {
+ \relative { c' d e }
+ }
+ \markup { first text }
+ \markup { second text }
+}
+@end lilypond
+
+
+See @inputfileref{input/regression,score-text.ly}.
+
+
+@item
+@TeX{}'s @code{kpathsea} library is loaded dynamically, so installing
+LilyPond does not require installing @TeX{} anymore.
+
+@item
+Point and click editing is now supported in the PS/PDF backend as
+well.
+See
+@ifhtml
+@uref{../../user/out-www/lilypond/Point-and-click.html,Point and click}
+@end ifhtml
+@ifnothtml
+the section Point and click in he user manual.
+@end ifnothtml
+
+@item
+White mensural ligatures now conform more closely to Renaissance
+usage.
+
@item
With the new @code{tieWaitForNote} property, arpeggios may be written
@end lilypond
@item
-The PostScript backend is now used by default. This backend requires
+The PostScript backend is now used by default. This backend requires
less machinery to run, and gives more consistent results.
-Due bugs in GhostScript's PDF handling, it is recommended to upgrade
-to GhostScript 8.x.
+
+GhostScript 8.x is required for PDF output. Earlier versions may hang
+while converting PostScript to PDF.
@item
Separator slashes may be inserted between systems in a score. For an