Bug#966701: Driverless printing in buster via ipp-usb
Andrei POPESCU wrote: >>> +Both printing with CUPS and scanning with >>> +SANE are increasingly likely to be possible >>> +without the need for any (often non-free) driver specific > > For me this would sound better: > > ... without the need for any driver (often non-free) specific > >>> +to the model of the hardware, especially in the case of devices >>> marketed in the past five years or so. Oh, yes, that works now, good idea. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#966701: Driverless printing in buster via ipp-usb
On Sb, 20 mar 21, 14:48:22, Brian Potkin wrote: > On Sat 20 Mar 2021 at 14:17:11 +, Justin B Rye wrote: > > > > > Presumably a cut'n'pasteo. Thanks, revised patch attached. > > -- > > JBR with qualifications in linguistics, experience as a Debian > > sysadmin, and probably no clue about this particular package > > > diff --git a/en/whats-new.dbk b/en/whats-new.dbk > > index c301cfad..4435fce5 100644 > > --- a/en/whats-new.dbk > > +++ b/en/whats-new.dbk > > @@ -99,40 +99,74 @@ see any updates for these packages and they will be > > marked as > > linkend="obsolete"/>. > > > > > > - > > - SANE and driverless scanning > > + > > + Driverless scanning and printing > > > > -Driverless scanning is the ability to scan without requiring a > > -free or non-free backend driver specific to that scanner model. > > -It is mainly associated with modern multi-function devices, but > > -some modern standalone scanners are known to work > > -driverless. Modern refers to devices that have been > > +Both printing with CUPS and scanning with > > +SANE are increasingly likely to be possible > > +without the need for any (often non-free) driver specific For me this would sound better: ... without the need for any driver (often non-free) specific > > +to the model of the hardware, especially in the case of devices > > marketed in the past five years or so. > > Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#966701: Driverless printing in buster via ipp-usb
On Sat 20 Mar 2021 at 14:17:11 +, Justin B Rye wrote: > Brian Potkin wrote: > [...] > >> +Both printing with CUPS and scanning with > >> +SANE are increasingly likely to be possible > >> +without the need for any (often non-free) backend driver specific > > > > "backend" has different meaning in CUPS and SANE; I'd omit it. It > > is also a possible tautology. > > > > > +to the model of the hardware, especially in the case of devices > > > marketed in the past five years or so. > [...] > > > + > > ^ > > printing > > Presumably a cut'n'pasteo. Thanks, revised patch attached. > -- > JBR with qualifications in linguistics, experience as a Debian > sysadmin, and probably no clue about this particular package > diff --git a/en/whats-new.dbk b/en/whats-new.dbk > index c301cfad..4435fce5 100644 > --- a/en/whats-new.dbk > +++ b/en/whats-new.dbk > @@ -99,40 +99,74 @@ see any updates for these packages and they will be > marked as > linkend="obsolete"/>. > > > - > - SANE and driverless scanning > + > + Driverless scanning and printing > > -Driverless scanning is the ability to scan without requiring a > -free or non-free backend driver specific to that scanner model. > -It is mainly associated with modern multi-function devices, but > -some modern standalone scanners are known to work > -driverless. Modern refers to devices that have been > +Both printing with CUPS and scanning with > +SANE are increasingly likely to be possible > +without the need for any (often non-free) driver specific > +to the model of the hardware, especially in the case of devices > marketed in the past five years or so. > > - > -The official SANE driverless backend is > -provided by sane-escl in -role="package">libsane1. An independently developed > -driverless backend is -role="package">sane-airscan. Both backends understand > -the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL > -protocol but -role="package">sane-airscan can also use the -url="https://wiki.debian.org/SaneOverNetwork#wsd";>WSD > -protocol. Users should consider having both backends on their > -systems. > - > - > -eSCL and WSD are network > -protocols. Consequently they will operate over a USB connection if > -the device is an - > url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB > -device. Note that libsane1 > -has ipp-usb as a > -recommended package. This leads to a suitable device being > -automatically set up to use a driverless backend driver when it is > -connected to a USB port. > - > + > + > +CUPS and driverless printing > + > + Modern printers connected by ethernet or wireless can already use > + https://wiki.debian.org/CUPSQuickPrintQueues";>driverless > + printing, implemented via CUPS and + role="package">cups-filters, as was described in the + > url="https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing";>Release > + Notes for buster. Debian 11 bullseye > + brings the new package ipp-usb, > + which is recommended by cups-daemon > + and uses the vendor-neutral + > url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB > + protocol supported by many modern printers. This allows a USB > + device to be treated as a network device, extending driverless printing > + to include USB-connected printers. The specifics are outlined > + https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb";>on > + the wiki. > + > + > + The systemd service file included in the + role="package">ipp-usb package starts the > + ipp-usb daemon when a USB-connected > + printer is plugged in, thus making it available to print to. By > + default cups-browsed should > + configure it automatically, or it can be > + https://wiki.debian.org/SystemPrinting";>manually set > + up with a local driverless print queue. > + > + > + > + > +SANE and driverless scanning > + > + The official SANE driverless backend is > + provided by sane-escl in + role="package">libsane1. An independently developed > + driverless backend is + role="package">sane-airscan. Both backends understand > + the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL > + protocol but + role="package">sane-airscan can also use the + url="https://wiki.debian.org/SaneOverNetwork#wsd";>WSD > + protocol. Users should consider having both backends on their > + systems. > + > + > + eSCL and WSD are network > + protocols. Consequently they will operate over a USB connection if > + the device is an IPP-over-USB device (see > + above). Note that + role="package">libsane1 has
Bug#966701: Driverless printing in buster via ipp-usb
Brian Potkin wrote: [...] >> +Both printing with CUPS and scanning with >> +SANE are increasingly likely to be possible >> +without the need for any (often non-free) backend driver specific > > "backend" has different meaning in CUPS and SANE; I'd omit it. It > is also a possible tautology. > > > +to the model of the hardware, especially in the case of devices > > marketed in the past five years or so. [...] > > + > ^ > printing Presumably a cut'n'pasteo. Thanks, revised patch attached. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package diff --git a/en/whats-new.dbk b/en/whats-new.dbk index c301cfad..4435fce5 100644 --- a/en/whats-new.dbk +++ b/en/whats-new.dbk @@ -99,40 +99,74 @@ see any updates for these packages and they will be marked as linkend="obsolete"/>. - - SANE and driverless scanning + + Driverless scanning and printing -Driverless scanning is the ability to scan without requiring a -free or non-free backend driver specific to that scanner model. -It is mainly associated with modern multi-function devices, but -some modern standalone scanners are known to work -driverless. Modern refers to devices that have been +Both printing with CUPS and scanning with +SANE are increasingly likely to be possible +without the need for any (often non-free) driver specific +to the model of the hardware, especially in the case of devices marketed in the past five years or so. - -The official SANE driverless backend is -provided by sane-escl in libsane1. An independently developed -driverless backend is sane-airscan. Both backends understand -the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL -protocol but sane-airscan can also use the https://wiki.debian.org/SaneOverNetwork#wsd";>WSD -protocol. Users should consider having both backends on their -systems. - - -eSCL and WSD are network -protocols. Consequently they will operate over a USB connection if -the device is an https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB -device. Note that libsane1 -has ipp-usb as a -recommended package. This leads to a suitable device being -automatically set up to use a driverless backend driver when it is -connected to a USB port. - + + +CUPS and driverless printing + + Modern printers connected by ethernet or wireless can already use + https://wiki.debian.org/CUPSQuickPrintQueues";>driverless + printing, implemented via CUPS and cups-filters, as was described in the https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing";>Release + Notes for buster. Debian 11 bullseye + brings the new package ipp-usb, + which is recommended by cups-daemon + and uses the vendor-neutral https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB + protocol supported by many modern printers. This allows a USB + device to be treated as a network device, extending driverless printing + to include USB-connected printers. The specifics are outlined + https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb";>on + the wiki. + + + The systemd service file included in the ipp-usb package starts the + ipp-usb daemon when a USB-connected + printer is plugged in, thus making it available to print to. By + default cups-browsed should + configure it automatically, or it can be + https://wiki.debian.org/SystemPrinting";>manually set + up with a local driverless print queue. + + + + +SANE and driverless scanning + + The official SANE driverless backend is + provided by sane-escl in libsane1. An independently developed + driverless backend is sane-airscan. Both backends understand + the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL + protocol but sane-airscan can also use the https://wiki.debian.org/SaneOverNetwork#wsd";>WSD + protocol. Users should consider having both backends on their + systems. + + + eSCL and WSD are network + protocols. Consequently they will operate over a USB connection if + the device is an IPP-over-USB device (see + above). Note that libsane1 has ipp-usb as a recommended package. This + leads to a suitable device being automatically set up to use a + driverless backend driver when it is connected to a USB port. + + +
Bug#966701: Driverless printing in buster via ipp-usb
On Fri 19 Mar 2021 at 16:05:36 +, Justin B Rye wrote: > Justin B Rye wrote: > > Well, for a start, we don't want to make users read through two > > separate competing explanations of what driverless operation is when > > they only need to read one. We should try to pull out as much > > repeated material as possible from the two sections and say it in an > > introductory paragraph; and for that to work, they have to be in a > > joint "Printing and Scanning" section. > > Here's an attempt at a combi-printer/scanner section, incorporating > both the existing driverless-SANE part and your new driverless-CUPS > patch with a lot of squeezing of repetitive bits. I may well have > introduced Docbook syntax errors as well as garbling the sense. > -- > JBR with qualifications in linguistics, experience as a Debian > sysadmin, and probably no clue about this particular package > diff --git a/en/whats-new.dbk b/en/whats-new.dbk > index c301cfad..41b72c1e 100644 > --- a/en/whats-new.dbk > +++ b/en/whats-new.dbk > @@ -99,40 +99,74 @@ see any updates for these packages and they will be > marked as > linkend="obsolete"/>. > > > - > - SANE and driverless scanning > + > + Driverless scanning and printing > > -Driverless scanning is the ability to scan without requiring a > -free or non-free backend driver specific to that scanner model. > -It is mainly associated with modern multi-function devices, but > -some modern standalone scanners are known to work > -driverless. Modern refers to devices that have been > +Both printing with CUPS and scanning with > +SANE are increasingly likely to be possible > +without the need for any (often non-free) backend driver specific "backend" has different meaning in CUPS and SANE; I'd omit it. It is also a possible tautology. > +to the model of the hardware, especially in the case of devices > marketed in the past five years or so. > > - > -The official SANE driverless backend is > -provided by sane-escl in -role="package">libsane1. An independently developed > -driverless backend is -role="package">sane-airscan. Both backends understand > -the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL > -protocol but -role="package">sane-airscan can also use the -url="https://wiki.debian.org/SaneOverNetwork#wsd";>WSD > -protocol. Users should consider having both backends on their > -systems. > - > - > -eSCL and WSD are network > -protocols. Consequently they will operate over a USB connection if > -the device is an - > url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB > -device. Note that libsane1 > -has ipp-usb as a > -recommended package. This leads to a suitable device being > -automatically set up to use a driverless backend driver when it is > -connected to a USB port. > - > + > + ^ printing > +CUPS and driverless printing > + > + Modern printers connected by ethernet or wireless can already use > + https://wiki.debian.org/CUPSQuickPrintQueues";>driverless > + printing, implemented via CUPS and + role="package">cups-filters, as was described in the + > url="https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing";>Release > + Notes for buster. Debian 11 bullseye > + brings the new package ipp-usb, > + which is recommended by cups-daemon > + and uses the vendor-neutral + > url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB > + protocol supported by many modern printers. This allows a USB > + device to be treated as a network device, extending driverless printing > + to include USB-connected printers. The specifics are outlined > + https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb";>on > + the wiki. > + > + > + The systemd service file included in the + role="package">ipp-usb package starts the > + ipp-usb daemon when a USB-connected > + printer is plugged in, thus making it available to print to. By > + default cups-browsed should > + configure it automatically, or it can be > + https://wiki.debian.org/SystemPrinting";>manually set > + up with a local driverless print queue. > + > + > + > + > +SANE and driverless scanning > + > + The official SANE driverless backend is > + provided by sane-escl in + role="package">libsane1. An independently developed > + driverless backend is + role="package">sane-airscan. Both backends understand > + the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL > + protocol but + role="package">sane-airscan can also use the + url="https://wiki.debian.org/SaneOverNetwork#wsd";>WSD > + protocol. Users should consider having both backend
Bug#966701: Driverless printing in buster via ipp-usb
Justin B Rye wrote: > Well, for a start, we don't want to make users read through two > separate competing explanations of what driverless operation is when > they only need to read one. We should try to pull out as much > repeated material as possible from the two sections and say it in an > introductory paragraph; and for that to work, they have to be in a > joint "Printing and Scanning" section. Here's an attempt at a combi-printer/scanner section, incorporating both the existing driverless-SANE part and your new driverless-CUPS patch with a lot of squeezing of repetitive bits. I may well have introduced Docbook syntax errors as well as garbling the sense. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package diff --git a/en/whats-new.dbk b/en/whats-new.dbk index c301cfad..41b72c1e 100644 --- a/en/whats-new.dbk +++ b/en/whats-new.dbk @@ -99,40 +99,74 @@ see any updates for these packages and they will be marked as linkend="obsolete"/>. - - SANE and driverless scanning + + Driverless scanning and printing -Driverless scanning is the ability to scan without requiring a -free or non-free backend driver specific to that scanner model. -It is mainly associated with modern multi-function devices, but -some modern standalone scanners are known to work -driverless. Modern refers to devices that have been +Both printing with CUPS and scanning with +SANE are increasingly likely to be possible +without the need for any (often non-free) backend driver specific +to the model of the hardware, especially in the case of devices marketed in the past five years or so. - -The official SANE driverless backend is -provided by sane-escl in libsane1. An independently developed -driverless backend is sane-airscan. Both backends understand -the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL -protocol but sane-airscan can also use the https://wiki.debian.org/SaneOverNetwork#wsd";>WSD -protocol. Users should consider having both backends on their -systems. - - -eSCL and WSD are network -protocols. Consequently they will operate over a USB connection if -the device is an https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB -device. Note that libsane1 -has ipp-usb as a -recommended package. This leads to a suitable device being -automatically set up to use a driverless backend driver when it is -connected to a USB port. - + + +CUPS and driverless printing + + Modern printers connected by ethernet or wireless can already use + https://wiki.debian.org/CUPSQuickPrintQueues";>driverless + printing, implemented via CUPS and cups-filters, as was described in the https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing";>Release + Notes for buster. Debian 11 bullseye + brings the new package ipp-usb, + which is recommended by cups-daemon + and uses the vendor-neutral https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb";>IPP-over-USB + protocol supported by many modern printers. This allows a USB + device to be treated as a network device, extending driverless printing + to include USB-connected printers. The specifics are outlined + https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb";>on + the wiki. + + + The systemd service file included in the ipp-usb package starts the + ipp-usb daemon when a USB-connected + printer is plugged in, thus making it available to print to. By + default cups-browsed should + configure it automatically, or it can be + https://wiki.debian.org/SystemPrinting";>manually set + up with a local driverless print queue. + + + + +SANE and driverless scanning + + The official SANE driverless backend is + provided by sane-escl in libsane1. An independently developed + driverless backend is sane-airscan. Both backends understand + the https://wiki.debian.org/SaneOverNetwork#escl";>eSCL + protocol but sane-airscan can also use the https://wiki.debian.org/SaneOverNetwork#wsd";>WSD + protocol. Users should consider having both backends on their + systems. + + + eSCL and WSD are network + protocols. Consequently they will operate over a USB connection if + the device is an IPP-over-USB device (see + above). Note that libsane1 has ipp-usb as a recommended package. This + leads to a suitable device being automatically set up to use a + driverless backend driver when it is connected to a USB port. + + +
Bug#966701: Driverless printing in buster via ipp-usb
Brian Potkin >>> Justin B Rye wrote: Hang on, is this to go in "What's New"? If so, it's competing with a version that was added a couple of days ago - https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef Have you seen that version? >>> >>> Doesn't that concern driverless scanning? >> >> Ah, phew. But shouldn't they both be under a heading "Driverless >> Printing and Scanning in Bullseye", with a subsection on printing and >> a second subsection starting "Similarly..." on scanning? > > Printing and scanning involve completely [^different] processes, so I have an > aversion to lumping them together. Two many users start off an > issue description with "My scanner works but my printer doesn't." If we were documenting the internal implementation details, this would make sense, but the Release Notes are for users who have absolutely no reason to care about that. The thing that matters to owners of printer/scanner hardware is that they should expect similarly improved functionality for both these processes. Certainly there are differences in how CUPS and SANE achieve driverless operation, but in each case the user-visible changes boil down to "by pulling in new protocol-handling dependencies" (and in fact ipp-usb comes into play for both). > I don't see anything to be gained with a composite section. Well, for a start, we don't want to make users read through two separate competing explanations of what driverless operation is when they only need to read one. We should try to pull out as much repeated material as possible from the two sections and say it in an introductory paragraph; and for that to work, they have to be in a joint "Printing and Scanning" section. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#966701: Driverless printing in buster via ipp-usb
On Wed 17 Mar 2021 at 12:56:00 +, Brian Potkin wrote: > On Wed 17 Mar 2021 at 12:07:18 +, Justin B Rye wrote: > > > Brian Potkin wrote: > > > Justin B Rye wrote: > > >> Hang on, is this to go in "What's New"? If so, it's competing with a > > >> version that was added a couple of days ago - > > >> > > >> > > >> https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef > > >> > > >> Have you seen that version? > > > > > > Doesn't that concern driverless scanning? > > > > Ah, phew. But shouldn't they both be under a heading "Driverless > > Printing and Scanning in Bullseye", with a subsection on printing and > > a second subsection starting "Similarly..." on scanning? > > Printing and scanning involve completely processes, so I have an ^ different
Bug#966701: Driverless printing in buster via ipp-usb
On Wed 17 Mar 2021 at 12:07:18 +, Justin B Rye wrote: > Brian Potkin wrote: > > Justin B Rye wrote: > >> Hang on, is this to go in "What's New"? If so, it's competing with a > >> version that was added a couple of days ago - > >> > >> > >> https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef > >> > >> Have you seen that version? > > > > Doesn't that concern driverless scanning? > > Ah, phew. But shouldn't they both be under a heading "Driverless > Printing and Scanning in Bullseye", with a subsection on printing and > a second subsection starting "Similarly..." on scanning? Printing and scanning involve completely processes, so I have an aversion to lumping them together. Two many users start off an issue description with "My scanner works but my printer doesn't." I don't see anything to be gained with a composite section. -- Brian.
Bug#966701: Driverless printing in buster via ipp-usb
Brian Potkin wrote: > Justin B Rye wrote: >> Hang on, is this to go in "What's New"? If so, it's competing with a >> version that was added a couple of days ago - >> >> >> https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef >> >> Have you seen that version? > > Doesn't that concern driverless scanning? Ah, phew. But shouldn't they both be under a heading "Driverless Printing and Scanning in Bullseye", with a subsection on printing and a second subsection starting "Similarly..." on scanning? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#966701: Driverless printing in buster via ipp-usb
On Wed 17 Mar 2021 at 11:18:54 +, Justin B Rye wrote: > Hang on, is this to go in "What's New"? If so, it's competing with a > version that was added a couple of days ago - > > > https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef > > Have you seen that version? Doesn't that concern driverless scanning? -- Brian.
Bug#966701: Driverless printing in buster via ipp-usb
Hang on, is this to go in "What's New"? If so, it's competing with a version that was added a couple of days ago - https://salsa.debian.org/ddp-team/release-notes/-/commit/30e6ab258f8e98fe43ded83205b68645e74c5cef Have you seen that version? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#966701: Driverless printing in buster via ipp-usb
On Tue 16 Mar 2021 at 19:57:47 +, Justin B Rye wrote: > Brian Potkin wrote: > >> USB connected printers and driverless printing > >> -- > >> > >> The Release Notes for Debian 10 briefly describe the driverless printing > >> situation implemented via CUPS and cups-filters. [1] The changes apply to > >> modern printers connected by ethernet or wireless. [2] > >> > >> The release of Debian 11 sees the inclusion of ipp-usb in the stable > >> archive. ipp-usb is recommended by cups-daemon and utilises the > >> vendor-neutral IPP-over-USB protocol that is supported by many modern > >> printers. ipp-usb allows a USB device to be seen and treated as a network > >> device. The outcome is that driverless printing is extended to include USB > >> connected printers. The specifics are outlined on the wiki. [3] > >> > >> The systemd service file included in the ipp-usb package starts the > >> ipp-usb daemon when a printer is plugged in. A USB connected printer now > >> becomes available to print to, either by being auto-setup by cups-browsed, > >> which is the default technique, or being manually installed [4] with a > >> local driverless print queue. > >> > >> The use of vendor printer drivers, free and non-free, becomes unnecessary > >> with networked and USB connected printers. > >> > >> > >> [1] > >> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing > >> [2] https://wiki.debian.org/CUPSQuickPrintQueues > >> [3] https://wiki.debian.org/CUPSDriverlessPrinting. > >> [4] https://wiki.debian.org/SystemPrinting > > > > Thinking on: > > > > The Release Notes for Debian 10 briefly describe... > > > > should probably be > > > > The Release Notes for Debian 10 briefly describes... > > Plural "notes", so I'd say that they "describe" the situation (and my > native en_GB tends if anything to be more tolerant than en_US of > mismatches). But it might be worth shifting things round so that the > sentence has a different subject, since this would let it introduce > topics in a more natural order: > >Modern printers connected by ethernet or wireless [1] can use driverless >printing, implemented via CUPS and cups-filters, as described in the >Debian 10 "buster" Release Notes. [2] I haven't any problem with that change. I particularly wanted a referral to buster because many users are still apparently unaware of the changes in the printing system. This is noticable with HP devices; HPLIP has "HP" in its name, so it must be good! > [...] > >[1] https://wiki.debian.org/CUPSQuickPrintQueues >[2] > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing > > Oh, watch out, that /stable/ URL will point at the wrong thing soon! > We need >[2] > https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.en.html#driverless-printing A good point. > > Having [3] as > > > > https://wiki.debian.org/CUPSDriverlessPrinting#debian > > > > might be considered more targeted. > > Calling that anchor "#debian" implies that the rest of the page is > about something other than Debian; and using the release name as a > section title will make things harder to follow once we're moving > towards Debian 12 "bookworm"! Couldn't the section be titled > something like "IPP-over-USB: automatic setup"? I'd see that as a wiki issue rather a Release Notes issue; thanks for raising it. I am inclining towards adopting your section title suggestion. Regards, Brian.
Bug#966701: Driverless printing in buster via ipp-usb
Brian Potkin wrote: >> USB connected printers and driverless printing >> -- >> >> The Release Notes for Debian 10 briefly describe the driverless printing >> situation implemented via CUPS and cups-filters. [1] The changes apply to >> modern printers connected by ethernet or wireless. [2] >> >> The release of Debian 11 sees the inclusion of ipp-usb in the stable >> archive. ipp-usb is recommended by cups-daemon and utilises the >> vendor-neutral IPP-over-USB protocol that is supported by many modern >> printers. ipp-usb allows a USB device to be seen and treated as a network >> device. The outcome is that driverless printing is extended to include USB >> connected printers. The specifics are outlined on the wiki. [3] >> >> The systemd service file included in the ipp-usb package starts the >> ipp-usb daemon when a printer is plugged in. A USB connected printer now >> becomes available to print to, either by being auto-setup by cups-browsed, >> which is the default technique, or being manually installed [4] with a >> local driverless print queue. >> >> The use of vendor printer drivers, free and non-free, becomes unnecessary >> with networked and USB connected printers. >> >> >> [1] >> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing >> [2] https://wiki.debian.org/CUPSQuickPrintQueues >> [3] https://wiki.debian.org/CUPSDriverlessPrinting. >> [4] https://wiki.debian.org/SystemPrinting > > Thinking on: > > The Release Notes for Debian 10 briefly describe... > > should probably be > > The Release Notes for Debian 10 briefly describes... Plural "notes", so I'd say that they "describe" the situation (and my native en_GB tends if anything to be more tolerant than en_US of mismatches). But it might be worth shifting things round so that the sentence has a different subject, since this would let it introduce topics in a more natural order: Modern printers connected by ethernet or wireless [1] can use driverless printing, implemented via CUPS and cups-filters, as described in the Debian 10 "buster" Release Notes. [2] [...] [1] https://wiki.debian.org/CUPSQuickPrintQueues [2] https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing Oh, watch out, that /stable/ URL will point at the wrong thing soon! We need [2] https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.en.html#driverless-printing > Having [3] as > > https://wiki.debian.org/CUPSDriverlessPrinting#debian > > might be considered more targeted. Calling that anchor "#debian" implies that the rest of the page is about something other than Debian; and using the release name as a section title will make things harder to follow once we're moving towards Debian 12 "bookworm"! Couldn't the section be titled something like "IPP-over-USB: automatic setup"? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#966701: Driverless printing in buster via ipp-usb
On Wed 23 Sep 2020 at 19:54:14 +0100, Brian Potkin wrote: > I would like the following version to replace previous offering: > > > USB connected printers and driverless printing > -- > > The Release Notes for Debian 10 briefly describe the driverless printing > situation implemented via CUPS and cups-filters. [1] The changes apply to > modern printers connected by ethernet or wireless. [2] > > The release of Debian 11 sees the inclusion of ipp-usb in the stable > archive. ipp-usb is recommended by cups-daemon and utilises the > vendor-neutral IPP-over-USB protocol that is supported by many modern > printers. ipp-usb allows a USB device to be seen and treated as a network > device. The outcome is that driverless printing is extended to include USB > connected printers. The specifics are outlined on the wiki. [3] > > The systemd service file included in the ipp-usb package starts the > ipp-usb daemon when a printer is plugged in. A USB connected printer now > becomes available to print to, either by being auto-setup by cups-browsed, > which is the default technique, or being manually installed [4] with a > local driverless print queue. > > The use of vendor printer drivers, free and non-free, becomes unnecessary > with networked and USB connected printers. > > > [1] > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing > [2] https://wiki.debian.org/CUPSQuickPrintQueues > [3] https://wiki.debian.org/CUPSDriverlessPrinting. > [4] https://wiki.debian.org/SystemPrinting > > Cheers, > > Brian. Thinking on: The Release Notes for Debian 10 briefly describe... should probably be The Release Notes for Debian 10 briefly describes... Having [3] as https://wiki.debian.org/CUPSDriverlessPrinting#debian might be considered more targeted. Cheers, Brian.
Bug#966701: Driverless printing in buster via ipp-usb
I would like the following version to replace previous offering: USB connected printers and driverless printing -- The Release Notes for Debian 10 briefly describe the driverless printing situation implemented via CUPS and cups-filters. [1] The changes apply to modern printers connected by ethernet or wireless. [2] The release of Debian 11 sees the inclusion of ipp-usb in the stable archive. ipp-usb is recommended by cups-daemon and utilises the vendor-neutral IPP-over-USB protocol that is supported by many modern printers. ipp-usb allows a USB device to be seen and treated as a network device. The outcome is that driverless printing is extended to include USB connected printers. The specifics are outlined on the wiki. [3] The systemd service file included in the ipp-usb package starts the ipp-usb daemon when a printer is plugged in. A USB connected printer now becomes available to print to, either by being auto-setup by cups-browsed, which is the default technique, or being manually installed [4] with a local driverless print queue. The use of vendor printer drivers, free and non-free, becomes unnecessary with networked and USB connected printers. [1] https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing [2] https://wiki.debian.org/CUPSQuickPrintQueues [3] https://wiki.debian.org/CUPSDriverlessPrinting. [4] https://wiki.debian.org/SystemPrinting Cheers, Brian.
Bug#966701: Driverless printing in buster via ipp-usb
Package: release-notes Severity: wishlist On Sb, 01 aug 20, 18:10:22, Brian Potkin wrote: > On behalf of the Printing Team: > > > > The Release Notes for Debian 10 briefly described the driverless > > printing situation implemented via CUPS and cups-filters. The changes > > applied to modern printers connected by ethernet or wireless. > > > > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#driverless-printing > > > > The release of Debian 11 sees the inclusion of ipp-usb into the stable > > archive. ipp-usb is recommended by cups-daemon and utilises the > > vendor-neutral IPP-over-USB protocol that is supported by many modern > > printers. ipp-usb allows a USB device to be seen and treated as a > > network device. The outcome is that driverless printing is extended to > > include USB connected printers. The specifics are outlined at > > > > https://wiki.debian.org/CUPSDriverlessPrinting. > > > > The systemd service file included in ipp-usb starts the ipp-usb daemon > > when a printer is plugged in, making a USB connected printer available > > for printing to, either by being auto-setup by cups-browsed or being > > manually installed with a local driverless print queue. The use of > > vendor printer drivers, free and non-free, becomes unnecessary. > > Let's turn this into a bug so it's not missed. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
