Several major bugs have been documented by users in the Adobe Community Forums since Acrobat and PDF Maker were updated on September 14, 2021.

They are:

1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 This violates the PDF/UA-1 standard which requires that every graphic have alt-text that verbally describes the graphic.

THIS IS A HUGE BUG. You essentially have made Acrobat unusable for those who are required by their country's laws to make fully accessible PDFs.

2: Every cell border on every table cell is being tagged as:
<P>PathPathPathPath. This violates PDF/UA-1 because unnecessary visual formatting is not being tagged at Artifacts.
See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

3: The underline on Hyperlinks should be tagged as artifacts. Right not, it appears as one or more "PathPathPath" which is announced by different assistive technologies. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath. This too is a violation of PDF/UA-1. https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

NOTE: To be correctly tagged per PDF/UA-1, the borders/shading content should:
— Not appear anywhere in the Tag tree, either as <Figure> or as "Path" in a yellow content container box.
— Not appear in the Order panel.
— Should appear as Artifact in the Content panel.

6: Dragging and dropping elements in both the Tag and Order panels is now broken.

The text cursor doesn't show anymore, and the little black line doesn't show anymore and instead appears several inches away from where it really is. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 and also https://community.adobe.com/t5/acrobat-discussions/acrobat-pro-reading-order-box-and-tag-dragging-no-longer-visible/m-p/12395226#M329877

And finally...
7: Once this update is installed, users can't revert back to a previous version of PDF Maker because Adobe doesn't allow that in Acrobat like it does with other Creative Suite applications.

So once the update is completed, it makes PDF Maker completely unusable for tagged accessible PDFs.

This affects millions of your government customers world wide, as well as millions of government contractors and millions of academic customers...all of whom are required by their country's laws to make accessible PDFs.

2 sets of sample Word and Matching PDF files are submitted as demonstrations of the problems in the exported PDFs via PDF Maker.

My business requires signature of multiple documents in various places and I'm required to sign hundreds of these documents near deadlines that occur throughout the year. Having the ability to open multiple documents at once to then quickly click to certify AND sign ALL signature fields placed in ALL open documents with only a few clicks would eliminate a lot of time I currently spend having to click through each signature field of each document.

While a batch signature functionality exists, the true efficiency of batch signing does not exist in the current Adobe functionality. Having to manually click through each signature field and the various steps associated to certify/sign for EACH field placed within the documents results in no time saved from doing each document individually. The number of clicks is the same. It would be nice to go through the signature prompts once and the batch signature functionality sign ALL open documents in all signature fields within those documents.

An example of the desired functionality that truly captures 'batch signature' and creates meaningful efficiency in the signature process can be found at the below link.

Example of Bluebeam functionality:

https://support.bluebeam.com/online-help/revu20/Content/RevuHelp/Menus/Batch/Sign-Seal/Batch-Sign-and-Seal.htm

Request:
A Microsoft Word document can be either a .docx or .dotx, the difference is that when saving the .docx, the file is overwritten; when saving the .dotx, a new file is created. I propose a similar feature for PDFs.

Use Case:
I've created a fillable PDF and saved it as a PDF to a network share and SharePoint. People have the tendency to open it, fill it out (as they should) and then click save (or Ctrl-S, muscle memory). That commits those filled form fields to the file system such that the next person who opens the file now sees a filled-out form.

I would like to do something to the file so that "Save" doesn't work. For example, if the file extension were .pdft, and I opened it, it could behave the same as any other .pdf. However, when I chose to save the file, a compliant program would recognize that the preference is to create a new file, not overwrite the existing file.

Context:
I propose a file extension change instead of metadata in the file because it is much easier, and doesn't require the PDF standards consortium to get involved. A non-compliant program would just overwrite the file as usual. This means that any PDF program could open a .pdft file simply by, in Windows, right-click, open with, and choosing whatever program; they would see no functional difference. However, a compliant program would make the default save operation require a new file name.

Such a convention would also be very easy for PDF tools made by other companies to implement more quickly promoting this convention.

This has been asked of the Adobe Community before: https://community.adobe.com/t5/acrobat-discussions/can-i-create-a-pdf-quot-template-quot-akin-to-word-s-template-dotx-function/m-p/10485536

Outlook stores its complete data in PST format. If Outlook gets hit by any error or becomes accessible, users can efficiently recover their data from PST files. But the issue arises when there is an unavailability of the Outlook email application.

Since the PST file is just compatible with Outlook, Users visit it following it to impossible to open the PST file data in want of Outlook. But this nuisance can be cracked smoothly if users ship PST to PDF. If you are somebody who is scheduling to achieve this data export, this blog choice offers you answers to export PST to PDF.

Visit at : https://www.osttopstapp.com/pst-to-pdf.html
.

Hi all,

can any of you tell me how to set Photoshop as the default for opening images from Acrobat Pro DC (macOS Monterey)?

Whenever I click on an image under "Edit PDF" with the "Edit" tool, the preview is displayed in the "Edit with" submenu. When I say "open with" I can select Photoshop. However, I would like to use Photoshop as the default here so that I don't always have to select the programme under "Open with".

I had actually remembered that I could set this in the settings under the item "Touch up". Unfortunately, this menu item no longer exists in the settings. What I do find is "Content editing". There I selected Photoshop as the default editor for the "Edit object" tool. Unfortunately, this did not have the effect I had hoped for.
((Transleted by deepL))

Original

Hallo zusammen,

kann mir einer vom euch sagen, wie ich Photoshop als Standard für das Öffnen von Bildern aus Acrobat Pro DC (macOS Monterey) festlegen kann?

Mir wird immer, wenn ich unter "PDF bearbeiten" mit dem Werkzeug "Bearbeiten" auf ein Bild klicke im Untermenü "Bearbeiten mit" die Vorschau angezeigt. Wenn ich sage, "öffnen mit" kann ich Photoshop auswählen. Ich würde hier aber gerne Photoshop als Standard nutzen, sodass ich unter "Öffnen mit" nicht immer das Programm auswöhlen muss.

Ich hatte eigentlich in Erinnerung, dass ich dies unter den Einstellungen beim Punkt "Touch up" einstellen konnte. Leider gibt es diesen Menüpunkt in den Einstellungen nicht mehr. Was ich finde ist "Inhaltsbearbeitung". Dort habe ich Photoshop als Standard-Editor für das Werkzeug "Objekt bearbeiten" ausgewählt. Leider hatte dies nicht die erhoffte Wirkung.

There is a problem with extracting single pages from particular PDF documments. Attaching the test.pdf file.

Extracting a single page from it (view->tools->Organize Pages->Open and you can do a drag & drop page to windows explorer) we are getting a pdf file with same file size as original but with only one page.
It seems that its not removing all jpegs from the file.
Attaching also sample file with extracted one page.

Files are generated by FPDF library and got a replay on their forum: "That's probably because FPDF uses the same Resources dictionary (containing all images) for all pages"

Doing a File->Save AS fixes the file size but it must be taken as additional action on extracting a page and its a bit problematic for non-technical people.