On Thu, 2005-01-20 at 10:45 -0500, Michael Stone wrote: > > Why does the xprint config file require the printer's resolution to be > hard-coded? The current situation is that a client system is configured > to point to a cups server to get a dynamic printer list, then xprint > needs a hard coded default resolution and a hard coded exception for > every printer that doesn't use the default. Having the ability to get > the printer list dynamically is useless if I have to change the client > for every new printer in order to get it to actually print properly... >
Upstream may be able to give a more comprehensive answer, but I can give just these 2 points: 1) It's just the way it is. No one's yet gone to the trouble of writing the extra code which will connect to the CUPS servers to grab the dynamic info off them. There's no simple tool like lpstat which does it, you've got to go to the libcupsys API. First person to provide the patch wins a six-pack of beer. 2) Xprint does not just support CUPS, it supports any printing system which provides a BSD or a SYSV interface. LPRng, for instance. Bear in mind, furthermore, that the printer list is only partially dynamic, discovered at start up. If the CUPS (or other) list is changed, Xprint will only find out when restarted, or by running xprehashprinterlist. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
