LilyPond uses a versioning scheme similar to the Linux kernel. In a
version "x.y.z", an even second number 'y' denotes a stable version.
-For development versions 'y' is odd. So, in theory, version 1.2 is
-stable, which means that there are no glaring errors in it. In practice
-1.2.x is also unmaintained.
-
- 1.3.x is in healthy development: lots of problems turn up, but
-they're fixed quickly. Therefore we recommend you try 1.2.x, if you
-have any problem with it, upgrade to the latest 1.3.x release.
+For development versions 'y' is odd. For using straightforward score
+production, please use the latest stable version. Development versions
+may not produce good or nice scores.
Requirements
============
For the compilation and running of LilyPond you need some additional
-packages. Please refer to the installation instructions in
-`INSTALL.txt'.
+packages. Please refer to the installation instructions.
NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file), you
don't have to compile LilyPond.
Documentation
=============
- The documentation is available online at
-`http://www.cs.uu.nl/~hanwen/lilypond/index.html'. You can also build
-it locally. This does require a working LilyPond binary. The following
-formats are supported:
- * HTML. Refer to INSTALL.txt for information on how to make the HTML
- documentation.
+ The real documentation is the directory Documentation/
- * `.dvi', for the tutorial and reference manual. Do
+ If you want to read the documentation online, these are options:
+ * use `.html'. Refer to INSTALL.txt for info on how to make the
+ .html documentation.
- make -C Documentation/user/ dvi
- The printable documentation is left in `Documentation/user/out/'.
+ * use `.html'. Point your browser to
+ `http://www.cs.uu.nl/~hanwen/lilypond/index.html'.
- * paper. Create the .dvi documentation, and print it with dvips.
+ * use `.dvi', for the tutorial and reference manual. Do
+ make -C Documentation/user/ dvi
-Comments
-========
+ * use ASCII. Do using
+ make -C doc
- LilyPond is a long way from finished and polished, so we please send
-your criticism, comments, bugreports, patches, etc., to the mailing
-list. and _not_ to us personally.
- We have the following mailing lists:
-
- * info-gnu-music@gnu.org
- (http://mail.gnu.org/mailman/listinfo/info-gnu-music) is a
- low-volume list for information on the GNU Music project.
- This list is moderated; ask David R. Linn <drl@gnu.org> or
- Han-Wen <hanwen@cs.uu.nl> to send announcements for this list.
+Comments
+========
- * gnu-music-discuss@gnu.org
- (http://mail.gnu.org/mailman/listinfo/gnu-music-discuss) For
- general discussions concerning LilyPond.
+ LilyPond is a long way from finished and polished. We do appreciate
+criticism, comments, bugreports, patches, etc.
- * help-gnu-music@gnu.org
- (http://mail.gnu.org/mailman/listinfo/help-gnu-music) For help
- with using LilyPond.
+ Please send your e-mail to one of the MAILING LISTS
- * bug-gnu-music@gnu.org
- (http://mail.gnu.org/mailman/listinfo/bug-gnu-music) If you have
- bugreports, you should send them to this list.
+ and _not_ to us personally. See `Documentation/mail.texi' for more
+info.
Windows 32
==========
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 section.
+
Caveats
=======
consult the FAQ and installation instructions before mailing your
problems.
+CDROM distributions
+===================
+
+ If you have received LilyPond on a cdrom, chances are that
+development has moved some patchlevels up. Please check the latest
+version of LilyPond before reporting bugs.
+