1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 1.9 since 1.8
12 Markup text (ie. general text formatting) may now be used for lyrics too.
15 Two new commands for grace notes have been added, @code{\accacciatura}
16 and @code{\appoggiatura},
23 Both reflect the traditional meanings of acciaccatura and appogiatura,
24 and both insert insert a slur from the first grace note to the main
28 Layout options for grace notes are now stored in a context property,
29 and may now be set separately from musical content.
32 The @code{\new} command will create a context with a unique
33 name automatically. Hence, for multi-staff scores, it is no longer
34 necessary to invent arbitrary context names. For example, a two-staff
35 score may be created by
39 \new Staff @{ @var{notes for 1st staff} @}
40 \new Staff @{ @var{notes for 2nd staff} @}
47 Octave checks make octave errors easier to correct.
54 This checks that @var{pitch} (without octave) yields @var{pitch} (with
55 octave) in \relative mode. If not, a warning is printed, and the
59 All articulations must now be entered postfix. For example,
66 is a pair of beamed slurred eighth notes.
69 The definition of @code{\relative} has been simplified. Octaves are
70 now always propagated in the order that music is entered. In the
75 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 @}
80 the octave of BODY is based on PRE, the starting octave of ALT1 on
81 BODY, the starting octave of ALT2 on ALT1, and the starting octave of
84 The same mechanism is used for all other music expressions, except the
85 chord. Backwards compatibility is retained through a special program option,
89 #(ly:set-option 'old-relative)
97 @chapter New features in 1.8 since 1.6
102 The chord entry code has been completely rewritten. It is now
103 cleaner and more flexible.
106 A new syntax has been added for text entry. This syntax is more
107 friendly than the old mechanism, and it is implemented in a more
108 robust and modular way. For more information, refer to the section on
109 "Text markup" in the notation manual.
112 The integration of the input language and Scheme has been made deeper:
113 you can now use LilyPond identifiers in Scheme, and use Scheme
114 expressions instead of LilyPond identifiers.
117 The internal representation of music has been cleaned up completely
118 and converted to Scheme data structures. The representation may be
122 A new uniform postfix syntax for articulation has been introduced.
123 A beamed slurred pair of eighth notes can be entered as
129 In version 2.0, postfix syntax will be the only syntax
130 available, and the dashes will become optional.
132 This will simplify the language: all articulations can be entered as
133 postfix, in any order.
136 A new syntax has been added for chords:
143 It is not necessary to update files to this syntax, but it will be for
144 using LilyPond version 2.0. In version 2.0, this syntax will be
154 \simultaneous @{ .. @}
157 for simultaneous music.
159 To convert your files from <PITCHES> to <<PITCHES>>, use the script
160 included in buildscripts/convert-new-chords.py
162 This change was introduced for the following reasons
166 It solves the "start score with chord" problem, where you have to
167 state \context Voice explicitly when a chord was the start of a
170 With the new syntax, it is possible to distinguish between
171 articulations (or fingerings) which are for a single chord note,
172 and which are for the entire chord. This allows for per-note
173 fingerings, and is more logical on the whole.
177 User code may now be executed during interpreting. The syntax for
181 \applycontext #SCHEME-FUNCTION
185 User code may now be executed on arbitrary grobs during interpreting.
186 The syntax for this feature is
189 \applyoutput #SCHEME-FUNCTION
193 SCHEME-FUNCTION takes a single argument, and is called for every grob
194 that is created in the current context.
197 New algorithms for chord-name formatting have been installed. They
198 can be tuned and have ergonomic syntax for entering exceptions.
201 Texts may now be put on multimeasure rests, e.g.
204 R1*20^\markup @{ "GP" @}
208 Ancient notation now prints ligatures in Gregorian square neumes
209 notation, roughly following the typographical style of the Liber
210 hymnarius of Solesmes, published in 1983. Ligatures are still printed
211 without the proper line breaking and horizontal spacing.
214 Glissandi can now be printed using the zigzag style.
217 LilyPond can now print clusters. The syntax is
220 \apply #notes-to-clusters @{ NOTE NOTE .. @}
224 For irregular meters, beat grouping marks can be printed. The
228 #(set-time-signature 7 8 '(3 2 2))
233 Nested horizontal brackets for music analysis can now be printed:
242 @item Ottava brackets are now fully supported as a feature. The syntax
250 @item Metronome markings are printed when a \tempo command is processed.
254 @item Fingerings can be put on chords horizontally.
258 @item The appearance of various glyphs has been fine-tuned.
262 @item Different types of percent style repeats may now be nested.
266 @item The emacs support has been extended.
270 The manual has been completely revised and extended.
274 @chapter New features in 1.6 since 1.4
280 Support for figured bass and tablature.
283 Completely rewritten beam formatting: provides much better output
288 Completely revised and improved music font.
292 Completely rewritten MIDI import support.
295 Completely rewritten grace note support. Practically speaking this
296 means that grace notes can be slurred to normal normal notes.
300 Improved accidental handling and formatting: styles for producing
301 cautionaries may vary, and complex collisions between accidentals of a
302 chord are handled much better.
305 Better spacing: both globally and locally. This includes subtle
306 details like optical stem spacing.
309 More support for ancient notation: mensural ligatures, ambitus
310 (pitch range) of voices, more shapes, etc.
313 More support for piano notation: bracket pedals, directed arpeggios,
317 Easier music polyphonic music entry.
320 More extensibility, many speedups and bugfixes
323 The manual has been thoroughly revised.
326 Development is now hosted at http://savannah.gnu.org, and sources
327 can be downloaded through anonymous CVS.
330 Support for windows: LilyPond is part of the cygwin distribution,
331 which comes with a user-friendly installer.