1 \input texinfo @c -*-texinfo-*-
8 @chapter New features in 1.9 since 1.8
13 The @code{\newcontext} command will create a context with a unique
14 name automatically. Hence, for multi-staff scores, it is no longer
15 necessary to invent arbitrary context names. For example, a two-staff
16 score may be created by
20 \newcontext Staff @{ @var{notes for 1st staff} @}
21 \newcontext Staff @{ @var{notes for 2nd staff} @}
28 Octave checks make octave errors easier to correct.
35 This checks that @var{pitch} (without octave) yields @var{pitch} (with
36 octave) in \relative mode. If not, a warning is printed, and the
40 All articulations must now be entered postfix. For example,
47 is a pair of beamed slurred eighth notes.
50 The definition of @code{\relative} has been simplified. Octaves are
51 now always propagated in the order that music is entered. In the
56 \repeat "unfold" 3 BODY \alternative @{ ALT1 ALT2 ALT3 @}
61 the octave of BODY is based on PRE, the starting octave of ALT1 on
62 BODY, the starting octave of ALT2 on ALT1, etc.
65 The same mechanism is used for all other music expressions, except the
66 chord. Backwards compatibility is retained through a special program option,
70 #(ly:set-option 'old-relative)
78 @chapter New features in 1.8 since 1.6
83 The chord entry code has been completely rewritten. It is now
84 cleaner and more flexible.
87 A new syntax has been added for text entry. This syntax is more
88 friendly than the old mechanism, and it is implemented in a more
89 robust and modular way. For more information, refer to the section on
90 "Text markup" in the notation manual.
93 The integration of the input language and Scheme has been made deeper:
94 you can now use LilyPond identifiers in Scheme, and use Scheme
95 expressions instead of LilyPond identifiers.
98 The internal representation of music has been cleaned up completely
99 and converted to Scheme data structures. The representation may be
103 A new uniform postfix syntax for articulation has been introduced.
104 A beamed slurred pair of eighth notes can be entered as
110 In version 2.0, postfix syntax will be the only syntax
111 available, and the dashes will become optional.
113 This will simplify the language: all articulations can be entered as
114 postfix, in any order.
117 A new syntax has been added for chords:
124 It is not necessary to update files to this syntax, but it will be for
125 using LilyPond version 2.0. In version 2.0, this syntax will be
135 \simultaneous @{ .. @}
138 for simultaneous music.
140 To convert your files from <PITCHES> to <<PITCHES>>, use the script
141 included in buildscripts/convert-new-chords.py
143 This change was introduced for the following reasons
147 It solves the "start score with chord" problem, where you have to
148 state \context Voice explicitly when a chord was the start of a
151 With the new syntax, it is possible to distinguish between
152 articulations (or fingerings) which are for a single chord note,
153 and which are for the entire chord. This allows for per-note
154 fingerings, and is more logical on the whole.
158 User code may now be executed during interpreting. The syntax for
162 \applycontext #SCHEME-FUNCTION
166 User code may now be executed on arbitrary grobs during interpreting.
167 The syntax for this feature is
170 \applyoutput #SCHEME-FUNCTION
174 SCHEME-FUNCTION takes a single argument, and is called for every grob
175 that is created in the current context.
178 New algorithms for chord-name formatting have been installed. They
179 can be tuned and have ergonomic syntax for entering exceptions.
182 Texts may now be put on multimeasure rests, e.g.
185 R1*20^\markup @{ "GP" @}
189 Ancient notation now prints ligatures in Gregorian square neumes
190 notation, roughly following the typographical style of the Liber
191 hymnarius of Solesmes, published in 1983. Ligatures are still printed
192 without the proper line breaking and horizontal spacing.
195 Glissandi can now be printed using the zigzag style.
198 LilyPond can now print clusters. The syntax is
201 \apply #notes-to-clusters @{ NOTE NOTE .. @}
205 For irregular meters, beat grouping marks can be printed. The
209 #(set-time-signature 7 8 '(3 2 2))
214 Nested horizontal brackets for music analysis can now be printed:
223 @item Ottava brackets are now fully supported as a feature. The syntax
231 @item Metronome markings are printed when a \tempo command is processed.
235 @item Fingerings can be put on chords horizontally.
239 @item The appearance of various glyphs has been fine-tuned.
243 @item Different types of percent style repeats may now be nested.
247 @item The emacs support has been extended.
251 The manual has been completely revised and extended.
255 @chapter New features in 1.6 since 1.4
261 Support for figured bass and tablature.
264 Completely rewritten beam formatting: provides much better output
269 Completely revised and improved music font.
273 Completely rewritten MIDI import support.
276 Completely rewritten grace note support. Practically speaking this
277 means that grace notes can be slurred to normal normal notes.
281 Improved accidental handling and formatting: styles for producing
282 cautionaries may vary, and complex collisions between accidentals of a
283 chord are handled much better.
286 Better spacing: both globally and locally. This includes subtle
287 details like optical stem spacing.
290 More support for ancient notation: mensural ligatures, ambitus
291 (pitch range) of voices, more shapes, etc.
294 More support for piano notation: bracket pedals, directed arpeggios,
298 Easier music polyphonic music entry.
301 More extensibility, many speedups and bugfixes
304 The manual has been thoroughly revised.
307 Development is now hosted at http://savannah.gnu.org, and sources
308 can be downloaded through anonymous CVS.
311 Support for windows: LilyPond is part of the cygwin distribution,
312 which comes with a user-friendly installer.