Re: PATCH: Change PDF 'author' field to use /Author (issue 260200043by address@hidden)

[Phil Holmes]

----- Original Message ----- 
From: <address@hidden>
To: <address@hidden>
Cc: <address@hidden>; <address@hidden>
Sent: Sunday, August 16, 2015 12:41 AM
Subject: Re: PATCH: Change PDF 'author' field to use /Author (issue 
260200043by address@hidden)


> https://codereview.appspot.com/260200043/diff/1/scm/framework-ps.scm
> File scm/framework-ps.scm (right):
>
> https://codereview.appspot.com/260200043/diff/1/scm/framework-ps.scm#newcode462
> scm/framework-ps.scm:462: (metadata-lookup-output 'pdfauthor 'composer
> "Author")
> If I understand the reason for this, it is only half done.  If it does
> not make sense to assume that 'pdfcomposer is the author of the
> document, then it does not make sense to assume that 'composer is
> either.  The question is, why assume that the composer is the author?
> Why not the arranger?  Why not the poet?
>
> Maybe there should be no fallback for pdfauthor, or maybe Lilypond
> should be given a new header field that means what the PDF Author field
> means.


I think the best bet would be to treat author in the same way as keywords 
and subject.  Neither of these is a true header field in Lilypond, in that 
they do not appear on the printed page.  However, both do appear in the PDF 
properties and both can be prefixed with 'pdf', like the 'true' header 
properties.  We would then simply have

(metadata-lookup-output 'pdfauthor 'author "Author")

as the relevant line.

--
Phil Holmes