Hi,

considering the recent misreading of lily's Gregorian chant capabilities that could be seen on this list, I would like to propose a minor update with clarifications to Sect. 7.7.10.2. See attachment.

Greetings,
Juergen
Index: Documentation/user/instrument-notation.itely
===================================================================
RCS file: 
/cvsroot/lilypond/lilypond/Documentation/user/instrument-notation.itely,v
retrieving revision 1.80
diff -u -r1.80 instrument-notation.itely
--- Documentation/user/instrument-notation.itely        5 Apr 2006 00:01:18 
-0000       1.80
+++ Documentation/user/instrument-notation.itely        12 Apr 2006 23:37:30 
-0000
@@ -3881,6 +3881,20 @@
 @code{\[ \stropha b \stropha b \stropha a \]}
 @end multitable
 
+The ligatures listed above mainly serve as a limited, but still
+representative pool of Gregorian ligature examples.  Virtually, within
+the ligature delimiters @code{\[} and @code{\]}, any number of heads
+may be accumulated to form a single ligature, and head prefixes like
[EMAIL PROTECTED], @code{\flexa}, @code{\virga}, @code{\inclinatum},
+etc. may be mixed in as desired.  The use of the set of rules that
+underlies the construction of the ligatures in the above table is
+accordingly extrapolated.  This way, infinitely many different
+ligatures can be created.
+
[EMAIL PROTECTED] TODO: create a regression or tips & tricks example document 
with
[EMAIL PROTECTED] even more Gregorian ligatures, and add a link to this document
[EMAIL PROTECTED] here.
+
 @refcommands
 
 The following head prefixes are supported
@@ -3902,7 +3916,11 @@
 @cindex @code{\quilisma}
 @code{\quilisma},
 @cindex @code{\deminutum}
[EMAIL PROTECTED]
[EMAIL PROTECTED],
[EMAIL PROTECTED] @code{\cavum}
[EMAIL PROTECTED],
[EMAIL PROTECTED] @code{\linea}
[EMAIL PROTECTED]
 
 Head prefixes can be accumulated, though restrictions apply.  For
 example, either @code{\descendens} or @code{\ascendens} can be applied
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to