Producer set to Author instead of producing software in document properties about asciidoctor-pdf HOT 3 CLOSED

Here's what I'm thinking. /Producer can be overridden using the producer attribute, but will default to the Asciidoctor PDF credit line. /Creator can be overridden using the publisher attribute, but will default to the author. (Here I'm remapping the publisher attribute to /Creator instead of /Producer per the description in the PDF specification).

(We always have to populate both fields or Prawn will fill them in with the text "Prawn").

from asciidoctor-pdf.

Here are the definitions of these fields according to the PDF specification:

• /Creator (Optional) If the document was converted to PDF from another format, the name of the conforming product that created the original document from which it was converted.
• /Producer (Optional) If the document was converted to PDF from another format, the name of the conforming product that converted it to PDF.

It would seem as though the Creator is for whatever product created the AsciiDoc (if relevant) and the Producer is for whatever product generated/produced the PDF (in this case Asciidoctor PDF + Prawn).

I would agree that Producer should be the Asciidoctor PDF credit.

Note that the Producer field can be overridden using the publisher attribute, which was requested/required by one of the users of Asciidoctor PDF long ago. (I think I'll add producer as a fallback just for completeness).

For Creator, I'm not sure. I think perhaps we should default that field to the author, but still allow it to be overridden using the creator attribute.

from asciidoctor-pdf.

/Creator can be overridden using the publisher attribute

I sure wish there was a /Publisher field, but there just isn't (and most PDF readers don't show custom fields). So publisher → /Creator just has to mean what the author wants it to mean. What's important is that now you'll have control over both fields, which is the key focus here in my mind.

from asciidoctor-pdf.