From: Grant T. <gt...@pi...> - 2001-04-05 22:36:51
|
>>>>> Mark Pruett <mp...@va...> writes: > Defining setpagedevice strings for these options won't cause any > problem for CUPS? Does CUPS use these PPD files in a different way > (not using the setpagedevice strings)? No, by definition CUPS and gpr's ppdfilt tread PPD options exactly the same way; libppd is merely a repackaged pstops from CUPS, after all. > Currently, gpr is PPD-centric, so we need to get as many useable > setpagedevice options into the PPD files as we can. I've been using > gpr almost exclusively for printing from netscape (with my HP > laserjet) and it's great for selecting options on-the-fly. Now it > looks like we're very close to supporting all these inkjets in gpr > as well. Yup. You'll still need some other option processing to be able to run drivers with non-postscript options. What we ought to do is sit down and make a filter "gnulpromatic" that uses the CUPS data files. Then you'll magically get support for printers from the other 199 manufacturers that you don't do now. > Having the 2-up/4-up feature built into gpr will save some people a > lot of paper (and ink) too. Yes, it's nice. I keep meaning to respin lpdomatic around pstops or pddfilt to get that stuff in. -- Grant Taylor - gt...@pi... - http://www.picante.com/~gtaylor/ Linux Printing Website and HOWTO: http://www.linuxprinting.org/ |