"Christopher R. Maden" writes:
> On 01/11/2013 03:23 AM, David Kastrup wrote:
>> File names are hierarchical. If you don't specify a filename inside
>> of a bookpart, do you think that the bookpart should not be written
>> out?
>
> I’m afraid I don’t follow... what do filenames have to do with t
Le 12 janv. 2013 à 11:10, Christopher R. Maden a écrit :
> I expect \bookpart{} to start a new page; and
> if the bookpart has a title or any other header info, I expect that to
> be printed at the top of that new page.
Christopher,
Indeed, \bookpart starts a new page.
In your example, the \boo
On 01/11/2013 03:23 AM, David Kastrup wrote:
> File names are hierarchical. If you don't specify a filename inside
> of a bookpart, do you think that the bookpart should not be written
> out?
I’m afraid I don’t follow... what do filenames have to do with this?
If you just meant title... I expect
"Christopher R. Maden" writes:
> It seems to me that there should be a little more granular control
> over what header elements are inherited at each level of the
> hierarchy. One can determine what constitutes the title line of a
> score with custom headers... but there should be a more
> strai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/11/2013 03:09 AM, Federico Bruni wrote:
> The following input works:
>
> \version "2.14.2"
>
> \paper { %print-all-headers = ##t }
>
> \book { \header { title = "My Songbook" } \markuplines
> \table-of-contents \bookpart { \tocItem \markup { M
Il 11/01/2013 06:06, Christopher R. Maden ha scritto:
I have a songbook I created in LilyPond 2.12.3. I recently upgraded
to 2.14.2.[*]
Suddenly, every song has the book title*and* the song title at the
start. Using print-all-headers only makes things worse, as I get the
book title but*not*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/11/2013 12:06 AM, Christopher R. Maden wrote:
> Suddenly, every song has the book title *and* the song title at
> the start. Using print-all-headers only makes things worse, as I
> get the book title but *not* the song title.
A temporary workar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/11/2013 12:06 AM, Christopher R. Maden wrote:
> I have a songbook I created in LilyPond 2.12.3. I recently
> upgraded to 2.14.2.[*]
(And yes, I did run convert-ly... no bearing on this particular issue,
AFAICT, but I suspect someone will ask if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a songbook I created in LilyPond 2.12.3. I recently upgraded
to 2.14.2.[*]
Suddenly, every song has the book title *and* the song title at the
start. Using print-all-headers only makes things worse, as I get the
book title but *not* the song
