> I personally don't bother so much about the names of the different
> fields. If you want some text to appear at the place where the default
> titling typesets the opus, for example, just use that field.
I think the main reason I'm reluctant to go that route is the issue of
documentation, particu
Quoting Graham Percival <[EMAIL PROTECTED]>:
I'd like this header printed by default, but I realize there's currently
no good spot for it. If it can't be printed, I think it needs to be
pulled from the manual.
Hmm... it shouldn't be too hard to add. Take a look at
ly/titling-init.ly (especi
On 22-Mar-06, at 10:43 AM, Geoff Horton wrote:
Hmm... it shouldn't be too hard to add. Take a look at
ly/titling-init.ly (especially since you were wanting to learn more
about the next level of lilypond stuff. :)
I found it already, based on your earlier suggestion :). It would be
very eas
On 22-Mar-06, at 7:28 AM, Geoff Horton wrote:
I noticed a thread about this from January, but there doesn't seem to
have been any discussion since then.
Oops, it slipped through the cracks.
The "All headers" template in 3.7.1 in the manual refers to a
\texttranslator field,
Hmm. It's in
I noticed a thread about this from January, but there doesn't seem to
have been any discussion since then.
The "All headers" template in 3.7.1 in the manual refers to a
\texttranslator field, but a close look at the sample output below it
reveals that this field does not appear in the output. I
