[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Prevent "orphan" markup
From: |
Urs Liska |
Subject: |
Prevent "orphan" markup |
Date: |
Mon, 16 Jan 2017 09:59:38 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 |
Hi all,
I have a multi-movement work (or rather numerous ones) where the
movement titles are printed using an automatically generated top-level
markup. The overall structure looks like:
\book {
\markup { "overall title" }
\bookpart {
% (first work in group)
\markup { "work title" }
\markup { "Title of first movement" }
\score {
% first movement
}
\markup { "Title of second movement" }
\score {
% second movement
}
% etc
} % end bookpart
\bookpart {
% second work in group
% ...
}
}
Each "work" is wrapped in a bookpart and will consequently start on a
new page.
I didn't want to do the same with the movements because there will be
cases where a new movement should better continue on the same page.
The problem is that *usually* the title of the next movement fits on the
same page as the end of the previous one but no music, so I have the
title of the next movement sitting on the bottom of a page.
So: is there a way that a top-level markup block can determine if there
will be at least one system of music coming on the same page?
I would really like to have an automatic way to handle this problem as I
expect to have a three-digit number of movements and quite different
configurations (full score, choral/continuo, parts) and perhaps also
different output targets/formats. Forcing all movements to start on a
new page would be a pity but seems the only workaround if I can't get a
proper automatic solution to run.
Any suggestions?
Urs
--
address@hidden
https://openlilylib.org
http://lilypondblog.org
- Prevent "orphan" markup,
Urs Liska <=