Graham,
It looks good when you finally know where the bug resides - I have
omitted lots of other things before sending this report.
And then: why not reduce it to the shortest possible like in example 1
below?!
I have added two more cases to document another issue which is probably
related: Where do the dashes go?
In the 3rd example you can also see the justification to let lilypond do
the break rather than add it myself.
Thanks for your help + regards!
Luc
\version "2.11.28"
%{ when the Bar_engraver is removed and textSpanner text happens to span
over a line break the text on the first line is misplaced %}
\layout { \context { \Staff \remove "Bar_engraver" }}
% 1:
{ \override TextSpanner #'bound-details #'left #'text ="shortest"
e 1 \startTextSpan \break e \stopTextSpan
}
% 2:
{ \override TextSpanner #'bound-details #'left #'text ="here we see
dashes - at least on the 2nd line"
e \startTextSpan e \break e e \stopTextSpan
}
% 3:
{ \override TextSpanner #'bound-details #'left #'text ="where are the
dashes?"
e 2 \startTextSpan e e \break e e \stopTextSpan
}
Graham Percival schrieb:
Thanks for the report; this has been added as
http://code.google.com/p/lilypond/issues/detail?id=401
In the future, please try to create a minimal bug report -- I cut your
example down to six notes (you may want to see the item in the tracker).
Cheers,
- Graham
Luc wrote:
\version "2.11.28"
%{ when the Bar_engraver is removed and textSpanner text happens to
span over 2 lines, the text on the first line is misplaced %}
\layout { \context { \Staff \remove "Bar_engraver" } } { \clef "G_8"
\relative e, {
e 2 f fis g gis a ais b c cis d dis e f fis g gis a ais
\override TextSpanner #'bound-details #'left #'text = "2nd"
b \startTextSpan c cis d dis \stopTextSpan
e f fis g gis a ais b c cis d dis e f fis g gis a ais b }}
Not too important, but you might like to know! Thanks
Luc
_______________________________________________
bug-lilypond mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/bug-lilypond