On Mar 19, 2011, at 11:01 AM, Han-Wen Nienhuys wrote: > On Wed, Mar 16, 2011 at 12:44 PM, [email protected] > <[email protected]> wrote: >> The problem is that Lilypond processes graphical objects before it processes >> pagination, making it impossible to know exactly how much space a footnote >> will take up when the graphical object is processed. >> >> One solution to this problem would be to reprocess all top-level markups >> with correct footnotes after having done the pagination, then redo the >> pagination and see if all the footnotes stay the same. If so, keep the >> current configuration. Otherwise, rinse & repeat. This actually seems >> kinda sorta doable, although I'd have to do some homework on how these >> markups are stored internally and figure out to what extent these internal >> representations survive downstream into the pagination phase. >> > > Overall comment: I think we should avoid 2 pass solutions if we can > help it. Have you thought of setting a fixed width/height for the > number and later filling it in?
That's what I do on line 1862 of define-markup-commands.com. This uses a seed of 0 (line 1861) on the first pass, and then uses the actual value on the second pass (line 1860). The seed of 0 works well for one digit numbers, but breaks down on larger #s. Cheers, Mike _______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
