-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] Include fax-specific options in "job-creation-attributes-supported" and "ipp-features-supported" if the queue is fax queue #459
Comments
Not only for CPDB but also in general for PPD-less printing (CUPS 3.x, New Architecture) one needs some hint that a print queue is actually a fax queue in the response to the |
My printer's answer to the
What is the "official" indicator that this is the fax queue of the printer? Is it the |
@tillkamppeter Yes, the 'faxout' in the "ipp-features-supported" attribute is what you want to look for when querying a particular URI. For DNS-SD, the presence of the "rfo" key tells you the printer also supports facsimile. |
@michaelrsweet thanks. But then the bug in CUPS is that if we have a fax queue (with appropriate attributes in the PPD) CUPS must advertise it properly, adding the |
Note that in the subject and in the initial posting most probably |
Yes, I accidentally mixed the two terms. What is the difference between them? |
@TinyTrebuchet IIUC job-settable-attributes are the attributes which can be set on job object as a whole, and job-creation-attributes are the attributes which you can set to the job object only if you are about to do Print-Job, Create-Job, Validate-Job and Print-URI requests. |
Marking this as RFE, since we haven't been sharing anything related to fax till now, and ipp-features-supported is hard-coded only to |
@zdohnal Indeed, ipp-features-supported should definitely include ipp-everywhere. @TinyTrebuchet From an IPP perspective, job-settable-attributes-supported specifies which Job attributes can be changed by a Set-Job-Attributes request after submission, while job-creation-attributes-supported specifies which attributes are supported in Create-Job and Print-Job requests. |
@zdohnal this should be simple to fix and not cause any regression risks. And this is very useful, as with this print dialogs can tell print and fax queues apart without resorting to PPD files. And as the current work on the Common Print Dialog Backends by @TinyTrebuchet is already working without PPDs and therefore full prepared for the New Architecture (CUPS 3.x) we should do this change soon. I do not want @TinyTrebuchet to re-introduce PPD support solely for determining whether a CUPS queue is a fax queue or not. |
@michaelrsweet could you do that little change of CUPS queues which are fax queues (appropriate fax attributes in their PPD files) include the |
@tillkamppeter I’ll take a look… |
The above PR should fix this. |
@tillkamppeter @TinyTrebuchet afaik the PR fixes the one part of the issue - sharing faxout in the ipp-features-supported, but the original problem, sharing fax-related attributes in the If you can provide the list of attributes which are suited for |
My printer, get-printer-attributes IPP response attached to an earlier comment here, has no |
@michaelrsweet do you know what a CUPS queue which faxes the job has to put into the get-printer-attributes response so that for a client it is like a network multi-function printer's fax queue? |
The fax-specific options (like phone number, etc) are not appearing as job-settable:
Furthermore, the printer attributes list generated using
ipptool -tv <PRINT-QUEUE> get-printer-attributes.test > attrs.txt
shows no mention of any fax-related option (other than in the name of print-queue itself). There is also no attribute for telling whether the print-queue is a fax or not.This is problematic for CPD CUPS backend, as it uses "job-creation-attributes" to get a fetch and forward list of CUPS options to the CPD frontend.
The attached PPD file is for a fax queue, generated with
driverless-fax
: hp8730fax.ppd.txtThe text was updated successfully, but these errors were encountered: