1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
6 @macro inputfileref{DIR,NAME}
7 @uref{../../\DIR\/collated-files.html#\NAME\,@file{\DIR\/\NAME\}}@c
9 @macro usermanref{NAME}
10 @inforef{\NAME\,,../user/lilypond/lilypond}@c
15 @macro inputfileref{DIR,NAME}
18 @macro usermanref{NAME}
19 See user manual, \NAME\
23 @macro textanchor{NAME}
30 @documentencoding utf-8
39 @unnumbered New features in 2.11 since 2.10
42 This document is also available in @uref{NEWS.pdf,PDF}. It's part of
43 the @uref{../,LilyPond Documentation}
55 * only show verbatim input for syntax/input changes
57 * try to be as brief possible in those cases
59 * don't try to provide real-world examples, they often get too big,
60 which scares away people.
62 * Write complete sentences.
64 * only show user-visible changes.
69 It is now possible to specify, using the @code{page-count} variable in
70 the paper block, the number of pages that will be used.
73 A new page breaking function, @code{ly:minimal-breaking}, is dedicated
74 to books with many pages or a lot of texts.
77 A table of contents is included using @code{\markuplines \table-of-contents}.
78 Elements are added to it using the @code{\tocItem} command.
81 Text spreading over several pages is entered using the
82 @code{\markuplines} keyword. Builtin markup list commands, such as
83 @code{\justified-lines} or @code{\wordwrap-lines} may be used, and new
84 ones created using the @code{define-markup-list-command} Scheme macro.
87 Particular points of a book may be marked with the @code{\label}
88 command. Then, the page where these points are placed can be refered to
89 using the @code{\page-ref} markup command.
92 Page breaking and page turning commands (@code{\pageBreak},
93 @code{\noPageBreak}, etc) can be used at top-level, between scores and
97 The following options are now changed as a @code{-d} sub-option:
98 @code{--backend}, @code{--safe}, @code{--preview} and
99 @code{--no-pages} (which became @code{-dno-print-pages}). The @code{-b}
100 option does not exist any more.
103 Improved testing procedure now catch changes in CPU and memory
104 performance, page layout, MIDI results and warnings. This helps to
105 reduce the number of regression errors during development, resulting
106 in more stable releases.
108 See @uref{INSTALL.html#testing} for more information.
110 Nested properties, such as @code{details} in @code{Slur}, can be
111 reverted as well. The syntax for this is
114 \revert Slur #'(details closeness-factor)
118 All line spanners are more flexible now in the configuration of
119 their end points. This includes glissando, voice followers, text
120 crescendos and other text spanners. The old syntax for setting
121 text on line spanners is no longer valid.
123 @c with ragged-right we can't see the gliss.
126 \override Glissando #'bound-details #'right #'text = \markup { \hcenter \bold down }
127 \override Glissando #'bound-details #'right #'Y = #-4
128 \override Glissando #'bound-details #'right #'padding = #0.0
129 \override Glissando #'bound-details #'left #'arrow = ##t
130 \override Glissando #'bound-details #'left #'padding = #3.0
131 \override Glissando #'style = #'trill
137 This feature was sponsored by Trevor Bača.
141 The environment variable LILYPONDPREFIX has been renamed to
145 Notes or rests, such as a typical end note, that fill an entire
146 measure are preceded by some more space.
148 @lilypond[ragged-right]
158 @item All @code{\score}s in a lilypond-book fragment are now inserted
159 into the document. Also, toplevel markups don't result in an entire
162 @item Alterations (such as a sharp and flat) may now be arbitrary
163 fractions. This allows some forms of microtonal music. For example,
164 Turkish makam music uses 1/9th tone alterations.
166 @lilypondfile{makam.ly}
170 @item Tie directions may be set with @code{^~} and @code{_~}
172 @item Tablature now supports harmonics and slides,
174 @lilypond[fragment,ragged-right,relative=1]
177 <c g'\harmonic> d\2\glissando e\2
181 This feature was sponsored by Mike Amundsen
183 @item Horizontal spacing now follows object outlines more
184 accurately. This allows tighter horizontal spacing.
186 @lilypond[fragment,ragged-right]
194 @item Objects that belong outside of the staff are
195 now positioned automatically to avoid collisions.
197 @lilypond[fragment,ragged-right,relative=1]
199 \once \override TextScript #'self-alignment-X = #CENTER
200 a,^"this doesn't collide with the c"
201 b^"this goes above the previous markup"
202 a8_"this goes below the dynamic"
206 @item Staves are spaced vertically using a skyline algorithm. This helps to avoid
207 uneven vertical spacing.
209 @lilypond[ragged-right]
211 %% todo: fix 'landscape PDF.
212 #(set-default-paper-size "a6" )
220 a,,1 | a'4 b' c'' d'' \break
221 \repeat unfold 2 {a' b' c'' d''} | b''''1
232 For older news, go to
233 @uref{http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html},
234 or @uref{../,go back} to the Documentation index.