Re: Problem controlling page numbers in bookparts

[Valentin Petzel]

Hello Vincent,

The first problem seems to be something internal to Lilypond. Basically the 
header markup seems to get called for the 0th page even though we don’t need 
it. But as only positive integers can be formatted as roman this causes a 
problem if the first bookpart is set to roman.

But we can easily fix this as shown in lines 37 and 39 in the fixed first 
example.

For your second problem: The code you are using is messing up the order of 
things. Basically it first performs the first-page check and then does the 
resetting stuff. This means that that if print-first-page-number is ##f the 
reset call is not evaluated on the first page. Apparently this fucks up this 
system. So the solution is to move the first page check after the reset part, 
as shown in lines 63-65 and 79-81 in the fixed second example.

Your third problem is basically a result from the same thing. Due to the order 
the first page check is done before resetting. This means that at the time the 
first page is checked it does not have page number 1. Changing the order again 
fixes this.

Cheers,
Valentin

example2.ly
Description: Text Data

example1.ly
Description: Text Data

signature.asc
Description: This is a digitally signed message part.