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

[lilypond]

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

Excellent sleuth work.  debug-skylines makes it quite clear that it is  
indeed not just the backend but also LilyPond that has a different notion  
of the content metrics.

That would seem to suggest that the font access is different, and leads to  
different results.

Taking some closer look at LilyPond's options, it would seem that a single  
run has just _one_ backend but may have different _formats_.  So the output  
_including_ LilyPond's idea of it (metrics) would seem to depend on the  
backend.

I'm currently doing a bisection (it's somewhere between 2.17.0 and 2.17.1).

--
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