@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 ifnothtml
+@documentencoding utf-8
+@documentlanguage en
+
+@ifnottex
+@node Top
+@top
+@end ifnottex
+@unnumbered New features in 2.5 since 2.4
+
@itemize @bullet
+@item
+Staves may be stopped and started halfway a line, e.g.
+
+@lilypond[relative=2,fragment,verbatim]
+b4 b \stopStaff b \startStaff b
+@end lilypond
+
+@noindent
+This feature has been sponsored by Hans Forbrich.
+
+@item
+Grid lines, vertical lines synchronized with notes, can be drawn across
+staves, by adding suitable engravers.
+An example is in @inputfileref{input/regression,grid-lines.ly},
+
+@lilypondfile[]{grid-lines.ly}
+
+@item
+Lines, such as glissandi or Text-spanner lines, can have arrows at the
+end, e.g.
+
+@lilypond[verbatim,fragment]
+\override Glissando #'arrow = ##t
+b''2 \glissando b'
+@end lilypond
+
+@item
+Chord names may now be rendered in Italian and French.
+
+@item
+@file{lilypond-book} now makes @file{lilypond} print line numbers
+relative to the input file for every error message.
+
+@item
+The command @code{\epsfile} allows inclusion of EPS graphics into
+markup texts.
+
+@item
+There is a music function @code{\musicDisplay}, which will display a
+music expression as indented Scheme code.
+
+@item
+Automatic beaming is now specified explicitly for each moment
+throughout a measure, which enables automatic beaming in compound
+measures, as demonstrated in the following item.
+
+@item
+A plus sign was added to the number font. This enables printing of
+compound time signatures
+
+@lilypondfile[]{compound-time.ly}
+
+@item
+A new @code{\circle} markup command allows for all kinds of circled
+texts
+
+@lilypondfile[]{circle.ly}
+
+@item
+String numbers are now printed on chords as well
+
+@lilypond[relative,relative=1,raggedright,fragment,verbatim]
+<c\1 e\2 g\3>
+@end lilypond
+
+See also @inputfileref{input/regression,string-number.ly}.
+
+This feature was sponsored by Gunther Strube.
+
+@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}
+@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 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 to 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
for texts, including kerning and accents.
@item
-LilyPond now uses FreeType read the Feta font as an OpenType
-font. This is cleaner design and more robust. A recent version of
-FontForge (11122004 or newer) and Freetype is required.
+LilyPond now uses FreeType read the Feta font as an OpenType font. This
+is a cleaner design and more robust. Recent versions of FontForge (2004
+1211 or newer) and Freetype are required. As a result,
-As a result, the SVG backend is now a fully functional backend.
+@item
+the SVG backend is now a fully functional backend.
@item
A new script, @code{\espressivo} has been added, for a combination of
@noindent
This will set stem directions and put the cue notes in the @code{cue}
-@code{Voice}
-
+@code{Voice}.
@item Stemlets, short stems over beamed rests, have been added.
@end itemize
-
+@ifhtml
For older news, go to
@uref{http://lilypond.org/doc/v2.4/Documentation/topdocs/out-www/NEWS.html}.
+@end ifhtml
+@bye
projects / lilypond.git / blobdiff