Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem

[lilypond]

Comment #10 on issue 3778 by address@hidden: SVG backend: tempo  
marking collides with stem
http://code.google.com/p/lilypond/issues/detail?id=3778

> I'm not sure what to think about it. But officially for this to be a  
> (blocking)
> regression, this should have been working _on purpose_ before, that is,  
> someone
> has done something specific about it to work correctly.

Sorry, but that just ain't true. If something was working before - even by  
accident - it should still be working in a new release.

This being said: the bug is really strange. The tempo marking goes up with  
certain notes, and not with others. In other words: it's not always sitting  
at the same height above the staff. For example in the minimal example I  
give, when one leaves out the starting rest (R1), it behaves correctly.

To complicate things further, look atht efollowing example, which matches  
more what one does for larger scores:

\version "2.18.2"

music = \relative c''' {  \grace s16 R1 \repeat unfold 5 { c4 f e b } }
global = \relative c''' { \tempo "Allegro Moderato" 4=120 s1 s1*4}

\score {
  \new Staff { << \global \music >> }
}


If one leaves out the leading grace note on the music variable, the result  
is different. The tempo marking shift up a little bit, but not enough.   
Having the grace spacer rest, buit not the R1 makes the tempo marking shift  
up further, but still not enough. It is only removing both the grace spacer  
rest and the R1 that gives a correct result.

So with the four permutations (grace present or not, R1 present or not),  
one gets four different results.

Don't know if this helps...

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings