There is not really a spec needed for this problem (whereas in general a "Make printing just work" spec is a great idea for the next UDS, only that I cannot participate in the UDS because I have an OpenPrinting meeting in Tokyo then).
I had some talk with HP on the OpenPrinting Summit 2007 in Montreal last week and they are working on this problem. See
So I think we should wait for HPLIP 2.7.10 and only if the problem is not addressed there think about calling foo2zjs scripts from the restricted-manager. I will add an HPLIP task. If HP solves this issue I will close the foo2zjs task and depending on HP's solution also the restricted-manager task.
Let's see what HP will do and decide before the end of this year. Then we have 3 months/2 alphas + 1 beta for intensive testing.
There is not really a spec needed for this problem (whereas in general a "Make printing just work" spec is a great idea for the next UDS, only that I cannot participate in the UDS because I have an OpenPrinting meeting in Tokyo then).
I had some talk with HP on the OpenPrinting Summit 2007 in Montreal last week and they are working on this problem. See
https:/ /www.linux- foundation. org/en/ OpenPrinting/ SummitMontreal
and
https:/ /www.linux- foundation. org/images/ 5/5f/LinuxPrint ingSummitHPLinu xPrintingUpdate .pdf /www.linux- foundation. org/images/ b/bd/Plugins. pdf
https:/
So I think we should wait for HPLIP 2.7.10 and only if the problem is not addressed there think about calling foo2zjs scripts from the restricted-manager. I will add an HPLIP task. If HP solves this issue I will close the foo2zjs task and depending on HP's solution also the restricted-manager task.
Let's see what HP will do and decide before the end of this year. Then we have 3 months/2 alphas + 1 beta for intensive testing.