X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Ftopdocs%2FREADME.texi;h=2d6e26b99ee0c8e6ab5335ea56d7ffe5a53d3f30;hb=915e0d52760d9b9655c30dc6a4e410b749a8c6bd;hp=eeb64dca85a1c8e303deffed4a7d9449a268f353;hpb=82731e802565546441c401a84a13b486e54eb760;p=lilypond.git diff --git a/Documentation/topdocs/README.texi b/Documentation/topdocs/README.texi index eeb64dca85..2d6e26b99e 100644 --- a/Documentation/topdocs/README.texi +++ b/Documentation/topdocs/README.texi @@ -1,111 +1,89 @@ \input texinfo @c -*-texinfo-*- @setfilename README.info -@settitle This is the toplevel README to LilyPond -@node Top, , , +@settitle Toplevel README + +@documentencoding utf-8 +@documentlanguage en + +@node Top @top -@chapter This is the toplevel README to LilyPond +@chapter Toplevel README LilyPond is a music typesetter. It produces beautiful sheet music -using a high level description file as input. LilyPond is part of -the GNU Project. +using a description file as input. LilyPond is part of the GNU +Project. @section Versioning -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. For using straightforward score -production, please use the latest stable version. Development versions -may not produce good or nice scores. - -@section Requirements +LilyPond uses a versioning scheme that easily identifies stable and +development releases. In a version "x.y.z", an even second number 'y' +denotes a stable version. For development versions 'y' is odd. -For the compilation and running of LilyPond you need some additional -packages. Please refer to the installation instructions. +@section Downloading -NOTE: If you downloaded a binary (.rpm or a W95/NT .zip file), -you don't have to compile LilyPond. +The primary download site for sourcecode is +@uref{http://lilypond.org/download/}. -@section Installation +@section Compilation -For your convenience, a formatted copy of the INSTALL instructions are -in the toplevel directory, as INSTALL.txt +For compiling and running LilyPond see the installation instructions. +These instructions can be found when you unpack lilypond, as +@file{lilypond-x.y.z/INSTALL.txt}. They are also available on the web +at +@uref{http://lilypond.org/doc/v2.1/Documentation/topdocs/out-www/INSTALL.html}. @section Documentation -The real documentation is the directory Documentation/ - -If you want to read the documentation online, these are options: -@itemize @bullet - -@item use 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 - -@example - make -C Documentation/user/ dvi -@end example +The documentation is available online at +@uref{http://www.lilypond.org/doc/}. -You need a working LilyPond binary to create the DVI sources . - - -@item use ASCII. Do -using @example - make -C doc -@end example - -@end itemize +You can also build it locally: follow the instructions under `Building +documentation' in the installation instructions. @section Comments -LilyPond is a long way from finished and polished. We do appreciate -criticism, comments, bugreports, patches, etc., but please, -@example - - Please send your e-mail to one of the MAILING LISTS - -@end example - -and @emph{not} to us personally. See @file{Documentation/mail.texi} for -more info. - -@section Windows 32 - -If you have received this file as part of a DOS/Window32 distribution -(@file{LilyPond-*.zip}), it is advisable to also download the -source package, since it might contain more documentation -@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/} +Send your criticism, comments, bugreports, patches, etc. to the mailing +list, not to us personally. -If you decide to build LilyPond from source, please read the INSTALL.txt -document first, especially the Windows NT/95 section. +@html + +@end html -@section Caveats +We have the following mailing lists: -If you have installed a previous version, be sure to remove old font -files, eg., -@example -rm `find /var/lib/texmf/fonts -name 'feta*'` -@end example +@itemize @bullet +@item @uref{http://mail.gnu.org/mailman/listinfo/info-lilypond,info-lilypond@@gnu.org} +is a low-volume list for information on LilyPond project. + This list is moderated; ask + @email{drl@@gnu.org, David R. Linn} or + @email{hanwen@@xs4all.nl, Han-Wen} to send announcements for this +list. + +@item +@uref{http://mail.gnu.org/mailman/listinfo/lilypond-devel,lilypond-devel@@gnu.org} + for discussions about developing LilyPond, in particular the unstable series. + +@item @uref{http://mail.gnu.org/mailman/listinfo/lilypond-user,lilypond-user@@gnu.org} + for discussions about using LilyPond, in particular the stable series. + +@item @uref{http://mail.gnu.org/mailman/listinfo/bug-lilypond,bug-lilypond@@gnu.org} +for sending bugreports. + +@item @uref{http://mail.gnu.org/mailman/listinfo/lilypond-cvs,lilypond-cvs@@gnu.org} + for log files from the +autobuild. +@end itemize -a script to do this for you is in @file{buildscripts/clean-fonts.sh} +You can search the lists from our @uref{http://lilypond.org/search, +searching facilities}. @section Bugs -Send bug reports to @email{bug-gnu-music@@gnu.org}. For help and -questions use @email{help-gnu-music@@gnu.org} and -@email{gnu-music-discuss@@gnu.org}. Please consult the FAQ and -installation instructions before mailing your problems. - -@section 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. +Send bug reports to @email{bug-lilypond@@gnu.org}. For help and +questions use @email{lilypond-user@@gnu.org}. @bye