[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: first-page-number silently ignored sometimes
|
From: |
Jean Abou Samra |
|
Subject: |
Re: first-page-number silently ignored sometimes |
|
Date: |
Thu, 8 Sep 2022 09:22:47 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 |
Le 08/09/2022 à 03:35, Nikolai Hedler a écrit :
Putting the function inside a bookpart's paper block causes it to have
no effect.
Well, that's expected. It's similar to \override Clef.color = ...
instead of \override Staff.Clef.color = ... Page numbering is
handled on the book level, so you have to put first-page-number
there.
Starting with LilyPond 2.23.12, there is actually a
bookpart-level-page-numbering paper variable that allows to
do the numbering per-bookpart.
LilyPond tries not to get in the way of the user if they want
to customize things. If there had been a warning, this Scheme-based
implementation of bookpart-level-page-numbering before it was
added to LilyPond would not have worked with first-page-number:
https://lists.gnu.org/archive/html/lilypond-user-fr/2022-07/msg00043.html