In previous versions of Acrobat I was able to Check a comment (typically once I had made an edit to my InDesign doc). By setting the filter to show unchecked comments only I was systematically able to go through a set of clients edits. In the new version of Acrobat you have removed the ability to just click to check a comment. I now have to open a drop down menu and select it. This is really annoying when you have a large document with over 100 comments (as I regularly do).

Please return the simple check box to the comments in Acrobat.

This request is being submitted at the suggestion of Adobe Support which was unable to provide effective support for Case Nº 0189220198. Of the 252 applications currently installed on our macOS Sierra system, only Acrobat Pro XI cannot be reinstalled or upgraded because the storage volumes are formatted as case-sensitive. The previously case-insensitive system volume on which Acrobat Pro XI version 11.0.20 had previously been installed was converted to a case-sensitive format. This was done by imaging the volume as a DMG file using Disk Utility, and then after reformatting as case-sensitive, the volume was restored using the ditto command in the Terminal. Acrobat Pro XI still runs exactly as it did when the system volume was case-insensitive. Notifications have now been displayed that Acrobat Pro XI should be updated to version 11.0.21 and then to version 11.0.22. Neither the stand-alone updaters nor the automatic updates will complete. Although the error dialogs are misleading, we have confirmed that these update failures occur because the installation scripts detect that the volume format is case-sensitive which causes script execution to terminate. The updaters do not include complete copies of the applications and resources to be updated, so manual update would be very difficult and error prone.

Adobe should do better. It is clear that Acrobat Pro XI is compatible with case-sensitive volumes, as is Adobe Acrobat Reader 2017 which installs and updates without problems. It is obvious that Apple is now focusing upon case-sensitive formats. All iOS devices are case-sensitive, and the new Apple File System was exclusively case-sensitive until late in the beta cycle. The new iOS 11 will include a standard file manager for the first time, so files will be moved between iOS and macOS systems far more often than with earlier system versions. That makes parity of case-sensitivity highly desirable to avoid artificial pathname conflicts. Currently, Adobe is the only known impediment to such parity. Adobe should comprehensively support case-sensitive macOS volume formats as soon as possible. Continued failure to do so will be viewed as inadequate support of the macOS platform.

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.

I have a Microsoft Word file that has a number of images. I need to make an accessible PDF. I have entered alternate text for each image in MS Word. When I convert the Word file to PDF, the alternate text I had entered in MS Word is carried over to the PDF, which is what I want. The problem is that it puts all images/figures at the beginning of the tag tree no matter where the image comes in the document. When I look at the Reading Order for each page, it puts all images as the last item to be read on the page, even if the image is at the beginning or middle of the page.

If I use the Autotag Document function to re-tag the file, it puts everything in the correct order but the alternate text entries for every image has been stripped out.