On Tue, May 25, 2021 at 01:27:03AM +0200, Kevin Kofler via devel wrote:
All this is of no use if the printer does not actually implement that though.
Of course. That's where this whole "printer application" thingey comes in.
I do not see how that is the common use case. Why would I want to print from my telephone? I do not even normally print from my notebook!
I don't think it's controversial to say that one needs to print from whatever computing devices one uses.
Well, if I want to configure the printer, I need to know what to point my browser at. But sure, if a dialog gives me a link, that is a way. Though it means yet another layer of indirection (bringing up the dialog first, only to get redirected to a web interface).
Running 'ippfind' will show you the list of all IPP-capable printers that are advertising themselves through mDNS, and the URI they can be reached at.
My desktop and my notebook, i.e., the devices I actually SSH to at times (from each other, usually), do have hardcoded IPs, yes. (And I also use X11 forwarding when I SSH, so Wayland is a non-starter.)
X11 forwarding through SSH while running Wayland seems to work just fine for me. *shrug*
More often than not, the "PDF-based print flow" just means that something client-side converts the PostScript to PDF before sending it to the shiny new "PDF-based print flow", only to have something in the driver filters convert the PDF back to PostScript before doing anything else.
This hasn't been the case since Fedora 19 (Spring 2013), which, as part of CUPS 1.6, switched to a PDF-native flow. Postscript is only used on the edges, ie if the printer requires it or the application supplies it. pdftopdf transforms proved to be a lot more robust than pstops due to PDF's semantics being far better defined.
(Incidently, Fedora 19 is also when the switch to using mDNS for printer discovery happened..)
- Solomon