I'm familiar with how to painstakingly troubleshoot the problem: a series of incremental exports while isolating the problem element. This might seem practical when the document in question is a page or two. But for long-format projects? There's just literally no reason I can imagine that InDesign can't report the actual error it encountered while exporting a PDF.
For my latest encounter with this error, I was thankfully only exporting a relatively small flyer. Took me about 10 minutes to isolate a couple of PNGs as the problem (why ID suddenly had a problem with a couple of re-used assets is another issue, altogether). My question is: Is there some reason InDesign couldn't have either...
1. told me there is a PNG on page 2 causing a problem;
2. told me the precise nature of the problem with those PNGs?
The pre-flight error reporting does this (although, pre-flight's green dot indicated there were no errors in this case); the "text overflow" reporting does this; so why shouldn't the export error reporting do the same? Again, the data is obviously available. I'd appreciate if InDesign would share it with the end-user. Again, yesterday's was an easy fix. Larger projects, I've blown 30 minutes of productivity chasing down a mysterious error.
I'm familiar with how to painstakingly troubleshoot the problem: a series of incremental exports while isolating the problem element. This might seem practical when the document in question is a page or two. But for long-format projects? There's just literally no reason I can imagine that InDesign can't report the actual error it encountered while exporting a PDF.
For my latest encounter with this error, I was thankfully only exporting a relatively small flyer. Took me about 10 minutes to isolate a couple of PNGs as the problem (why ID suddenly had a problem with a couple of re-used assets is another issue, altogether). My question is: Is there some reason InDesign couldn't have either...
1. told me there is a PNG on page 2 causing a problem;
2. told me the precise nature of the problem with those PNGs?
The pre-flight error reporting does this (although, pre-flight's green dot indicated there were no errors in this case); the "text overflow" reporting does this; so why shouldn't the export error reporting do the same? Again, the data is obviously available. I'd appreciate if InDesign would share it with the end-user. Again, yesterday's was an easy fix. Larger projects, I've blown 30 minutes of productivity chasing down a mysterious error.