-New features in 1.7 since 1.6
+New features in 1.8 since 1.6
+=============================
-* Deeper integration of the input language and Scheme. You can now use
+** The chord entry code has been completely rewritten. It is now
+cleaner and more flexible.
+
+** A new syntax has been added for text entry. This syntax is more
+friendly than the old mechanism, and it is implemented in a more
+robust and modular way. For more information, refer to the section on
+"Text markup" in the notation manual.
+
+** Deeper integration of the input language and Scheme. You can now use
LilyPond identifiers in Scheme, and use Scheme expressions instead of
LilyPond identifiers.
-* Music types cleaned up and Schemified.
+** The internal representation of music has been cleaned up completely
+and converted to Scheme data structures. The representation may be
+exported as XML.
-* New syntax for chords:
+** A new syntax has been added for chords:
<< PITCHES >>
-This is in addition to the < MUSICS > syntax for simultaneous music. Combined with this: uniform postfix syntax for articulations:
+It is not necessary to update files to this syntax, but it will be for
+using LilyPond version 2.0. In version 2.0, this syntax will be
+changed to
+
+ < PITCHES > for chords
+
+and
+
+ \simultaneous { .. } for simultaneous music.
+
+To convert your files from <PITCHES> to <<PITCHES>>, use the script
+included in buildscripts/convert-new-chords.py
+
+** A new uniform postfix syntax for articulation has been introduced.
+A beamed slurred pair of eighth notes can be entered as
c8-[-( d8-]-)
-for a beamed slurred pair of eighth notes.
+In version 2.0, postfix syntax will be the only syntax
+available, and the dashes will become optional.
-* Texts on multimeasure rests can be set by the user.
+** User code may now be executed during interpreting. The syntax for
+this code is
-* Zigzagged glissandi
+ \applycontext #SCHEME-FUNCTION
-* XML music output.
-* Preliminary Sodipodi/SVG output
+** User code may now be executed on arbitrary grobs during interpreting.
+The syntax for this feature is
-* Cluster support. Syntax:
+ \applyoutput #SCHEME-FUNCTION
- NOTE-\openCluster
- ..
- NOTE-\closeCluster
+SCHEME-FUNCTION takes a single argument, and is called for every grob
+that is created in the current context.
-* Beat grouping indications. Syntax:
+** New algorithms for chord-name formatting have been installed. They
+can be tuned and have ergonomic syntax for entering exceptions.
- #(set-time-signature 7 8 '(3 2 2))
+** Texts may now be put on multimeasure rests, eg.
-* User code evaluation during interpreting. Syntax
+ R1*20^\markup { "GP" }
- \applycontext #SCHEME-FUNCTION
+** Ancient notation now prints ligatures in Gregorian square neumes
+notation, roughly following the typographical style of the Liber
+hymnarius of Solesmes, published in 1983. Ligatures are still printed
+without the proper line breaking and horizontal spacing.
+
+** Glissandi can now be printed using the zigzag style.
+
+** Clusters may now be printed. The syntax is:
+
+ \apply #clusters-to-notes { NOTE NOTE .. }
-* Nested horizontal brackets for music analysis.
+** For irregular meters, beat grouping marks can be printed. The
+syntax for this is
- NOTE-\groupOpen
+ #(set-time-signature 7 8 '(3 2 2))
+
+** Nested horizontal brackets for music analysis can now be printed.
+
+ NOTE-\startGroup
..
- NOTE-\groupClose
+ NOTE-\stopGroup
+
+** Ottava brackets are now fully supported as a feature. The syntax
+is
+
+ #(set-octavation 1)
+
+** Metronome markings are printed when a \tempo command is processed.
+
+** Fingerings can be put on chords horizontally.
+
+** The appearance of various glyphs has been fine-tuned.
+
+** Different types of percent style repeats may now be nested.
+
+** The emacs support has been extended.
+
+** The manual has been completely revised and extended.
+
+
New features in 1.6 since 1.4
+=============================
* Support for figured bass and tablature.