Originally created by: *anonymous
Originally created by: pkx1...@gmail.com
Currently, the PDF author field is filled with the composer. This is nice fall back but in most cases the author of the document and the composer will be different. While I can write pdfcomposer = "Author Name" it appears as intended as /Author(Author Name) but it also appears as /Composer(Author Name) which is wrong. Wouldn't it make sense to offer both fields: Author and Composer separately? A fallback if no author is given makes sense but it would be good to be able to specify an author differing from the composer.
Originally posted by: pkx1...@gmail.com
This passes make, make check and a full make doc. However reg tests show programming errors
for example
--snip--
Writing ./voice-4-midi-systems.tex...
Writing ./voice-4-midi-systems.count...
Writing timing to voice-4-midi.profile...
+programming error: Parsed object should be dead: #<Context_def CueVoice /home/james/lilypond-git/build/out/share/lilypond/current/ly/performer-init.ly:110:1>
+continuing, cross fingers
+programming error: Parsed object should be dead: #<Prob: Music C++: Music((origin . #<location out-test/voice-4-midi.ly:72:3>))((display-methods #<procedure #f (check)>) (name . BarCheck) (types bar-check) (iterator-ctor . #<primitive-procedure ly:bar-check-iterator::constructor>)) >
+
+continuing, cross fingers
input/regression/midi/voice-4-midi.log
--snip--
MOst (if not all of the Midi reg tests show this same error)
Labels: -Patch-new Patch-needs_work
I've created a new patch for this at:
https://codereview.appspot.com/264970043/
This uses author and pdfauthor as the normal fields to set Author in the PDF properties.
Diff:
I've created a new patch for this at:
https://codereview.appspot.com/264970043/
This uses author and pdfauthor as the normal fields to set Author in the PDF properties.
Passes make, make check and a full make doc.
Patch on countdown for September 5th
Patch counted down - please push
Pushed to staging as 9cd96a9f2f66f8182099079685456a6e23c26862