* mf/GNUmakefile: always trace pfa fonts.

[lilypond.git] / Documentation / user / preface.itely

diff --git a/Documentation/user/preface.itely b/Documentation/user/preface.itely
index 18e1186b01e21c3441effe63b66cf6ae566b905a..91b7c6bc22657585a3f6d0ffc0ed5d3b23acd60c 100644 (file)
--- a/Documentation/user/preface.itely
+++ b/Documentation/user/preface.itely
@@ -1,8 +1,65 @@
 @comment @c -*-texinfo-*-
 
+
 @node Preface
 @unnumbered Preface
 
+@menu
+* Preface to version 2.0::
+* Preface to version 1.8::
+* Preface to version 1.6::
+@end menu
+
+
+@node Preface to version 2.0
+@unnumberedsec Preface to version 2.0
+
+
+Due to personal circumstances, Han-Wen was able to do a lot more on
+LilyPond during the past months. A testament to that is the quick
+release of version 2.0, less than two months after 1.8. We have taken
+the opportunity to make a few radical changes to the syntax: note
+attributes, like articulation, dynamics and fingerings are now
+post-fix exclusively. This makes entering scores easier: you never
+have to think about the order of the attributes.  With version 2.0, we
+have a new and improved platform for working on notation and
+typography features for coming versions,
+ 
+Due to other personal circumstances, Jan was not able to do more than
+packaging for Cygwin.  The good news is that we now have a nearly
+fool-proof installation for Windows.  He will be back in 2.1.
+
+
+Han-Wen and Jan
+
+Utrecht/Eindhoven, The Netherlands, September 2003.
+
+@node Preface to version 1.8
+@unnumberedsec Preface to version 1.8
+
+If you are familiar with LilyPond version 1.6, then version 1.8 will
+no offer no big surprises. The only conspicuous change is in the way
+that formatted text is entered. There is now a new syntax that is more
+friendly, more versatile and extensible. We hope you like it.  In
+general, development on version 1.8 has been focused on improving the
+design of various internal mechanisms.  This includes chord name
+formatting and entry code, music expression storage, and integration
+between LilyPond and Scheme.  These changes may not be evident
+directly, but they make the program more robust and more flexible,
+which translates into fewer bugs and more adjustment options.
+
+Special thanks for version 1.8 go out to Juergen Reuter for lots of
+work on the ancient notation engine, and to Amy Zapf for pushing us to
+rewrite the chord name support.
+
+@c TODO [wie meer?]  
+
+Han-Wen and Jan, 
+
+Utrecht/Eindhoven, The Netherlands, April/May 2003.
+
+@node Preface to version 1.6
+@unnumberedsec Preface to version 1.6
 
 It must have been during a rehearsal of the EJE (Eindhoven Youth
 Orchestra), somewhere in 1995 that Jan, one of the cranked violists