I resolved a postscript issue by applying two patches from the xerox.com site to my brand new xerox docucolor 242 with bustled EFI feiry X3eTY RIP (1 and 2)
Now I have a new problem specific to CorelDraw (both X3 and X4) printing to this RIP/printer.
I resolved a postscript issue by applying two patches from the xerox.com site to my brand new xerox docucolor 242 with bustled EFI feiry X3eTY RIP (1 and 2) Now I have a new problem specific to CorelDraw (both X3 and X4) printing to this RIP/printer. If I print an 11 x 17 landscape and select the print/paper size as 11 x 17 landscape on the latest xerox/fiery postscript printer driver, the print now comes out portrait on the 11x17 sheet rotated 90 degrees and cut off. If I publish to PDF from coreldraw, I can print the same print from acrobat and landscape is landscape with the same printer/rip settings - no rotation occurs. Any ideas what is different in the way coreldraw is sending the print ot the rip from the way acrobat is sending the print? I found that if I check the box in coreldraw for use PPD and select the pagemaker ppd file provided by xerox, I can print from coreldraw without the involuntary landscape -> portrait rotation occuring, so I can print a landscape 11x17 landscape on an 11x17 sheet without issue. However, then I lose the much nicer Fiery print driver GUI with it's quick presets and easier tab organization, etc. and have to select all the options from the one-page alphabetical advanced tab of dropdowns which takes a lot more time. At least it works though, and with an hour or so I should be able to create seperate ppd files for each of my common print job options, but this isn't as smooth as being able to print without the ppd with the print driver's native GUI. Any ideas on whay the PPD works printing form coreldraw but the rotation occurs when printing to the fiery driver direct now? Color Printing Forum : Print Directory http://community.coreldraw.com/forums/p/10367/41764.aspx#41764
Island said:If I print an 11 x 17 landscape and select the print/paper size as 11 x 17 landscape on the latest xerox/fiery postscript printer driver, the print now comes out portrait on the 11x17 sheet rotated 90 degrees and cut off.
It's an incorrect boundry box in the PS output from Draw. You can see it in Ghostscript on screen.
Known and reported.
I guess the solution is to process the file via Acrobat.
The issue doesn't happen with every RIP as they often ignore the boundary box.
Yani
Thanks Paul and Yani for confirming before I tore my hair out over this frustrating issue.
At least I am able to use the PPD to get CorelDraw X4 to not rotate the print incorrectly, so I can print to the new machine (since I have a 5 year lease on the new printer, and other than this it's really nice.) By using the PPD workaround for Draw I do lose the Fiery GUI and some features like image shift which are not available in the PPD apparently. I hope Corel can fix this in the next service pack or version at least.
Any ideas on how to best advocate for a fix to this issue?
Just applied CorelDraw 4 SP2 and was hoping this would be fixed, but the problem was not fixed.
If I print from CorelDraw 4 SP2 (14.0.0.701) to an 11 x 17 sheet of paper and select landscape in the print driver, the print comes out of the xerox printer rotated 90 degrees on the sheet and cut-off. (as if I had selected portrait.)
I can print fine to the same printer/RIP using Adobe Photoshop or Adobe Acrobat without any rotation issue.
Printer is a Xerox Docucolor 242 with an EFI Fiery X3eTY RIP.
efi Driver version shows:
version: 3.0
Driver Version: 6.0.6001.18000
User Interface Version: 3.1.221.0
Server: DC-260-78A4CA
Server Version 2.0
Product Family X3TY
It's an odd problem in that my other software (all my non-CorelDraw software) can print to the same print driver without the rotation issue. At the same time my CorelDraw software can print to canon fiery rips without the rotation. So I'm left with my favorite softwrae (corel) and my new favorite printer (this new docucolor) being somewhat crippled by this rotation problem. Frustrating as I was really hoping for a fix in SP2.