I have CC full suite and from the day I had to install Adobe Acrobat Pro DC I have been unable to print locally from any open PDF. I have tried multiple fixes. I have uninstalled and reinstalled several times. I've updated the printer drivers and had my IT support look at it. And now that this program is embedded in everything, I can't event go back to Acrobat XI. If I'm lucky I can export the PDF as an image or word document and print from there, but if I'm looking at document that's large that is just simply not a valid workaround. In this day and age, this shouldn't even be an issue

When printing an Internet-Document from Firefox 57 the print generates multiple errors if the title of the document to print contains quotation marks. The error box mentions: "C:\Program Files (x86)\Adobe\Acrobat 2015\Acrobat\Intellektuelle" Diese Datei kann nicht geöffnet werden." (The file could not be opened. Verify the correct location." - should be the approximate translation.)

Where the "Intellektuelle" is the first word of the documet title inside the quotation marks. The same error appears for every word in the title and one additional time. The PDF finally generated contains only part of the document to print. You could try it with the following site https://www.heise.de/tp/features/Intellektuelle-Monokultur-im-Westen-3892083.html

The Acrobat version is 2015.006.30392.

Currently Adobe Acrobat DC does not recognise if the default printer setting on my mac has been set to duplex. There is a work around. By pressing the printer button and selecting 'duplex' from the print dialogue box that is revealed, pdfs can be printed double sided (DC warns against doing this by the way). The trouble is that it is easy to forget to follow this process, particularly when I am in a hurry, with the result that pdfs, in my case often 20 or 30 pages documents, are printed single sided. This wastes paper, is environmentally unfriendly and negates the whole reason for setting the default to double sided. I have many applications on my mac and Adobe applications (it's not just DC) are the only ones that don't recognise the duplex default setting. Please feel free to contact me if you require further information.

2) Steps to reproduce the problem:

Being logged into the business account of OfficeDepot.com for the company I work for, and needing to create a PDF of a shopping list of one of my coworkers I will start by:

a) Either right clicking on the web page or clicking on the 3 vertical dots in the top right corner of the Chrome web browser.
b) I then locate and click on the "print" option.
c) When the print window comes up, I change it from a physical printer to Adobe PDF to "print" (create) a PDF of the web page I was on and needed.
d) I click "print" at this point.
e) Then Adobe Acrobat Pro DC opens with my newly "printed" PDF.

3) Environment:

a) Windows 7 Enterprise
b) Google Chrome
c) Adobe Acrobat Pro DC

4) Expected Results:

A FULL copy of the web page in PDF format with ALL of the information showing on the PDF that was meant to be there.

5) Observed Results:

A PDF with the bottom 1/3 of the page blank.

** This problem doesn't seem to happen all the time, nor with all web pages, BUT it happens enough that it henders my job in a very BIG way!

In Distiller Pro XI 11.0.20 (28/03/2017), and in many earlier versions, pdfmark is inconsistent about whether strings should be plain ASCII or in the pdf encoding. In particular, “… /Title String /OUT pdfmark” can be in the PDF encoding, but “/Label String /PAGELABEL pdfmark” must be plain ASCII.

Example PostScript:

%!PS

/Times-Bold 48 selectfont
/StringASCII (ASCII-encoded string) def
/StringPDF (PDF-\351\361\347\370\360\353\360 \235tr\232\361g) def % Silly accents

36 36 moveto (ASCII string) show
mark /Dest /Page1ASCII /DEST pdfmark
mark /Action /GoTo /Dest /Page1ASCII /Title StringASCII /Count 0 /OUT pdfmark
mark /Label StringASCII /PAGELABEL pdfmark
showpage

36 36 moveto (PDF-encoded string) show
mark /Dest /Page2PDF /DEST pdfmark
mark /Action /GoTo /Dest /Page2PDF /Title StringPDF /Count 0 /OUT pdfmark
mark /Label StringPDF /PAGELABEL pdfmark
showpage

which is also at
http://www.jdawiseman.com/papers/bugs/20170513_pdmark_encoding_bug.ps

distills to
http://www.jdawiseman.com/papers/bugs/20170513_pdmark_encoding_bug.pdf

The outline items are correct — screen grab at
http://www.jdawiseman.com/papers/bugs/20170513_OUTs.png

But the second pagelabel has gone all wrong: it cannot cope with the pdf encoding.
http://www.jdawiseman.com/papers/bugs/20170513_PAGELABELs.png

This is a bug, also reported at
https://groups.google.com/forum/#!topic/comp.lang.postscript/xqXz9g44ATs