Seems on one mentioned SamatraPDF viewer. It has a view option "Fit Content", which actually "removes" margins in display area, and it's going across pages, so it works for me.
From the Adobe validator (Preflight in Acrobat X Pro):
Click for full size
I don't see how much more official you can get. That happened on a "Report PDF syntax issues" in Preflight. The same thing when I tried to test for PDF/A validity. The report process aborts rather than continuing, as it would do for minor errors. There is no response on the numerous Adobe forum posts about this error.
Opening the file in Notepad++ and ripping out every stream (stream
to endstream
inclusive) leads to a blank file that does not report an error on opening and only a few minor syntax errors in Preflight (related to the missing streams). Obviously there's something invalid in/about one of those streams, perhaps an invalid control character or something. I don't know much about the PDF format.
Also, PDF creation using the built-in tool works perfectly on your presentation in PowerPoint 2010. It appears only 2007 SP3 is affected - as you found yourself, no previous version was and no later version is. Depending on Microsoft's policy, this may or may not warrant a bugfix. It could be that the encoding used in 2007 SP3's version for images is not fully supported by Adobe.
Was the file you provided exported with the "ISO 19005-1 compliant (PDF/A)" option checked? If not, could you provide one that is?
Unless the file was exported as a standards compliant format (that option is unchecked by default!), it is not necessarily a 'bug', unless they explicitly say Adobe Acrobat/Reader should be able to open their PDFs - especially when some programs can. You may be fighting an uphill battle for a refund.
Best Answer
If you use Ghostscript on Windows, you'll have two executables:
gswin32c.exe
gswin32.exe
The first one is to be run from inside a 'DOS box' (i.e.
cmd.exe
window) -- either interactively or not. It prints all stderr/stdout messages into the cmd.exe window and also expects any input commands to be typed in there.The second one opens a separate Window for "interactivity': prints stderr/stdout to separate window, and expects commands there.
To avoid the 'prompt to type in', you have to use the right commandline parameters when you call either one of the commands. For example:
-dNOPAUSE
processes all pages of the input file (instead of pausing after each one).-dBATCH
avoids the return to thegs>
prompt after the last page.A complete command for Ghostscript to test your PDF would be (inside a DOS box) to run
(the
-o
parameter implicitly uses-dBATCH -dNOPAUSE
.)-sDEVICE=nullpage
doesn't do any conversion and doesn't write an output file. But it makes Ghostscript to run all the rendering commands of the input PDF. Should the input be invalid, Ghostscript will tell you with its stdout/stderr messages.