Trevor Bača gmail.com> writes:
> (I personally think that at least dynamics should exhibit baseline
> alignment by default, but at least there's an easy workaround with
> definitions like those above.)
Any text that aligns horisontally, should align on the baseline. For latin
scripts at least.
On 12/3/06, Orm Finnendahl <[EMAIL PROTECTED]> wrote:
Hi Mats,
thanks for the reply.
Am 03. Dezember 2006, 20:33 Uhr (+0100) schrieb Mats Bengtsson:
> This problem has been discussed before and in the mailing list
> archives
do you have any idea how the thread was called? I presume, the
workar
Hi Mats,
thanks for the reply.
Am 03. Dezember 2006, 20:33 Uhr (+0100) schrieb Mats Bengtsson:
> This problem has been discussed before and in the mailing list
> archives
do you have any idea how the thread was called? I presume, the
workaround is similar to using a \strut box in TeX?
--
Orm
This problem has been discussed before and in the mailing list
archives, you can find some tricks to get the desired alignment
using hidden letters, but I agree that it should be handled
better by default.
/Mats
Quoting Orm Finnendahl <[EMAIL PROTECTED]>:
Hi,
as a follow-up: The same seems
Hi,
as a follow-up: The same seems to apply for TextSpanners in
general. In the following example, the baselines of the s.t. and
s.p. aren't aligned either:
\override TextSpanner #'edge-text = #'("s.t." . " s.p.")
f2~ \startTextSpan f2 \stopTextSpan |
It looks pretty bad and the only fix in t
Hi,
I observed a nasty behaviour trying to set the #'padding property of
the DynamicLineSpanner: The \p and \pp are not baseline-aligned with
the \ff or \mf.
Has this been reported before? To me this looks like something which
should rather get corrected in lilypond itself than cluttering the
scr
