lilypond-0.0.34

diff --git a/Documentation/faq.pod b/Documentation/faq.pod
index fac6903cb1d1575bcb96cdb66b7650f41ce944c0..b0096fd73a879dcab7ed03e993072b67b20c6e10 100644 (file)
--- a/Documentation/faq.pod
+++ b/Documentation/faq.pod
@@ -17,7 +17,7 @@ specify
 
 Q: I want a DOS/NT/W95 port.
 
-A0: Reconsider.  Try Linux.  It-s fun!
+A0: Reconsider.  Try Linux.  It's fun!
 
 A1: Currently (patchlevel 27), LilyPond (and flowerLib) compiles, links
 and runs on windhoos-nt, using the cygnus gnu port (release b17.1). 
@@ -26,18 +26,27 @@ Have a look at http://www.cygnus.com/gnu-win32.  To make LilyPond type
 make $OS. (I am not promising to maintain this platform, it is just that
 when having to use doze, i-m sometimes too lazy to reboot.)
 
-A2: I haven't had time to find a GCC crosscompiler to DOS/win (in rpm,
-please :).  
+A2: I haven't had time to find a GCC crosscompiler (*with* g++, mind you) to
+DOS/win (in rpm, please :).
+
 
 Q: Why GPL?
 
 A: Yes.
 
+
 Q: Why shouldn't I put all commands (\clef, \meter) inside the music?
 
 A: You should do what you like, but at some time we will enable
 quoting of music ("Stichnoten"). Besides if you are going to type an
-orchestral score, then you'd probably want to enter most of those
-commands only once.
+orchestral score, then you'd probably want to enter most of the meter,
+repeat commands only once.
+
 
+Q: Could you implement feature XXXX? It is really easy, just extend
+the syntax to allow YYYY!
 
+A: If it is reasonable, I'll add XXXX to the TODO list. In general
+finding a cute syntax (such as YYYY) isn't very hard. The complicated
+issue how to adapt the internals to do XXXX. The parser is really  a
+simple front end to the complicated internals.