Re: opus and piece fields in top level header.

[Richard Shann]

On Sat, 2015-10-10 at 14:40 -0500, David Wright wrote:
> Quoting Richard Shann (address@hidden):
> > On Fri, 2015-10-09 at 23:37 +0200, Simon Albrecht wrote:
> > > On 09.10.2015 22:25, Richard Shann wrote:
> > > > In the 2.18 it does not seem to mention that the opus and piece fields
> > > > are not output anywhere if they are set in a \header{} block *outside*
> > > > any \score{} block, but this seems to be the case.
> > > 
> > > I can’t access the 2.18 docs ATM, since lilypond.org is down. But in the 
> > > current development version, this is documented in NR 3.2.1, with an 
> > > example for the default placement. 3.2.2 has an explanation how to 
> > > redefine the \paper variable bookHeaderMarkup, and the default value can 
> > > be found in ‘ly/titling-init.ly’.
> > 
> > Thank you - that is the documentation I was looking at, and it not quite
> > as explicit as it could be: there is a series of notes including this
> > one
> > 
> > - Only piece and opus are printed in a \score when the paper variable
> > print-all-headers is set to ##f (the default). 
> > 
> > which could be supplemented by
> > 
> > - The piece and opus are ignored when in a \header block not inside a
> > \score block.
> 
> That's not my experience. The piece and opus are printed but they have
> constant values: their last external definition in the file. Placing
> them inside a \score block sets (and overrides) individual values.

hmm, I think I see what you mean. So perhaps this addition to sentence
would help:

- Only piece and opus are printed in a \score when the paper variable
print-all-headers is set to ##f (the default). This means that, if set
at the top level, they will be repeated for each \score block unless
overridden.

Richard