Merge branch 'master' of carldsorensen@git.sv.gnu.org:/srv/git/lilypond into ralph

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

diff --git a/Documentation/user/preface.itely b/Documentation/user/preface.itely
index 5540ea0250a74d90ea74ad5519ce6ceb96d5911a..d82632e77f55985fd26339759a26318fe4cdb1f5 100644 (file)
--- a/Documentation/user/preface.itely
+++ b/Documentation/user/preface.itely
@@ -1,60 +1,59 @@
-@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
+
+@c \version "2.12.0"

 
 @node Preface
 @unnumbered Preface
 
 
 It must have been during a rehearsal of the EJE (Eindhoven Youth
 
 @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
-told Han-Wen, one of the distorted french horn players, about the
+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
 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 e-mail exchanges Han-Wen started
+quickly got hooked.  It was decided that MPP was a dead end.  After
+lots of philosophizing and heated email exchanges, Han-Wen started

 LilyPond in 1996.  This time, Jan got sucked into Han-Wen's new
 project.
 
 In some ways, developing a computer program is like learning to play
 LilyPond in 1996.  This time, Jan got sucked into Han-Wen's new
 project.
 
 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 can't do are challenging. After the initial excitement,
-you have to practice and practice. Scales and studies can be dull, and
-if you aren't motivated by others, be them teachers, conductors or
-audience, it is very tempting to give up. You continue, and gradually
-playing it becomes a part of your life. Some days it comes naturally,
-and it's wonderful, and on some days it just doesn't work, but you
-keep playing, day after day.
-
-Like making music, working on LilyPond is can be dull work, and on
-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 use it to produce
-impressive pieces of sheet music.  Seeing that still feels unreal, but
-in a very pleasant way.
+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
+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.
+
+Like making music, working on LilyPond can be dull work, and on
+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 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
 
 Our users not only give us good vibes by using our program, many of

-them also help us by giving suggestions and sending bugreports. So,
-first and foremost, we would like to thank all users that sent us
-bugreports, gave suggestions or contributed in any other way to
-LilyPond.
-
-We would especially like to thank the following people: Mats Bengtsson
-for the incountable number of questions he answered on the mailing
-list, and Rune Zedeler for his energy in finding and fixing bugs.
-Nicola Bernardini for inviting us to his workshop on music publishing,
-which was truly a masterclass, and Heinz Stolba and James Ingram for
-teaching us there. [wie nog meer?]
-
-Playing and printing music is more than nice analogy: programming
+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 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
 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!
+music.  May it help you create lots of beautiful music!

 
 Han-Wen and Jan
 
 Utrecht/Eindhoven, The Netherlands, July 2002.
 
 
 Han-Wen and Jan
 
 Utrecht/Eindhoven, The Netherlands, July 2002.
 

-