Re: how to reuse common header attributes

[Keith OHara]

Xavier Noria <fxn <at> hashref.com> writes:

> 
> On Mon, Dec 10, 2012 at 12:13 AM, Keith OHara wrote:
> 
> > I think so, mostly. Maybe put an extra set of {} around \addlyrics,
> > just in case you forget how \addlyrics works (like I often do).

> and don't quite understand that remark. Guess it has to do with
> variable assignment?

Yes, I did not see at first that both melody and lyrics were stored under
the name 'melody' because I forget how \addlyrics makes an attachment onto 
the previous musical expression.  Extra braces don't make it any more clear,
so I withdraw that suggestion.

melody = \relative c' {c4 d e f
 } \addlyrics { do re mi fa }

>     http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Entering-
lyrics#Lyrics-explained

Be careful about which version of the documentation you read, that it 
corresponds to the version of the program you are actually using. 
(Your example looked like it might have used version 2.16)  

> >     subtitle = \markup { "Part for" \concat{"E"\flat} "saxaphone"}
> 
> That would be a nice touch. The flat looks weird over here though (see
> attachment), is there an alternate markup I could use?

Bummer.  You can remove the \concat {} to get a space between E and flat.
LilyPond reads unicode, in the utf-8 encoding, so you can use the flat 
character ♭, unicode 2ffD to write E♭ directly in your input file.  Your 
text editor might not have a glyph for the flat, but you will see the flat 
sign from the roman font in the PDF file.