> the last time i asked for help with my score, i was told not to report
> bugs in old versions of lilypond. now i'm finally up-to-date, so you
> can't get around me that way this time. :)
>
> the score's at:
>
> http://www4.smart.net/~jcovey/tmp/smith/
>
> i've just looked at the first page so far. four questions:
>
> 1. why are the harmonic notations ("Art. Harm XV" and "XII Harm")
> missing?
Since you have set textStyle="finger", which gives a font that only
includes the numbers 0-9. You should never need to specify the
"finger" textStyle explicitly, since it's chosen automatically for
fingerings, for example when you write c^2.
> 2. why is the "pp" written over top of the note?
The patch included below makes this customizable. You could then set
the distance between the dynamics and the closest note or note line
using the property Voice.dynamicPadding. (I don't have the right
computer here to be able to compile Lilypond, so I haven't tried the
patch myself, but hopefully it should work)
> 3. why are "2", "1", and "1" on the second line touching the note
> heads?
Set the property Voice.textScriptPadding to add the distance.
> 4. why are there two "1"s under the first note in the bottom part?
Probably since you add one in guitartwo and one in bass_fingerings.
> and one comment:
>
> the tuplet braces are *much* better now, but there are still
> occasional problems. look at the triplet marking in the lower part in
> lines two and three; it sits right on the staff line, and is invisible.
Yes, some more intelligence is needed in the algorithm which decides the
positioning.
/Mats
The patch:
diff -urN ../lilypond-1.1.49/lily/dynamic-engraver.cc lily/dynamic-engraver.cc
--- ../lilypond-1.1.49/lily/dynamic-engraver.cc Fri May 28 10:16:00 1999
+++ lily/dynamic-engraver.cc Wed Jun 23 08:46:26 1999
@@ -133,7 +133,13 @@
staff_side_p_->dir_ = (Direction) (int) prop;
}
-
+ prop = get_property ("dynamicPadding", 0);
+ if (prop.isnum_b ())
+ {
+ staff_side_p_->set_elt_property (padding_scm_sym,
+ gh_double2scm(Real(prop)));
+ }
+
announce_element (Score_element_info (text_p_, absd));
announce_element (Score_element_info (staff_side_p_, absd));
}