CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch:
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/06/16 12:02:41
Modified files:
. : ChangeLog
Documentation/user: basic-notation.itely putting.itely
Log message:
New doc section on fixing overlapping notation.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?tr1=1.3789&tr2=1.3790&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/basic-notation.itely.diff?tr1=1.24&tr2=1.25&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/putting.itely.diff?tr1=1.3&tr2=1.4&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3789 lilypond/ChangeLog:1.3790
--- lilypond/ChangeLog:1.3789 Thu Jun 16 11:49:38 2005
+++ lilypond/ChangeLog Thu Jun 16 12:02:41 2005
@@ -1,3 +1,11 @@
+2005-06-16 Graham Percival <[EMAIL PROTECTED]>
+
+ * Documentation/user/basic-notation.itely: include ChoirStaff
+ in System start delimiters.
+
+ * Documentation/user/putting.itely: new doc section on
+ fixing overlapping notation.
+
2005-06-16 Han-Wen Nienhuys <[EMAIL PROTECTED]>
* Documentation/user/global.itely (Paper size): \paper is in
Index: lilypond/Documentation/user/basic-notation.itely
diff -u lilypond/Documentation/user/basic-notation.itely:1.24
lilypond/Documentation/user/basic-notation.itely:1.25
--- lilypond/Documentation/user/basic-notation.itely:1.24 Wed Jun 15
11:39:42 2005
+++ lilypond/Documentation/user/basic-notation.itely Thu Jun 16 12:02:41 2005
@@ -1250,9 +1250,10 @@
@cindex brace, vertical
@cindex grand staff
@cindex staff group
[EMAIL PROTECTED] staff, choir
Many scores consist of more than one staff. These staves can be
-joined in three different ways
+joined in four different ways
@itemize @bullet
@item The group is started with a brace at the left, and bar lines are
@@ -1278,6 +1279,17 @@
>>
@end lilypond
[EMAIL PROTECTED] The group is started with a bracket, but bar lines are not
+connected. This is done with the @internalsref{ChoirStaff} context.
+
[EMAIL PROTECTED],raggedright,quote]
+\new ChoirStaff
+\relative <<
+ \new Staff { c1 c }
+ \new Staff { c c }
+>>
[EMAIL PROTECTED] lilypond
+
@item The group is started with a vertical line. Bar lines are not
connected. This is the default for the score.
Index: lilypond/Documentation/user/putting.itely
diff -u lilypond/Documentation/user/putting.itely:1.3
lilypond/Documentation/user/putting.itely:1.4
--- lilypond/Documentation/user/putting.itely:1.3 Tue Jun 7 05:29:30 2005
+++ lilypond/Documentation/user/putting.itely Thu Jun 16 12:02:41 2005
@@ -8,6 +8,7 @@
@menu
* Suggestions for writing LilyPond files::
* Extending the templates::
+* Fixing overlapping notation::
@end menu
@@ -244,3 +245,63 @@
@end lilypond
+
[EMAIL PROTECTED] Fixing overlapping notation
[EMAIL PROTECTED] Fixing overlapping notation
+
+This may come as a surprise, but LilyPond isn't perfect. Some notation
+elements can overlap. This is unfortunate, but (in most cases) is easily
+solved.
+
[EMAIL PROTECTED],fragment,raggedright,verbatim,relative=2]
+e4^\markup{ \italic ritenuto } g b e
[EMAIL PROTECTED] lilypond
+
[EMAIL PROTECTED] padding
+
+The easiest solution is to increase the distance between the object
+(in this case text, but it could easily be fingerings or dynamics
+instead) and the note. In LilyPond, this is called the
[EMAIL PROTECTED] property. For most objects, it is around 1.0 or
+less (it varies with each object). We want to increase it, so let's
+try 1.5
+
[EMAIL PROTECTED],fragment,raggedright,verbatim,relative=2]
+\once \override TextScript #'padding = #1.5
+e4^\markup{ \italic ritenuto } g b e
[EMAIL PROTECTED] lilypond
+
+That looks better, but it isn't quite big enough. After experimenting
+with a few values, I think 2.3 is the best number. I leave this as an
+exercise for the reader.
+
[EMAIL PROTECTED] extra-offset
+
+Another solution gives us complete control over placing the object -- we
+can move it horizontally or vertically. This is done with the
[EMAIL PROTECTED] property. It is slightly more complicated and can
+cause other problems. When we move objects with @code{extra-offset},
+the movement is done after LilyPond has placed all other objects. This means
+that the result can overlap with other objects.
+
[EMAIL PROTECTED],fragment,raggedright,verbatim,relative=2]
+\once \override TextScript #'extra-offset = #'( 1.0 . -1.0 )
+e4^\markup{ \italic ritenuto } g b e
[EMAIL PROTECTED] lilypond
+
+With @code{extra-offset}, the first number controls the horizontal
+movement (left is negative); the second number controls the vertial
+movement (up is positive). After a bit of experimenting, I decided
+that these values look good
+
[EMAIL PROTECTED],fragment,raggedright,verbatim,relative=2]
+\once \override TextScript #'extra-offset = #'( -1.6 . 1.0 )
+e4^\markup{ \italic ritenuto } g b e
[EMAIL PROTECTED] lilypond
+
+
[EMAIL PROTECTED]
+
+This manual: @ref{The \override command}, @ref{Common tweaks}.
+
+
_______________________________________________
Lilypond-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
