Re: doc enhancement for \headers

[Mark Mathias]

Eluze and Graham,

Since Eluze is a bug squad member and will be on call next Tuesday, perhaps
I should have let this go for him to handle, but I've already gone ahead
and entered this into the issues-tracker as:
http://code.google.com/p/lilypond/issues/detail?id=2640&thanks=2640&ts=1341685687
 .

Hope that's what you wanted!
Mark

On Thu, Jul 5, 2012 at 11:05 AM, -Eluze <address@hidden> wrote:

>
> is it asking too much to add a full list or table of all the \header
> variables supported by default!? this would save users a lot of time
> searching for an example/snippet where all of them are shown (actually this
> is the 3rd example in
>
> http://www.lilypond.org/doc/v2.15/Documentation/notation/creating-titles-headers-and-footers#title-blocks-explained
> 3.2.1 Creating titles headers and footers . it is not mentioned that all
> variables are listed.
>
> \header is found 75 times in the NR.
>
> imo this would make the NR more a reference than a collection of loosely
> connected examples (the examples are still welcome!)
>
> thanks
> Eluze
>
>
> and here is how this could look like:
>
> +++ (right after Title blocks explained or after the Note)
>
> there are 13 variables that can be defined in the \header block and which
> will be used by the default header and footnote engraver:
>
> dedication
> title
> subtitle
> subsubtitle
> instrument*
> poet
> composer
> meter
> arranger
> piece**
> opus**
>
> tagline
> copyright
>
> *  the instrument will be repeated on every page.
> ** these are printed in a \score when the paper variable print-all-headers
> is set to ##f (default)
>
> +++
>
> this list could be enhanced with the position of each item.
> --
> View this message in context:
> http://old.nabble.com/doc-enhancement-for-%5Cheaders-tp34118295p34118295.html
> Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>