On Aug 23, 2006, at 6:07 PM, Scott Crick (Lists) wrote:
It works fine with Acrobat Distiller. I create PDFs with this tool all the time.
You need to use the Fiery PPD... make everything exactly as if you were sending to the Fiery and then use Adobe Acrobat Distiller. If you have to, grab the spool file from the Fiery RIP server. The reason why this is important is because it might be a "bug" with the Fiery PPD.
The reason this is driving me nuts is because no other applications seem to have this problem with the Fiery RIPs that I've ever encountered. It's JUST Print Window that causes this problem. It also doesn't happen to any other type of printer or RIP that I've ever tried, just Fiery RIPs. So yes, it might be RIP-specific, but it also points to something specific that Print Window is doing that is causing the problems with that specific RIP. If other apps can print to it successfully, so should Print Window.
If there is any error or warning, then the Adobe Distiller log window will display it. If your files do not have any errors or warnings, then it *is* the RIP implementation which is flawed.
Unfortunately, companies do not like to license Adobe Postscript anymore and feel that it is more cost effective to create their own postscript interpreter... and therefore it is their responsibility to correct issues that do not conform to Adobe's own RIPs. It really does not matter which program created the troublesome print file.
I'm not sure it's a REALbasic issue, per se. It could very well be my code.
Unless you were creating Postscript or PDF data directly, I doubt that it is your code.
I can still report it to EFI (maker of Fiery RIPs), and probably will, but I think that might be barking up the wrong tree as it does seem something specific to Print Window (which just happens to be REALbasic-based).
It is to your benefit to report this to EFI asap, so at least you can tell your customers that you have contacted this issue to EFI and you are waiting for feedback from them. EFI cannot fix it if they don't know about it, and who knows how long it will take to respond to this particular issue.
There is no reason why you cannot continue to look into this issue on your end -- if nothing else than to look for a work-around.
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
