Native Win32 Cups Client?

[Anonymous]

>
> Only "get a list of printers" is not sufficient.
>
> Note that normally printing under Windows is done different
> than under Unix/Linux.
> See for example the "two longer explanations" in
> http://lists.suse.com/archive/suse-linux-e/2004-Nov/1186.html
>
> I.e. the CUPS client for Windows must also convert the usual
> Windows document types (e.g. "doc") to something which can be
> processed by the CUPS filtering system (i.e. to PostScript).
>

Thanks for that, some good info there. I guess the solution could be, when the list is discovered by the Windows CUPS client it uses a generic printer driver on the windows side and then just sends that to the CUPS server.

It could work similar to rdesktop, when you redirect a local printer to a RDP session, on the Windows Server side it thinks you have a HP Colour Laserjet in Postscript mode. So the windows applications just send Postscript down the the Linux client and then the local print system just does the filtering, spooling and printing locally.

So in CUPS, the Win32 CUPS client discovers all printers on the local Subnet, it then adds these to the Windows printer list, telling Windows to use the HP Colour Laserjet Postscript driver. Then when a user prints to one of the CUPS discovered printers it just sends a postscript job over to the CUPS server that has that printer attached which does the neccesary filtering / spooling / printing.

Thoughts anyone?

Cheers

Mark Johnson