Hi,
I am asking these following set of questions in relation to the Desktop
printing task
http://www.opensolaris.org/os/project/jds/tasks/desktop_printing
on GTK+ Print Backend for PAPI:
1. If I set up to acess a remote print queue, such as
pdub0418dbl:\
:printer-uri-supported=lpd\://dbl-nw.Ireland/printers/pdub0405dbl#Solaris:\
:bsdaddr=dbl-nw.Ireland,pdub0405dbl,Solaris:\
:description=remote print server:
(My machine is a dhcp client), when I do lpstat -p pdub0418dbl, I only got
$ lpstat -p pdub0418dbl -l 2
printer pdub0418dbl idle. enabled since Tue Oct 31 16:17:49 2006. available.
printer-name=pdub0405dbl
printer-uri-supported=lpd://xxxx.Ireland/printers/pdub0405dbl#Solaris
printer-state-reasons=no entries
printer-state=3
This is the same result if I use the PAPI libraries call.
With only these information, it is hard to know what printer
capabilities does
this printer supports and to update the GUI accordingly. Is there anything
one can do or assume about these information?
2. On the local print queue, we typically have
number-up-supported=1
number-up-default=1
Is this really supported on the server? Playing around with it, doesn't
seems to
be so. But can this be made supported on the PAPI server side?
3. In a previous discussion, I was advised that I have to parse the PPD for
additional information. But it seems if the print queue is on the local
machine,
PAPI already parsed the PPD file and present these information through
the API.
Why do I need to parse the PPD file then?
If parsing the PPD file is required for the remote queue, there are
potentially 2 problems
- How does one know what is printer model the print queue is?
- What should one do while the print server may have the PPD file but
the local machine
has not that PPD file?
