Skip to content

Brian Keller

My feedback

1 result found

  1. 39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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
    Brian Keller commented  · 

    Ravi - It has been over 3 months since you have responded to this case and clearly more companies have found problems. In addition, the newest version of the software version 19.0 does not address or correct the problems. I know that I have supplied files as requested and I have to imagine that others have as well. When are you going to provide feedback on this? Like I stated last month there have already been large financial impacts to these problems that have been introduced. It has been 5 months since the release of the problem version and yet there is no fix (or acknowledgement that a problem was introduced) from Adobe.

    An error occurred while saving the comment
    Brian Keller commented  · 

    So, interesting followup about this issue. We just installed a new version of Apogee Prepress software and upon talking to a resource with the company I was shown that they have a specific hotfix applied in their new version 13 software that addresses this problem that InDesign exporting has caused. I still have not been able to test it personally. I have to imagine that someone reached out to Adobe to make you aware of this issue in 18.4 and yet it still is not corrected. This and the increasing number of complaints on this topic shows that there is a problem that is not being addressed. I know that this has already caused problems here and a rather large financial hit with re-works. This has been going on for 3 months and minimal response.

    An error occurred while saving the comment
    Brian Keller commented  · 

    Ravi,

    I know that you responded to me after supplying you with some sample files. The comment you made was to look at our imposition software to see if it is not compatible with your updated libraries. I will look into this, but I still would like to know what Adobe changed in the export to PDF function that broke this. We have found that if we create a PDF file through Adobe Distiller and then bring that PDF file into the same imposition program that it works correctly. Why does your Adobe Distiller product work and yet the export to PDF in 18.4 & 18.5 does not work? Looking at the comments you are getting from many different users, it appears that this is some kind of Adobe issue. Please advise.

    Brian Keller supported this idea  · 
    An error occurred while saving the comment
    Brian Keller commented  · 

    We are also a commercial printer and have recently seen this same problem arise with a couple exported PDF files from InDesign verison 18.4 as well. We import these PDF files into our imposition program that creates a postscript file and that is when we see the pages go blank. We then create our own PDF proofs with guidelines for the margins from the imposition and the pages are blank in the PDF file we make through Distiller.(thankfully shows in the proofs)

    We have found a workaround that if we postscript the PDF file and re-make PDF files through Distiller before importing that it appears to correct the issue, but this is time consuming.

    I have just gotten word from a few of my employees that they are starting to see more issues with InDesign exported PDF files from version 18.4. I have asked our customer to supply the native InDesign files as well for troubleshooting to see if this is corrected in 18.5, but looking at the comments here it does not appear that 18.5 fixed the problem.

Feedback and Knowledge Base