Merge with master

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

diff --git a/Documentation/user/preface.itely b/Documentation/user/preface.itely
index aaca1f9f493461588257d5f205302a0340417009..a4d8f295eaf9b4c9f3ec9a57221172d97c5b2761 100644 (file)
--- a/Documentation/user/preface.itely
+++ b/Documentation/user/preface.itely
@@ -1,18 +1,25 @@
-@comment @c -*-texinfo-*-
+@c -*- coding: utf-8; mode: texinfo; -*-
+@c This file is part of lilypond.tely
+@ignore
+    Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
+
+    When revising a translation, copy the HEAD committish of the
+    version that you are working on.  See TRANSLATION for details.
+@end ignore
 
 @node Preface
 @unnumbered Preface
 
 
 It must have been during a rehearsal of the EJE (Eindhoven Youth
-Orchestra), somewhere in 1995 that Jan, one of the cranked violists
+Orchestra), somewhere in 1995 that Jan, one of the cranked violists,
 told Han-Wen, one of the distorted French horn players, about the
 grand new project he was working on.  It was an automated system for
 printing music (to be precise, it was MPP, a preprocessor for
 MusiXTeX).  As it happened, Han-Wen accidentally wanted to print out
 some parts from a score, so he started looking at the software, and he
 quickly got hooked.  It was decided that MPP was a dead end.  After
-lots of philosophizing and heated email exchanges Han-Wen started
+lots of philosophizing and heated email exchanges, Han-Wen started
 LilyPond in 1996.  This time, Jan got sucked into Han-Wen's new
 project.
 
@@ -20,8 +27,8 @@ In some ways, developing a computer program is like learning to play
 an instrument.  In the beginning, discovering how it works is fun, and
 the things you cannot do are challenging.  After the initial excitement,
 you have to practice and practice.  Scales and studies can be dull, and
-if you are not motivated by others---teachers, conductors or
-audience---it is very tempting to give up.  You continue, and gradually
+if you are not motivated by others -- teachers, conductors or
+audience -- it is very tempting to give up.  You continue, and gradually
 playing becomes a part of your life.  Some days it comes naturally, and
 it is wonderful, and on some days it just does not work, but you keep
 playing, day after day.
@@ -31,7 +38,7 @@ some days it feels like plodding through a morass of bugs.
 Nevertheless, it has become a part of our life, and we keep doing it.
 Probably the most important motivation is that our program actually
 does something useful for people.  When we browse around the net we
-find many people that use LilyPond, and produce impressive pieces of
+find many people who use LilyPond, and produce impressive pieces of
 sheet music.  Seeing that feels unreal, but in a very pleasant way.
 
 Our users not only give us good vibes by using our program, many of
@@ -39,7 +46,7 @@ them also help us by giving suggestions and sending bug reports, so we
 would like to thank all users that sent us bug reports, gave
 suggestions or contributed in any other way to LilyPond.
 
-Playing and printing music is more than nice analogy.  Programming
+Playing and printing music is more than a nice analogy.  Programming
 together is a lot of fun, and helping people is deeply satisfying, but
 ultimately, working on LilyPond is a way to express our deep love for
 music.  May it help you create lots of beautiful music!
@@ -48,22 +55,3 @@ Han-Wen and Jan
 
 Utrecht/Eindhoven, The Netherlands, July 2002.
 
-@menu
-* Notes for version 2.4::       
-@end menu
-
-@node Notes for version 2.4
-@unnumberedsec Notes for version 2.4
-
-The most important developments in 2.4 are related.  In LilyPond 2.4
-@TeX{} is no longer strictly necessary to engrave music.  This is
-because LilyPond can now also layout pages and determine page breaks.
-Another notable feature is the syntax, which has been simplified even
-further compared to previous versions.
-
-
-
-
-Han-Wen and Jan
-
-Utrecht/Eindhoven, The Netherlands, September 2004.