From: fred <fred>
Date: Sun, 24 Mar 2002 19:39:10 +0000 (+0000)
Subject: lilypond-0.0.51
X-Git-Tag: release/1.5.59~4965
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=0aba933eb273549dbb0d248a40153183aaff0abe;p=lilypond.git

lilypond-0.0.51
---

diff --git a/Documentation/index.pod b/Documentation/index.pod
index d6588acde2..b67f1543ff 100644
--- a/Documentation/index.pod
+++ b/Documentation/index.pod
@@ -1,12 +1,12 @@
 =head1 NAME
 
-LilyPond -- the Webpage
+GNU LilyPond -- the Webpage
 
 Excuse me for this poor page. I don't really have time for doing this..
 
 =head1 DESCRIPTION
 
-Technically LilyPond is a preprocessor which generates TeX
+Technically GNU LilyPond is a preprocessor which generates TeX
 (or LaTeX) output which contains information to typeset a musical
 score. Practically it is a typesetter, which only uses TeX as an
 output medium. (this is handy because there exist music fonts for TeX)
@@ -15,7 +15,7 @@ As a bonus, you can also output a MIDI file of what you typed.
 
 It translates script files (mudela files or F<*.ly>'s) into TeX input.
 Typesetting music is a complex task, whereas the message that printed
-music conveys is usually a simple one. LilyPond is a try at providing
+music conveys is usually a simple one. GNU LilyPond is a try at providing
 a simple interface for setting music.
 
 =head1 DOCUMENTATION
@@ -27,8 +27,12 @@ The installation instructions.
 </a
 >
 
-
-
+=item *
+<a href=MANIFESTO.html
+>
+Design criteria
+</a
+>
 
 =item *
 <a href=lilypond.html
diff --git a/Documentation/lilygut.pod b/Documentation/lilygut.pod
index a1b8497f52..99c15cea10 100644
--- a/Documentation/lilygut.pod
+++ b/Documentation/lilygut.pod
@@ -1,10 +1,10 @@
 =head1 NAME
 
-LilyGuts - doco to the internals of LilyPond
+LilyGuts - doco to the internals of GNU LilyPond
 
 =head1 DESCRIPTION
 
-This page documents some aspects of the internals of LilyPond. Some of
+This page documents some aspects of the internals of GNU LilyPond. Some of
 this stuff comes from e-mail I wrote, some from e-mail others wrote,
 some are large comments taken away from the headers
 
@@ -14,7 +14,7 @@ You should use doc++ to take a peek at the sources.
 
 =head1 OVERVIEW
 
-LilyPond is a "5-pass" system:
+GNU LilyPond is a "5-pass" system:
 
 =over 4
 
@@ -225,7 +225,7 @@ meter sign after the clef. Using the previous notation,
 
 	\discretionary{bar meter}{clef meter}{ bar meter }
 
-In Lilypond, we have the same concepts (and the same
+In GNU Lilypond, we have the same concepts (and the same
 terminology). Each (nonrhythmic) symbol is typeset using a Command
 (code: TYPESET). At a breakpoint, TYPESET commands can be grouped
 using separators (in lower case):
@@ -276,7 +276,7 @@ have been the subject of discussion in this thread).
 as you can see, these distance are conflicting. So instead of
 satisfying all those ideals simultaneously, a compromise is sought.
 
-This is Columbus' egg: LilyPond attaches "springs" to each
+This is Columbus' egg: GNU LilyPond attaches "springs" to each
 column-pair.  each spring has an equilibrium-position which is equal to
 the above mentioned distance, so
 
@@ -291,8 +291,8 @@ with minimum potential energy, for you physicists out there.
 This algorithm for doing one line, gives a "badness" parameter for
 each line (the potential energy). Now one can use TeX's algorithm for
 making paragraphs (using this new version of "badness"): one should
-try to minimise the overall badness of a paragraph. LilyPond also uses the
-concept of pre- and post-breaks.
+try to minimise the overall badness of a paragraph. GNU LilyPond also
+uses the concept of pre- and post-breaks.
 
 (actually, it is a bit more complicated: each column also has a
 minimum distance to other columns, to prevent symbols from running