[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking c
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem |
Date: |
Tue, 20 May 2014 10:46:57 +0000 |
Updates:
Cc: address@hidden
Comment #20 on issue 3778 by address@hidden: SVG backend: tempo marking
collides with stem
http://code.google.com/p/lilypond/issues/detail?id=3778
28f3294954eff1f263d3b2e3de1c520f4d2fbdfc is the first bad commit
commit 28f3294954eff1f263d3b2e3de1c520f4d2fbdfc
Author: Mike Solomon <address@hidden>
Date: Mon Aug 27 23:47:04 2012 +0200
Improvements in vertical skyline approximations (issue 2148).
The file stencil-integral.cc provides a suite of functions that
traverse a stencil and do linear approximations of its components.
These are then turned into boxes that are passed to the Skyline
constructor. This approximation is used for several vertical skylines
including those of VerticalAxisGroup and System. As a result of these
more accurate approximations, vertical spacing is more snug between
grobs.
Additionally, in axis-group-interface.cc, skylines of grobs are no
longer compared to a monolithic axis-group skyline but rather all
of the component skylines of the axis-group, allowing grobs to
be fit under other ones if there is space instead of always shifted
over.
Two new python scripts allow to visualize the position of skylines.
All other changes provide functions that allow for better debugging
of Skylines, better approximations of grobs via skylines, and changes
to the measurement of distance between grobs via the new Skyline API.
This results in a significant time increase in score compilation for
objects with complex skylines such as all text grobs. For orchestral
scores, the increase is not as steep.
So it would appear that the skylining for SVG fonts is broken and the old
behavior has been replaced by a non-working one. The commit is quite
humongous, so pinpointing the relevant part is certainly non-trivial.
--
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
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, (continued)
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/19
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem,
lilypond <=
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/20
- Message not available
- Re: [Lilypond-auto] Issue 3778 in lilypond: SVG backend: tempo marking collides with stem, lilypond, 2014/05/23