GregJ
My feedback
1 result found
-
40 votes
The fix of the issue is now available in the latest InDesign 2024(v19.5.0.084). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign Team
An error occurred while saving the comment An error occurred while saving the comment GregJ commentedWaiting to update until we start getting more new files from customers but so far it seems okay.
An error occurred while saving the comment GregJ commentedAnd still nothing..
An error occurred while saving the comment GregJ commentedSame status here as well. I did run a file through qpdf and saw file offset warnings. The resulting "qdf" file did work though. This was a simple 4 page file going to plate. Will try on other files in the future.
May or may not help but I am attaching a screenshot from the command line. This was from a 19.2 file that wound up with missing text on the first page.
An error occurred while saving the comment GregJ commentedWe're still having issues with 19.2 as well. Rewriting a pdf from 18.3 works about 90% of the time. We do sometimes get an error in Apogee 10. Invalid stream length, IOError. Apogee can also have problems creating thumbnails if none are embedded when the error occurs. Usually a random page or two.
I'm sure at least some here know Agfa / Eco3 sent info on their findings about this soon after it was discovered and they made their patch. Unfortunately not everyone is running patchable versions. Can understand it might take time but this is getting beyond tedious and for the first time I actually cringe when I see pdf files from InDesign.
We're starting to get mostly 19.4 files now and things seem to be resolved however we have received a 19.4 file or 2 that have caused errors but that was most likely due to having some of the corrupt pdf elements placed into those files. Imagine that will take a bit longer till more and more update.
Still doesn't excuse how long it took to fix this.