release: 1.3.145

[lilypond.git] / Documentation / topdocs / README.texi

diff --git a/Documentation/topdocs/README.texi b/Documentation/topdocs/README.texi
index 5c0af13b71a101030df496b32511e663acf99b99..c10fa8db2add931b92c8877d76242eac1cf040cf 100644 (file)
--- a/Documentation/topdocs/README.texi
+++ b/Documentation/topdocs/README.texi
@@ -26,7 +26,8 @@ problem with it, upgrade to the latest 1.3.x release.
 @section Requirements
 
 For the compilation and running of LilyPond you need some additional
-packages.  Please refer to the installation instructions.
+packages.  Please refer to the installation instructions in
+@file{INSTALL.txt}.
 
 NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file),
 you don't have to compile LilyPond.
@@ -38,50 +39,47 @@ in the toplevel directory, as INSTALL.txt
 
 @section Documentation
 
-The real documentation is the directory Documentation/
-
-If you want to read the documentation online, these are options:
+The documentation is available online at
+@uref{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:
 @itemize @bullet
 
-@item  use HTML. Refer to INSTALL.txt for information
+@item HTML. Refer to INSTALL.txt for information
 on how to make the HTML documentation.
 
-@item  use HTML. Point your browser to
-@uref{http://www.cs.uu.nl/~hanwen/lilypond/index.html}.
-@item use @file{.dvi},  for the tutorial and reference manual. Do
-
+@item @file{.dvi},  for the tutorial and reference manual. Do
 @example 
-  make -C Documentation/user/ dvi 
-@end example 
 
-You need a working LilyPond binary to create the DVI and HTML sources.
+ make -C Documentation/user/ dvi 
 
-@item  use ASCII. Do
-using @example 
-       make doc
 @end example 
+The printable documentation is left in @file{Documentation/user/out/}.
+
+@item paper. Create the .dvi documentation, and print it with dvips.
 
 @end itemize
 
 
 @section Comments
 
-LilyPond is a long way from finished and polished.  We do appreciate
-criticism, comments, bugreports, patches, etc., but please,
-@example 
+LilyPond is a long way from finished and polished, so we please send
+your criticism, comments, bugreports, patches, etc., to the mailing
+list.  and @emph{not} to us personally.
 
-          Please send your e-mail to one of the MAILING LISTS
- 
-@end example 
-
-and @emph{not} to us personally. We have the following mailing lists:
+We have the following mailing lists:
 
 @itemize @bullet
 @item @uref{http://mail.gnu.org/mailman/listinfo/info-gnu-music,info-gnu-music@@gnu.org}
 is a low-volume list for information on the GNU Music project.
     This list is moderated; ask 
     @email{drl@@gnu.org, David R. Linn} or
-    @email{hanwen@@cs.uu.nl, Han-Wen} to send announcements for this list.
+    @email{hanwen@@cs.uu.nl, Han-Wen} to send announcements for this
+list.
+@item
+@uref{http://mail.gnu.org/mailman/listinfo/gnu-music-discuss,gnu-music-discuss@@gnu.org}
+  For general discussions concerning LilyPond.
+
 @item @uref{http://mail.gnu.org/mailman/listinfo/help-gnu-music,help-gnu-music@@gnu.org}
     For help with using LilyPond.
 @item @uref{http://mail.gnu.org/mailman/listinfo/bug-gnu-music,bug-gnu-music@@gnu.org}
@@ -96,9 +94,6 @@ If you have received this file as part of a DOS/Window32 distribution
 source package, since it might contain more documentation
 @uref{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.
-
 @section Caveats
 
 If you have installed a previous version, be sure to remove old font