Hi,

Pretty sure this is a bug, but thought I'd post to bug- first before
opening in Google.

Sometimes I build .ly files that are essentially text docs as a
sequence of \markup commands.

In versions up to the .11 dev series, what we might call "multipage
markup" files would of course break onto multiple pages if there were
enough \markup blocks to warrant so.

In the current releases a warning issues and all the text gets shoved
onto a single page, even if there's a considerable amount of text and
overprint results.

%%% BEGIN %%%

\version "2.11.17"

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

\markup { text. }

%%% END %%%

Sorry for the length of the example; needs length to show up.

Bug? Or new behavior? (If the latter, what's the right way to set a page break?)



--
Trevor Bača
[EMAIL PROTECTED]
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to