On 2012/06/10 16:09:03, dak wrote:
On 2012/06/10 15:58:25, MikeSol wrote: > This fixes Issue 2574 but also deals with the
footnote-break-visibility
regtest, > which currently does not register the property change (this may have
something
> to do with the footnote engraver being on the Score level).
I'll readily admit that the footnote engraver being at Score level may
be a
source for new problems. However, automatic footnotes get a number
for each
time they hit an engraver, and footnotes may occur at pretty much any
level. So
I don't really see a way around having the engraver registered at
Score level by
default.
Moving it to lower levels may be a user-level option, but it comes at
the cost
of some elements no longer being available for footnoting. So it
would be good
if we could get the Score-level footnote engraver working well.
It's worth mentioning in the change log and perhaps a convert-ly NOT_SMART rule. A once-over of the footnote regtests wouldn't hurt either if you have a bit of time just to make sure they're doing what they claim to be doing. http://codereview.appspot.com/6306064/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
