Abro este hilo, por que no se si esta reportado o no, pero tengo problemas para abrir archivos grandes en mi nueva MacBook Pro Max. Si el PDF pesa mas de 2gb directamente no me abre el documento (lo he probado a abrir en otras maquinas mas antiguas y sin problema), esto me esta pasando en una maquina que compre recientemente MacBook Pro Max, 32gb de RAM y 1tb de HD. La maquina no es, por que ese mismo PDF lo abro y manipulo sin problemas en el programa Vista Previa, pero en Acrobat ni lo abre.
La cuestion es... ¿alguien sabe de esto?, ¿le pasa a algien mas?, ¿existe solucion?

Muchas gracias.

Acrobat Pro DC Bug (version 21.007 using Windows 10)

This is a new bug, so suggests it relates to a recent update.

When Splitting a PDF file via Top Level Bookmark.
You receive the following error message (see screenshot).

"The file may be read-only, or another user may have it open. Please save the document with a different file name or in a different folder".

Trying either of the above suggestions will not work and you continue to receive the same error message when attempting to split the file.

The only way to get around this, is to manually select 'A Folder on My Computer' under the splitter Output Options menu. You can actually select the same folder which the original file is in and it works fine, which is odd as this is the same end result as the default selection (The Same Folder Selected at Start) which prompts the error message.

The error message appears with all my PDF files and colleagues, both desktop and server based. As mentioned it use to work fine so possible recent Acrobat Pro update bug.

please add a functionality that allows you to open a cross-reference to a point within the same document in a new tab/window. currently when you click a cross-reference the reader jumps to the linked section in the document and the current position where the link was clicked from gets lost. this happens a lot of times when you read a scientific script for example and there are references to figures/tables on a different page. every time you click a link and you want to go back afterwards it takes a lot of time to scroll back to the origin page. i posted this issue to the community and got told to submit a request here by an adobe support team member.

If I create a brand new destination within a PDF using Acrobat Pro DC, then host that PDF on a web server, and then open up and navigate to that Destination via a web browser via the #[Destination] or #nameddest=[Destination] anchor tag (it makes no difference which browser), it will properly take me to that destination. However, if I then change that Destination in Acrobat Pro DC by moving to a different location in the document, and using the "Set Destination" option in the context menu of the Destination, and then rehost the PDF on a web server and attempt to navigate to the Destination again, it will not properly navigate to the new Destination location. I have to delete the Destination and recreate it for the Destination to be properly navigated to within the browser.

Interestingly, within Acrobat Pro DC, it will navigate to the new Destination location if I double-click the Destination. But the browser will not. The browser will open up the first page in the PDF. It does not seem to recognize when a Destination's location has changed. The Destination has to be deleted and recreated.

It seems as if the behavior behind the "Set Destination" option in the Destination's context menu does not reflect all of the same behavior behind creating a brand new destination; like perhaps there's a property that should be getting set that isn't, which might be specific to browser plug-in behavior but not the native behavior within Adobe Pro DC.

I am using Acrobat DC Pro Version 2021.007.20099.

My system details are CPU i9-10920x, GPU NVidia 3090 Studio driver 472.12, 256GB RAM, sveral m2 and SSD drives, Windows 10 Pro 21H1. I use two Eizo CS2721 monitors in 10 bit mode and both are calibrated and profiled using Eizo's colour navigator 7 software to produce v2 profiles.

The issue :

I create a document in InDesign including 3 placed images each based on the same image but converted and tagged with a different profile in Photoshop (ARGB,sRGB,ProPhoto) . All three, as expected, look identical on the InDesign page as they did in Photoshop and print direct from InDesign identically. So far so good - colour management is working correctly in In Design and Photoshop.

However, I then export from In Design to a PDF using "High Quality Print modified" to "Acrobat 8/9 PDF1.7" and with Colour Conversion set to "No Colour Conversion" and "Include All RGB and Tagged Source CMYK profiles".

If I view that exported PDF in Acrobat Pro DC, the three images still look the same as each other in the PDF, so the tagged image profiles are being used, but all three look oversaturated compared to the In Design and Photoshop display. By oversaturated it is like viewing untagged sRGB on a wide gamut monitor. Opening the same PDF in Photoshop or InDesign displays correctly.

As a test I set both monitors to use an incorrect (linear gamma) profile. Photoshop and InDesign now display incorrecty (as would be expected with such a widely incorrect monitor profile). Acrobat DC Pro displays the same oversaturated images as it did before - absolutely zero change despite the deliberately broken monitor profile. My conclusion - Acrobat DC Pro is ignoring the monitor profile and just assuming that the monitor is narrow gamut (close to sRGB).

I have uninstalled and re-installed Acrobat DC Pro - and it has not changed these results.

Dave