X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Ftopdocs%2FREADME.texi;h=20a051f983d79a0c86d19e5eac90a962acdcf9bb;hb=3e0974be7b4d4ae1cedebeee8376093fe8816740;hp=d7eb7764b80bb7bbce6685cfdaeeabb9a77df5dc;hpb=e4a2733b4c0ab484305dc19fc598d70a9631539b;p=lilypond.git diff --git a/Documentation/topdocs/README.texi b/Documentation/topdocs/README.texi index d7eb7764b8..20a051f983 100644 --- a/Documentation/topdocs/README.texi +++ b/Documentation/topdocs/README.texi @@ -1,135 +1,89 @@ \input texinfo @c -*-texinfo-*- +@documentencoding utf-8 +@documentlanguage en @setfilename README.info -@settitle This is the toplevel README to LilyPond - -@node Top, , cdrom distributions, (dir) -@top -@menu -* This is the toplevel README to LilyPond::This is the toplevel README to LilyPond -@end menu - +@settitle Toplevel README +@node Top +@top -@node This is the toplevel README to LilyPond, versioning, , Top -@menu -* versioning:: versioning -* requirements:: requirements -* installation:: installation -* documentation:: documentation -* comments:: comments -* windows 32:: windows 32 -* caveats:: caveats -* bugs:: bugs -* cdrom distributions:: cdrom distributions -@end menu -@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. - -@node versioning, requirements, This is the toplevel README to LilyPond, This is the toplevel README to LilyPond -@section versioning +using a description file as input. LilyPond is part of the GNU +Project. -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 Versioning -@node requirements, installation, versioning, This is the toplevel README to LilyPond -@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), then -you don't have to compile LilyPond. +The primary download site for sourcecode is +@uref{http://lilypond.org/download/}. -@node installation, documentation, requirements, This is the toplevel README to LilyPond -@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.12/Documentation/topdocs/INSTALL.html}. -@node documentation, comments, installation, This is the toplevel README to LilyPond -@section documentation +@section Documentation -The real documentation is the directory Documentation/ - -If you want to read the documentation online, these are options: -@itemize @bullet -@item use @file{.html}. Refer to INSTALL.txt for info on how to make the -.html documentation. -@item use @file{.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/tex/ dvi -@end example - - -@item use ASCII. Do -using @example - make -C Documentation/ -@end example - -@end itemize +The documentation is available online at +@uref{http://lilypond.org/doc/}. +You can also build it locally: follow the instructions under `Building +documentation' in the installation instructions. -@node comments, windows 32, documentation, This is the toplevel README to LilyPond -@section comments -LilyPond is a long way from finished and polished. We do appreciate -criticism, comments, bugreports, patches, etc. -@example +@section Comments - Please send your e-mail to one of the MAILING LISTS - -@end example +Send your criticism, comments, bugreports, patches, etc. to the mailing +list, not to us personally. -and @emph{not} to us personally. See @file{Documentation/links.yo} for more info. +@html + +@end html -@node windows 32, caveats, comments, This is the toplevel README to LilyPond -@section windows 32 +We have the following mailing lists: -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 -@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. - -@node caveats, bugs, windows 32, This is the toplevel README to LilyPond -@section caveats - -* Please read the file BUGS for some ugly bugs. - -* 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 - -a script to do this for you is in @file{buildscripts/clean-fonts.sh} - -@node bugs, cdrom distributions, caveats, This is the toplevel README to LilyPond -@section bugs +@itemize @bullet +@item @uref{http://lists.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://lists.gnu.org/mailman/listinfo/lilypond-devel,lilypond-devel@@gnu.org} + for discussions about developing LilyPond, in particular the unstable series. + +@item @uref{http://lists.gnu.org/mailman/listinfo/lilypond-user,lilypond-user@@gnu.org} + for discussions about using LilyPond, in particular the stable series. + +@item @uref{http://lists.gnu.org/mailman/listinfo/bug-lilypond,bug-lilypond@@gnu.org} +for sending bugreports. + +@item @uref{http://lists.gnu.org/mailman/listinfo/lilypond-cvs,lilypond-cvs@@gnu.org} + for log files from the +autobuild. +@end itemize -Send bug reports to bug-gnu-music@@gnu.org. For help and questions use -help-gnu-music@@gnu.org and gnu-music-discuss@@gnu.org. Please consult -the faq before mailing your problems. +You can search the lists from our @uref{http://lilypond.org/search, +searching facilities}. -@node cdrom distributions, Top, bugs, This is the toplevel README to LilyPond -@section cdrom distributions +@section Bugs -if you have received LilyPond on a cdrom, chances are that development -has moved a 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