1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 1.9 since 1.8
13 Two new commands for grace notes have been added, @code{\accacciatura}
14 and @code{\appoggiatura},
21 Both reflect the traditional meanings of accacciatura and appogiatura,
22 and both insert insert a slur from the first grace note to the main
26 Layout options for grace notes are now stored in a context property,
27 and may now be set separately from musical content.
30 The @code{\new} command will create a context with a unique
31 name automatically. Hence, for multi-staff scores, it is no longer
32 necessary to invent arbitrary context names. For example, a two-staff
33 score may be created by
37 \new Staff @{ @var{notes for 1st staff} @}
38 \new Staff @{ @var{notes for 2nd staff} @}
45 Octave checks make octave errors easier to correct.
52 This checks that @var{pitch} (without octave) yields @var{pitch} (with
53 octave) in \relative mode. If not, a warning is printed, and the
57 All articulations must now be entered postfix. For example,
64 is a pair of beamed slurred eighth notes.
67 The definition of @code{\relative} has been simplified. Octaves are
68 now always propagated in the order that music is entered. In the
73 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
78 the octave of BODY is based on PRE, the starting octave of ALT1 on
79 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
82 The same mechanism is used for all other music expressions, except the
83 chord. Backwards compatibility is retained through a special program option,
87 #(ly:set-option 'old-relative)
95 @chapter New features in 1.8 since 1.6
100 The chord entry code has been completely rewritten. It is now
101 cleaner and more flexible.
104 A new syntax has been added for text entry. This syntax is more
105 friendly than the old mechanism, and it is implemented in a more
106 robust and modular way. For more information, refer to the section on
107 "Text markup" in the notation manual.
110 The integration of the input language and Scheme has been made deeper:
111 you can now use LilyPond identifiers in Scheme, and use Scheme
112 expressions instead of LilyPond identifiers.
115 The internal representation of music has been cleaned up completely
116 and converted to Scheme data structures. The representation may be
120 A new uniform postfix syntax for articulation has been introduced.
121 A beamed slurred pair of eighth notes can be entered as
127 In version 2.0, postfix syntax will be the only syntax
128 available, and the dashes will become optional.
130 This will simplify the language: all articulations can be entered as
131 postfix, in any order.
134 A new syntax has been added for chords:
141 It is not necessary to update files to this syntax, but it will be for
142 using LilyPond version 2.0. In version 2.0, this syntax will be
152 \simultaneous @{ .. @}
155 for simultaneous music.
157 To convert your files from <PITCHES> to <<PITCHES>>, use the script
158 included in buildscripts/convert-new-chords.py
160 This change was introduced for the following reasons
164 It solves the "start score with chord" problem, where you have to
165 state \context Voice explicitly when a chord was the start of a
168 With the new syntax, it is possible to distinguish between
169 articulations (or fingerings) which are for a single chord note,
170 and which are for the entire chord. This allows for per-note
171 fingerings, and is more logical on the whole.
175 User code may now be executed during interpreting. The syntax for
179 \applycontext #SCHEME-FUNCTION
183 User code may now be executed on arbitrary grobs during interpreting.
184 The syntax for this feature is
187 \applyoutput #SCHEME-FUNCTION
191 SCHEME-FUNCTION takes a single argument, and is called for every grob
192 that is created in the current context.
195 New algorithms for chord-name formatting have been installed. They
196 can be tuned and have ergonomic syntax for entering exceptions.
199 Texts may now be put on multimeasure rests, e.g.
202 R1*20^\markup @{ "GP" @}
206 Ancient notation now prints ligatures in Gregorian square neumes
207 notation, roughly following the typographical style of the Liber
208 hymnarius of Solesmes, published in 1983. Ligatures are still printed
209 without the proper line breaking and horizontal spacing.
212 Glissandi can now be printed using the zigzag style.
215 LilyPond can now print clusters. The syntax is
218 \apply #notes-to-clusters @{ NOTE NOTE .. @}
222 For irregular meters, beat grouping marks can be printed. The
226 #(set-time-signature 7 8 '(3 2 2))
231 Nested horizontal brackets for music analysis can now be printed:
240 @item Ottava brackets are now fully supported as a feature. The syntax
248 @item Metronome markings are printed when a \tempo command is processed.
252 @item Fingerings can be put on chords horizontally.
256 @item The appearance of various glyphs has been fine-tuned.
260 @item Different types of percent style repeats may now be nested.
264 @item The emacs support has been extended.
268 The manual has been completely revised and extended.
272 @chapter New features in 1.6 since 1.4
278 Support for figured bass and tablature.
281 Completely rewritten beam formatting: provides much better output
286 Completely revised and improved music font.
290 Completely rewritten MIDI import support.
293 Completely rewritten grace note support. Practically speaking this
294 means that grace notes can be slurred to normal normal notes.
298 Improved accidental handling and formatting: styles for producing
299 cautionaries may vary, and complex collisions between accidentals of a
300 chord are handled much better.
303 Better spacing: both globally and locally. This includes subtle
304 details like optical stem spacing.
307 More support for ancient notation: mensural ligatures, ambitus
308 (pitch range) of voices, more shapes, etc.
311 More support for piano notation: bracket pedals, directed arpeggios,
315 Easier music polyphonic music entry.
318 More extensibility, many speedups and bugfixes
321 The manual has been thoroughly revised.
324 Development is now hosted at http://savannah.gnu.org, and sources
325 can be downloaded through anonymous CVS.
328 Support for windows: LilyPond is part of the cygwin distribution,
329 which comes with a user-friendly installer.