release: 0.1.57

[lilypond.git] / Documentation / faq.pod

diff --git a/Documentation/faq.pod b/Documentation/faq.pod
index 76ad9e5ddb8806fc6c12339a0115c926e15df5fa..9611c995d0d571a66023c1bf134166e17cef2a47 100644 (file)
--- a/Documentation/faq.pod
+++ b/Documentation/faq.pod
@@ -9,6 +9,14 @@ are meant to be relative to the source directory)
 
 =head2 Installing
 
+Q: Wow, the webpages look really neat, but if I install the .exe file
+on my windows 3.11 machine, it doesn't work.
+
+A: The DOS port is done with the cygnus W32 port of the GNU utils. It
+does I<not> work with windows 3.x; you need NT or w95 (this is not a
+recommendation, btw.  We recommend you use Unix, in particular, use
+GNU/Linux)
+
 Q: I get all kinds of errors while  compiling F<parser.cc>
 
 A: LilyPond uses features of bison version 1.25. Please confirm that
@@ -21,8 +29,8 @@ If the problem persists, then please mail me.
 Q: Some of your neat scripts fail, what directories do you use:
 
 A: [This only applies if you don't do C<make install>, and develop out
-of the source directory]
-I have a directory which contains all music related stuff,
+of the source directory] I have a directory which contains all music
+related stuff,
 
        ~/something/
 
@@ -172,10 +180,9 @@ elements.)
 
 Q: Do you support multiple staff-sizes?
 
-A: Yes and no.  At this time you can choose between 16 or 20 pt
-staff-size (you can have other sizes, but you need to tinker with the
-fonts to get those).  The sizes can't be changed per staff (yet).
-Look at F<standchen.ly> for an example.
+A: Yes and no.  At this time you can choose between 11, 13, 16, 19,
+20, 23 and 20 pt staff-size.  The sizes can't be changed per staff
+(yet).  Look at F<standchen.ly> for an example.
 
 
 =head2 How do I ....
@@ -216,6 +223,11 @@ or use spacing-notes to put markings at different horizontal positions
        >
 
 
+Q: How do I get bar numbers?
+
+A: See F<init/engraver.ly>.  You have to uncomment some entries.  To
+do this  `portably' you should redefine some engravers in your own
+source files.  Check out F<init/rhythm.ly>.
 
 =head2 Development
 
@@ -294,6 +306,14 @@ Q: Why GPL?
 A: Yes.
 
 
+Q: Your make system does not adhere to GNU coding standards, could you
+please fix it?
+
+A: No.  We have evaluated the standard GNU combination for compiling
+programs (autoconf, automake, libtool) and found to be inadequate in
+several respects.  More detailed argumentation is included with
+LilyPond (see F<automake.urgh>)
+
 Q: Why do I need g++ >= 2.7?
 
 A: By using g++, GNU LilyPond is portable to all platforms which support
@@ -350,6 +370,12 @@ LD_LIBRARY_PATH to a directory containing F<libflower.so>
 
 =head2 DOZE
 
+Q: I downloaded the W95 port, and it doesn't match the website!
+
+A: The website is usually made from the latest snapshots.  The W95
+binaries are only made every once in a while.  They can lag several
+versions behind the latest version. 
+
 Q: I want a DOS/NT/W95 port.
 
 A.0: Reconsider.  Try Linux.  It's fun!