Hi,
I'm having some kind of hard time with wine's printing capabilities and have already started digging the wine sources for potential fixes to my problems (printing to some high volume postscript printers from some Adobe applications).
But before I proceed any further, I would be grateful for some basic information on wine's printing system (unfortunately the documentation on this issue is somewhat "limited" :-)
* Postscript level Googling the net some resources indicate that wine only supports postscript level 1 printing. Is this still true as of now? Does this also affect CUPS environments?
* Postscript level vs. PPDs If wine only supports language level 1, why then does generic.ppd have its LanguageLevel set to 3?
* starting point Most of the printing tasks are obviously handled by the stuff in dlls/wineps/*. Any other important nodes?
happy hacking
Udo Rader
On Mon, Jan 03, 2005 at 07:16:20PM +0100, Udo Rader wrote:
Hi,
I'm having some kind of hard time with wine's printing capabilities and have already started digging the wine sources for potential fixes to my problems (printing to some high volume postscript printers from some Adobe applications).
But before I proceed any further, I would be grateful for some basic information on wine's printing system (unfortunately the documentation on this issue is somewhat "limited" :-)
- Postscript level
Googling the net some resources indicate that wine only supports postscript level 1 printing. Is this still true as of now? Does this also affect CUPS environments?
No clue.
You can print color with wineps, which is not a level 1 feature, so I suspect that this is not quite true.
- Postscript level vs. PPDs
If wine only supports language level 1, why then does generic.ppd have its LanguageLevel set to 3?
I copied it from a sample PPD file at the time of creation.
- starting point
Most of the printing tasks are obviously handled by the stuff in dlls/wineps/*. Any other important nodes?
dlls/winspool/ has the spooling stuff, but this is of less interest.
Ciao, Marcus
On Mon, 3 Jan 2005, Udo Rader wrote:
Hi,
I'm having some kind of hard time with wine's printing capabilities and have already started digging the wine sources for potential fixes to my problems (printing to some high volume postscript printers from some Adobe applications).
You need to be more specific here. If you're trying to print stuff from Acrobat Reader (now called Adobe Reader), then that's known not to work.
If printing from that application works with some printers but not with others, then it may be an incompatibility between the postscript generated by Wine and the postscript interpreter of the printer...
On Wed, 2005-01-05 at 12:02 +0100, Francois Gouget wrote:
On Mon, 3 Jan 2005, Udo Rader wrote:
Hi,
I'm having some kind of hard time with wine's printing capabilities and have already started digging the wine sources for potential fixes to my problems (printing to some high volume postscript printers from some Adobe applications).
You need to be more specific here. If you're trying to print stuff from Acrobat Reader (now called Adobe Reader), then that's known not to work.
Yes, one of the applications I am trying to print out with is Acrobat Reader. Others are "locally focused" applications, eg. some old warehouse management software.
If printing from that application works with some printers but not with others, then it may be an incompatibility between the postscript generated by Wine and the postscript interpreter of the printer...
Thats exactly the case. I've tried a couple of things so far, starting with dirty workarounds like piping the postscript generated by wineps through ghostscript's pswriter device, but that is not really satisfying (printing works but the postscript codesize increases dramatically). Thus I at least want to try to reach the bottom of the problem, which IMHO is likely to be in wineps ...
happy hacking
udo rader
Hi,
On Wed, Jan 05, 2005 at 12:50:24PM +0100, Udo Rader wrote:
On Wed, 2005-01-05 at 12:02 +0100, Francois Gouget wrote:
If printing from that application works with some printers but not with others, then it may be an incompatibility between the postscript generated by Wine and the postscript interpreter of the printer...
Thats exactly the case. I've tried a couple of things so far, starting with dirty workarounds like piping the postscript generated by wineps through ghostscript's pswriter device, but that is not really satisfying (printing works but the postscript codesize increases dramatically). Thus I at least want to try to reach the bottom of the problem, which IMHO is likely to be in wineps ...
[just pointing out obvious things here] You should probably try to print very, very simple documents, maybe very simple ones suddenly start to work. If that doesn't help, try using different applications which don't work with a large printout, but do work with a much less complicated printout. Once you get one PostScript file that works, you could compare it with a slightly differing one that doesn't work, to find the issue.
Good luck!
Andreas Mohr