On 8/23/06 7:34 PM, "Phil M" <[EMAIL PROTECTED]> wrote: > My recommendation for you is to capture the print spool file and try > to process it with another RIP... I have found that the best tool to > use is Adobe Acrobat Distiller using all of the same settings as if > you were sending it to the Fiery RIP. Basically, if you can > reproduce the error (or something similar) in Acrobat, then it is a > problem with the file/REALbasic. Since Distiller is a end-user > application, it provides far better error reporting than a hardware > RIP, and there is a good chance that you could isolate the error. If > you cannot reproduce the error, then it is an issue with the Fiery > RIP and should be reported to Fiery, including the print-spool file > in the bug report, and state which version of Adobe Acrobat the file > correctly distills with.
It works fine with Acrobat Distiller. I create PDFs with this tool all the time. 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. > It might turn out that this is a REALbasic-specific issue, but my > guess is that this might an OS specific issue. In fact, it might be > reproducible with a limited range of operating system versions (such > as OS X 10.3.9 - 10.4.7, but not lower than 10.3.8). So make sure > you report the OS version the spool-file was printed from. I'm not sure it's a REALbasic issue, per se. It could very well be my 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). I should probably say that the print jobs Print Window sends are all Vector-based, using StringShapes, Group2Ds, etc. Maybe something specific to those classes? Sincerely, Scott -- SearchWare Solutions Simply Great Software http://www.searchwaresolutions.com Webthoughts: http://www.searchwaresolutions.com/other/weblog/ _______________________________________________ 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>
