summaryrefslogtreecommitdiff
path: root/README.txt
diff options
context:
space:
mode:
authorHan-Wen Nienhuys <hanwen@xs4all.nl>1999-05-10 11:03:26 +0200
committerHan-Wen Nienhuys <hanwen@xs4all.nl>1999-05-10 11:03:26 +0200
commit42ab6ff971c06253b34f96ed122836ab88d09cc0 (patch)
tree1b27b8e67da7e37a68bce762fc7d495a9f70ac9e /README.txt
parent1b071315c1d318e46035ec8bc0b73da55a025ae8 (diff)
release: 1.1.42
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt49
1 files changed, 17 insertions, 32 deletions
diff --git a/README.txt b/README.txt
index eee3265d47..be3bd2a836 100644
--- a/README.txt
+++ b/README.txt
@@ -19,35 +19,22 @@ odd. For using straightforward score production, please use
the latest stable version. Development versions may not
produce good or nice scores.
-If you have downloaded a
-
-*.pre*
-
-version, then this is version is *not* meant for producing
-nice output (but to keep your patchsets up to date). It
-might not even compile. The same goes for a version with a
-4th version number, eg
-
-1.2.3.mypatch2
-
-It will be safer if you download 1.2.3 or wait for 1.2.4.
-
2: REQUIREMENTS
-For the compilation and running of LilyPond you need some
+For the compilation and running of LilyPond you need some
additional packages. Please refer to the installation
instructions.
-NOTE: If you downloaded a binary (.rpm or a W95/NT .zip
+NOTE: If you downloaded a binary (.rpm or a W95/NT .zip
file), then you don't have to compile LilyPond.
3: INSTALLATION
-For your convenience, a formatted copy of the INSTALL
+For your convenience, a formatted copy of the INSTALL
instructions are in the toplevel directory, as INSTALL.txt
-The process is fairly straightforward, but chances are that
-you have to specify directories for to configure: this is
+The process is fairly straightforward, but chances are that
+you have to specify directories for to configure: this is
done with the options --enable-tex-dir and --enable-mf-dir
4: DOCUMENTATION
@@ -59,36 +46,35 @@ ure first, and then do this:
make doc
-You can also simply read the .yo sources. They are ASCII
+You can also simply read the .yo sources. They are ASCII
text. The complete documentation is accessible in formatted
-form at the website http://www.cs.uu.nl/people/hanwen/lily-
+form at the website http://www.cs.uu.nl/people/hanwen/lily-
pond/index.html
5: COMMENTS
-LilyPond is a long way from finished and polished. We do
+LilyPond is a long way from finished and polished. We do
appreciate criticism, comments, bugreports, patches, etc.
-Please send your e-mail to one of the MAILING LISTS
+ Please send your e-mail to one of the MAILING LISTS
-and not to us personally. See Documentation/links.yo for
+and not to us personally. See Documentation/links.yo for
more info.
6: WINDOWS 32
-If you have received this file as part of a DOS/Window32
-distribution (lilypond-*.zip), then it is advisable to also
-download the source package, since it might contain more
+If you have received this file as part of a DOS/Window32
+distribution (LilyPond-*.zip), then it is advisable to also
+download the source package, since it might contain more
documentation ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/
If you decide to build LilyPond from source, please read the
-INSTALL.txt document first, especially the Windows NT/95
+INSTALL.txt document first, especially the Windows NT/95
section.
7: CAVEATS
-* Please read the file BUGS for some ugly bugs. This espe-
-cially applies Linux-Intel unix users.
+* Please read the file BUGS for some ugly bugs.
* If you have installed a previous version, be sure to
remove old font files, eg
@@ -101,6 +87,5 @@ fonts.sh
8: CDROM DISTRIBUTIONS
If you have received LilyPond on a cdrom, chances are that
-development has moved a some patchlevels up. If possible,
-please check the latest version of LilyPond before reporting
-bugs.
+development has moved a some patchlevels up. Please check
+the latest version of LilyPond before reporting bugs.