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. Sh, 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.
+For development versions 'y' is odd.
- 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.
+ Version 1.4 is the latest stable release.
-Requirements
-============
+Compilation
+===========
- For the compilation and running of LilyPond you need some additional
-packages. Please refer to the installation instructions.
+ For compiling and running LilyPond please refer to the installation
+instructions. These instructions can be found when you unpack lilypond,
+as `lilypond-x.y.z/INSTALL.txt'.
NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file), you
don't have to compile LilyPond.
-Installation
-============
-
- For your convenience, a formatted copy of the INSTALL instructions
-are in the toplevel directory, as INSTALL.txt
-
Documentation
=============
- The real documentation is the directory Documentation/
-
- If you want to read the documentation online, these are options:
- * use HTML. Refer to INSTALL.txt for information on how to make the
- HTML documentation.
-
- * use HTML. Point your browser to
- `http://www.cs.uu.nl/~hanwen/lilypond/index.html'.
-
- * use `.dvi', for the tutorial and reference manual. Do
+ The documentation is available online at `http://www.lilypond.org/'.
+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.
- make -C Documentation/user/ dvi
+ * `.dvi', for the tutorial and reference manual. Do
- You need a working LilyPond binary to create the DVI and HTML
- sources.
+ make -C Documentation/user/ dvi
+ The printable documentation is left in `Documentation/user/out/'.
- * use ASCII. Do using
- make doc
+ * paper. Create the .dvi documentation, and print it with dvips.
Comments
========
- LilyPond is a long way from finished and polished. We do appreciate
-criticism, comments, bugreports, patches, etc., but please,
+ 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.
- Please send your e-mail to one of the MAILING LISTS
-
- and _not_ to us personally. We have the following mailing lists:
+ We have the following mailing lists:
* info-gnu-music@gnu.org
(http://mail.gnu.org/mailman/listinfo/info-gnu-music) is a
This list is moderated; ask David R. Linn <drl@gnu.org> or
Han-Wen <hanwen@cs.uu.nl> to send announcements for this list.
+ * gnu-music-discuss@gnu.org
+ (http://mail.gnu.org/mailman/listinfo/gnu-music-discuss) For
+ general discussions concerning LilyPond.
+
* help-gnu-music@gnu.org
(http://mail.gnu.org/mailman/listinfo/help-gnu-music) For help
with using LilyPond.
==========
If you have received this file as part of a DOS/Window32 distribution
-(`LilyPond-*.zip'), 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 section.
+(`LilyPond-*.zip'), it is advisable to also download the source package
+(ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/), since it might contain more
+documentation
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.
-
projects / lilypond.git / blobdiff