GDI Printers

"But I'm just sending data to Windows - why doesn't the Windows printer driver just take care of it?" I probably hear that question at least a dozen times a year. Somebody wants to send Unix/Linux print jobs through Samba to a shared Windows printer and it's not working. Why not? Well, if the printer is a so called GDI, Windows-only ( sometimes called host-based) printer, the reason is simple: you aren't giving the driver what it wants. GDI printer drivers expect GDI data, a Microsoft format that is used both for displays and printers. It's basically a bit map of the page to be printed, but what's more important is what it is not: it isn't text, it isn't PostScript and it isn't PCL. The driver that Windows sends the GDI data to can't handle anything complicated like that; it can't convert text to graphics, can't draw lines from vector descriptions, etc. It needs GDI data and that's that. You'd think that there would be things that convert arbitrary data (text? PostScript?) to GDI. In fact, if you are even vaguely familiar with Linux, you would immediately think that GhostScript has an output that will produce GDI. You'd be right, too, except that it's apparently only available on Windows Ghostscript. That's called "mswinpr2", and you'd use it in combination with Redmon (a Windows print redirector) to do the translation. See PrintFile but again, that's done on the Windows side. You'd think that the easy way to do this would be to produce GDI output on the Linux side and then ship that through Samba to unmodified Windows machines. Or that's what I'd think anyway, and tantalizingly enough, "gs --help" lists "gdi" as one of its output formats. However, it looks to me like that produces PJL files. Unless I'm horribly misunderstanding what GDI looks like (see Del.icio.us") | Yahoo! My Web A.P. Lawrence provides SCO Unix and Linux consulting services http://www.pcunix.com