lilypond-0.0.43

diff --git a/ANNOUNCE b/ANNOUNCE
index df31a15ba0eb004dd2a269af60180847d21d084a..afcf2ffd5dcea4e8282c8ecfc054f67de75ae244 100644 (file)
--- a/ANNOUNCE
+++ b/ANNOUNCE
@@ -1,4 +1,4 @@
-[Draft version]
+
 [Draft version]
 
 CALL FOR HACKERS: LilyPond, the Music Typesetter

diff --git a/Documentation/faq.pod b/Documentation/faq.pod
index 2c5ceb2cb97673829fa6bbb792e9bb841cb18bab..d63883106d0e61c4af45280c52615cbd227e6407 100644 (file)
--- a/Documentation/faq.pod
+++ b/Documentation/faq.pod
@@ -6,6 +6,40 @@ FAQ - LilyPond FAQs
 
 Some questions that have been answered before.
 
+Q: I can type
+
+       <a c> <e g>
+
+to make a few chords, but why do I have to type
+
+
+       < { a() e } { c () g } >
+
+in stead of
+
+       <a( c(> <)e )g>
+
+to generate  slurs between the chords?
+
+A: When you type 
+
+       <a c> <e g>
+
+this is shorthand for
+
+       < { a } { c } > < { e } { g } >
+
+Slurs have to be confined to `voices', and the a and the e are in
+different {} blocks, so they are in different voices. You should view
+the desired construct as a "generalised chord" (two voices stacked
+vertically). It might help you visualise this by using the following
+formatting:
+
+       < { a () e }
+         { c () g }
+       >
+
+
 Q: Why are [] around the notes, and () inbetween?
 
 A: [] designate beams, a note can only be in one beam at the same