http://bugs.winehq.org/show_bug.cgi?id=3599
------- Additional Comments From roli8200@yahoo.de 2006-19-07 06:12 -------
The logs do not help me to find an error in winspool, that result in the mentioned failure. ("+psdrv" from comment #1 was not included. "Please add ..." from my comment #6)
Its seems rater that the psdrv wasn't used by corel draw. And I think it isn't "bug" in a literal sense. The bug is more in the logical meaning of the wineprint. There should (must) be configuration options to configure: - Which printer type is reported to the windows apps Should rater report the original printer type configured in cups than just tell the app: Its just postscript printer. I think if wine whould report a "normal" (in my case) HP Laserjet 4 Corel would use the "normal" winprint api instead of self generating postscript code - What to do with the generated (in case of Corel) post script code.
I think the whole reason behind this bug is that wine transports the generated postscript code directly "as text" to the printerspooler instead to tell him "Look here comes postscript code, render it for the selected printer model". This assumption is based on the first line of the paper printed postscript code: "%%BeginDocument: Wine passthrough". So its just a matter of the handling of the generated printer code and this should not be that big reason to handle that.