[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: printpagenumber in 2.5.31

From: Fairchild
Subject: RE: printpagenumber in 2.5.31
Date: Sun, 26 Jun 2005 14:43:12 -0500

printpagenumber =  ##f works just fine in 2.4.6.  I hope it survives.

                             - Bruce

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Sent: Sunday, June 26, 2005 2:37 PM
To: Bertalan Fodor; lilypond-user
Cc: address@hidden
Subject: Re: printpagenumber in 2.5.31

I didn't know that such property did even exist - it seems that it's not  
in the documentation (?), just in some changelog.

printpagenumber doesn't work indeed. I've been hacking with recently, and I've modified it again so it now takes into  
account the values of printfirstpagenumber *and* printpagenumber to print  
the page numbers accordingly.

I can post the new patch if the lily meisters agree again.

If yes, before that I would like to know opinions about how  
printfirstpagenumber should behave:

as it is now, the value of printfirstpagenumber affects to page number  
"1". If the firstpagenumber property has a different value, the page with  
that number will be printed no matter what value printfirstpagenumber has.  
Only page "1" will be printed or not. In my opinion,  
"printfirstpagenumber" should affect to "page firstpagenumber", not "page  

In fact, this issue affects to the Copyright and Instrument fields. If  
firstpagenumber is not 1, they don't print correctly. I can easily fix all  

Somebody disagrees? Opinions welcome, thx.


On Sun, 26 Jun 2005 10:13:10 +0200, Bertalan Fodor <address@hidden>  

> Is it intentional that setting printpagenumber = ##f doesn't work
> anymore?
> Bert

lilypond-user mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]