Mats,
I tried incorporating your suggestions with mixed success. The
following definition works:
mpdolce = #(make-dynamic-script (markup #:hspace 0 #:translate '(5 . 0)
#:line(#:dynamic "mp" #:text #:italic "dolce" )))
I changed the (cons 5 0) as you suggested, and changed hspace value to 0.
I tried fooling around with the horizontal alignment but ran into the
problem you mentioned with #:translate. When I changed that to
#:left-align it had no effect at all (of course, but I had to fiddle a
bit before I even understood the problem you described below). Changing
the default alignment for predefined vs. user-defined dynamic texts is
something beyond my skills, so my instinct is to keep the #:translate
command in this macro for now.
Does that sound ok?
Jon
Mats Bengtsson wrote:
mpdolce = #(make-dynamic-script (markup #:hspace 1 #:translate (cons 5 0)
#:line(#:dynamic "mp" #:text #:italic "dolce" )))
It seems that the above line is copied from the current documentation
but it seems a bit weird:
- I don't understand why we need the #:hspace 1 (there are some similar
examples in the NR, but they use #:hspace 0, which makes somewhat more
sense.
- Using #:translate is in my opinion just a silly way of fooling the
default implementation that automatically gives centered alignment of
the full markup. I know that this issue has been discussed in length
several times and I haven't had the time to follow all the arguments,
but my intuitive idea of how to solve the problem is rather to turn of
the automatic centering set the alignment point explicitly both for the
predefined dynamics and for user defined ones.
- Is there any good reason to use (cons 5 0) instead of '(5 . 0)? The
latter is the syntax used for most other settings in the documentation
where the value is a pair, but for some reason the person who first
documented the \translate markup command choose to use cons instead and
this habit has been copied all over the manual.
/Mats
--
Jonathan Kulp
http://www.jonathankulp.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
