lilypond-devel
[Top][All Lists]
Advanced

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

Re: 2.11 lilypond-book and headers


From: Laura Conrad
Subject: Re: 2.11 lilypond-book and headers
Date: Thu, 11 Oct 2007 00:48:26 -0400
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.91 (gnu/linux)

>>>>> "Graham" == Graham Percival <address@hidden> writes:

    Graham> Laura Conrad wrote:
    >> In 2.11, if a \lilypondfile{filename} isn't the first one on the page,
    >> no headers are printed. 
    >> 
    >> Is there a way to turn off this behavior, or to regulate it in some
    >> way?  It may be  a feature for somebody, but it's a bug for this
    >> particular document.

    Graham> Is

    Graham> \paper{
    Graham>   printallheaders=##t
    Graham> }

    Graham> What you're looking for?  

It does fix the problem.  It would be better if it could be specified
as an option to \lilypondfile or even as a command line option to
lilypond-book, though.  

    Graham> It's the second item from the bottom of the "creating
    Graham> titles" page.

That says:

     If you define the \header inside the \score block, then normally
     only the piece and opus headers will be printed.  
...  
     You may change this behavior (and print all the headers when
     defining \header inside \score) by using

             \paper{
                  printallheaders=##t
                  }


I would never have guessed that having a piece start in the middle of
a latex page was equivalent to having the headers of the piece inside
a score.  So maybe a discussion of what lilypond-book is doing to the
structure of a lilypond file that would cause the output to be
different when I say "\lilypondfile{file.ly}" inside a latex file than
if I just say "lilypond file.ly" would be a good thing.

I would attempt to write this explanation if I understood it, but I
don't.  In versions previous to 2.11, I think I was always successful
in arguing that it was a bug when they were different.  If it's not a
bug, I think it should be documented as a feature.  

I have only spent an hour or so trying to figure out why it would be a
useful feature, and I have been unsuccessful, but I'm willing to
listen if a developer who implemented it on purpose has a rationale
for having done so.  If it happened by accident, and nobody has ever
had a reason to use it as a feature, I'll be happy to submit a bug
report.

-- 
Laura (mailto:address@hidden , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139




reply via email to

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