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

[nine . fierce . ballads]

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.

(Also -- not a problem with this patch -- where's the credit for
translators?)

https://codereview.appspot.com/260200043/