For inclusion in Debian 11's Release Notes

[Brian Potkin]

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.

========================================================================


Regards,

Brian.

[Andrei POPESCU]

Package: release-notes
Severity: wishlist

Post by Brian Potkin
========================================================================
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

[Brian Potkin]

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.

[Brian Potkin]

Post by Brian Potkin
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.

[Justin B Rye]

Post by Brian Potkin

Post by Brian Potkin
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

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

Post by Brian Potkin
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"?

[Brian Potkin]

Post by Justin B Rye

Post by Brian Potkin

Post by Brian Potkin
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

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
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!

Post by Justin B Rye
[...]
[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.

Post by Justin B Rye

Post by Brian Potkin
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.

[Justin B Rye]

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?

[Brian Potkin]

Post by Justin B Rye
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?

[Justin B Rye]

Post by Brian Potkin

Post by Justin B Rye
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?

[Brian Potkin]

Post by Justin B Rye

Post by Brian Potkin

Post by Justin B Rye
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 Potkin]

Post by Brian Potkin

Post by Justin B Rye

Post by Brian Potkin

Post by Justin B Rye
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

[Justin B Rye]

Brian Potkin

Post by Justin B Rye

Post by Brian Potkin

Post by Justin B Rye
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.

[Justin B Rye]

Post by Justin B Rye
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.

[Brian Potkin]

Post by Justin B Rye

Post by Justin B Rye
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"/>.
</para>
-<section id="sane-driverless-scanning">
- <title>SANE and driverless scanning</title>
+<section id="driverless-operation">
+ <title>Driverless scanning and printing</title>
<para>
- 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. <quote>Modern</quote> refers to devices that have been
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> 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.

Post by Justin B Rye
+ to the model of the hardware, especially in the case of devices
marketed in the past five years or so.
</para>
- <para>
- The official <literal>SANE</literal> driverless backend is
- provided by <literal>sane-escl</literal> in <systemitem
- role="package">libsane1</systemitem>. An independently developed
- driverless backend is <systemitem
- role="package">sane-airscan</systemitem>. Both backends understand
- the <ulink url="https://wiki.debian.org/SaneOverNetwork#escl">eSCL
- protocol</ulink> but <systemitem
- role="package">sane-airscan</systemitem> can also use the <ulink
- url="https://wiki.debian.org/SaneOverNetwork#wsd">WSD</ulink>
- protocol. Users should consider having both backends on their
- systems.
- </para>
- <para>
- <literal>eSCL</literal> and <literal>WSD</literal> are network
- protocols. Consequently they will operate over a USB connection if
- the device is an <ulink
- url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb">IPP-over-USB</ulink>
- device. Note that <systemitem role="package">libsane1</systemitem>
- has <systemitem role="package">ipp-usb</systemitem> 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.
- </para>
+
+ <section id="CUPS and driverless printinging">

^
printing

Post by Justin B Rye
+ <title>CUPS and driverless printing</title>
+ <para>
+ Modern printers connected by ethernet or wireless can already use
+ <ulink url="https://wiki.debian.org/CUPSQuickPrintQueues">driverless
+ printing</ulink>, implemented via <literal>CUPS</literal> and <sysitem
+ role="package">cups-filters</sysitem>, as was described in the <ulink
+ url="https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing">Release
+ Notes for buster</ulink>. Debian 11 <quote>bullseye</quote>
+ brings the new package <systemitem role="package">ipp-usb</sysitem>,
+ which is recommended by <systemitem role="package">cups-daemon</sysitem>
+ and uses the vendor-neutral <ulink
+ url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb">IPP-over-USB</ulink>
+ 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
+ <ulink url="https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb">on
+ the wiki</ulink>.
+ </para>
+ <para>
+ The systemd service file included in the <systemitem
+ role="package">ipp-usb</sysitem> package starts the
+ <literal>ipp-usb</literal> daemon when a USB-connected
+ printer is plugged in, thus making it available to print to. By
+ default <systemitem role="package">cups-browsed</sysitem> should
+ configure it automatically, or it can be
+ <ulink url="https://wiki.debian.org/SystemPrinting">manually set
+ up with a local driverless print queue</ulink>.
+ </para>
+ </section>
+
+ <section id="SANE and driverless scanning">
+ <title>SANE and driverless scanning</title>
+ <para>
+ The official <literal>SANE</literal> driverless backend is
+ provided by <literal>sane-escl</literal> in <systemitem
+ role="package">libsane1</systemitem>. An independently developed
+ driverless backend is <systemitem
+ role="package">sane-airscan</systemitem>. Both backends understand
+ the <ulink url="https://wiki.debian.org/SaneOverNetwork#escl">eSCL
+ protocol</ulink> but <systemitem
+ role="package">sane-airscan</systemitem> can also use the <ulink
+ url="https://wiki.debian.org/SaneOverNetwork#wsd">WSD</ulink>
+ protocol. Users should consider having both backends on their
+ systems.
+ </para>
+ <para>
+ <literal>eSCL</literal> and <literal>WSD</literal> are network
+ protocols. Consequently they will operate over a USB connection if
+ the device is an <literal>IPP-over-USB</literal> device (see
+ above). Note that <systemitem
+ role="package">libsane1</systemitem> has <systemitem
+ role="package">ipp-usb</systemitem> 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.
+ </para>
+ </section>
+
</section>
<section id="major-packages">

THe rest looks OK.

[Justin B Rye]

Brian Potkin wrote:
[...]

Post by Brian Potkin

Post by Justin B Rye
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> 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.

Post by Justin B Rye
+ to the model of the hardware, especially in the case of devices
marketed in the past five years or so.

[...]

Post by Brian Potkin

Post by Justin B Rye
+ <section id="CUPS and driverless printinging">

^
printing

Presumably a cut'n'pasteo. Thanks, revised patch attached.

[Brian Potkin]

Post by Justin B Rye
[...]

Post by Brian Potkin

Post by Justin B Rye
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> 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.

Post by Justin B Rye
+ to the model of the hardware, especially in the case of devices
marketed in the past five years or so.

[...]

Post by Brian Potkin

Post by Justin B Rye
+ <section id="CUPS and driverless printinging">

^
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"/>.
</para>
-<section id="sane-driverless-scanning">
- <title>SANE and driverless scanning</title>
+<section id="driverless-operation">
+ <title>Driverless scanning and printing</title>
<para>
- 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. <quote>Modern</quote> refers to devices that have been
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> 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.
</para>
- <para>
- The official <literal>SANE</literal> driverless backend is
- provided by <literal>sane-escl</literal> in <systemitem
- role="package">libsane1</systemitem>. An independently developed
- driverless backend is <systemitem
- role="package">sane-airscan</systemitem>. Both backends understand
- the <ulink url="https://wiki.debian.org/SaneOverNetwork#escl">eSCL
- protocol</ulink> but <systemitem
- role="package">sane-airscan</systemitem> can also use the <ulink
- url="https://wiki.debian.org/SaneOverNetwork#wsd">WSD</ulink>
- protocol. Users should consider having both backends on their
- systems.
- </para>
- <para>
- <literal>eSCL</literal> and <literal>WSD</literal> are network
- protocols. Consequently they will operate over a USB connection if
- the device is an <ulink
- url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb">IPP-over-USB</ulink>
- device. Note that <systemitem role="package">libsane1</systemitem>
- has <systemitem role="package">ipp-usb</systemitem> 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.
- </para>
+
+ <section id="CUPS and driverless printing">
+ <title>CUPS and driverless printing</title>
+ <para>
+ Modern printers connected by ethernet or wireless can already use
+ <ulink url="https://wiki.debian.org/CUPSQuickPrintQueues">driverless
+ printing</ulink>, implemented via <literal>CUPS</literal> and <sysitem
+ role="package">cups-filters</sysitem>, as was described in the <ulink
+ url="https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.html#driverless-printing">Release
+ Notes for buster</ulink>. Debian 11 <quote>bullseye</quote>
+ brings the new package <systemitem role="package">ipp-usb</sysitem>,
+ which is recommended by <systemitem role="package">cups-daemon</sysitem>
+ and uses the vendor-neutral <ulink
+ url="https://wiki.debian.org/CUPSDriverlessPrinting#ippoverusb">IPP-over-USB</ulink>
+ 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
+ <ulink url="https://wiki.debian.org/CUPSDriverlessPrinting#ipp-usb">on
+ the wiki</ulink>.
+ </para>
+ <para>
+ The systemd service file included in the <systemitem
+ role="package">ipp-usb</sysitem> package starts the
+ <literal>ipp-usb</literal> daemon when a USB-connected
+ printer is plugged in, thus making it available to print to. By
+ default <systemitem role="package">cups-browsed</sysitem> should
+ configure it automatically, or it can be
+ <ulink url="https://wiki.debian.org/SystemPrinting">manually set
+ up with a local driverless print queue</ulink>.
+ </para>
+ </section>
+
+ <section id="SANE and driverless scanning">
+ <title>SANE and driverless scanning</title>
+ <para>
+ The official <literal>SANE</literal> driverless backend is
+ provided by <literal>sane-escl</literal> in <systemitem
+ role="package">libsane1</systemitem>. An independently developed
+ driverless backend is <systemitem
+ role="package">sane-airscan</systemitem>. Both backends understand
+ the <ulink url="https://wiki.debian.org/SaneOverNetwork#escl">eSCL
+ protocol</ulink> but <systemitem
+ role="package">sane-airscan</systemitem> can also use the <ulink
+ url="https://wiki.debian.org/SaneOverNetwork#wsd">WSD</ulink>
+ protocol. Users should consider having both backends on their
+ systems.
+ </para>
+ <para>
+ <literal>eSCL</literal> and <literal>WSD</literal> are network
+ protocols. Consequently they will operate over a USB connection if
+ the device is an <literal>IPP-over-USB</literal> device (see
+ above). Note that <systemitem
+ role="package">libsane1</systemitem> has <systemitem
+ role="package">ipp-usb</systemitem> 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.
+ </para>
+ </section>
+
</section>
<section id="major-packages">

I have read the text a couple of times and have not spotted anything
untoward. Thanks.

[Andrei POPESCU]

Post by Justin B Rye
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"/>.
</para>
-<section id="sane-driverless-scanning">
- <title>SANE and driverless scanning</title>
+<section id="driverless-operation">
+ <title>Driverless scanning and printing</title>
<para>
- 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. <quote>Modern</quote> refers to devices that have been
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> 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

Post by Justin B Rye
+ to the model of the hardware, especially in the case of devices
marketed in the past five years or so.
</para>

Kind regards,
Andrei

[Justin B Rye]

Post by Andrei POPESCU

Post by Justin B Rye
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> are increasingly likely to be possible
+ without the need for any (often non-free) driver specific

... without the need for any driver (often non-free) specific

Post by Justin B Rye
+ 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.

[Hendrik Boom]

Post by Andrei POPESCU

Post by Justin B Rye
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"/>.
</para>
-<section id="sane-driverless-scanning">
- <title>SANE and driverless scanning</title>
+<section id="driverless-operation">
+ <title>Driverless scanning and printing</title>
<para>
- 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. <quote>Modern</quote> refers to devices that have been
+ Both printing with <literal>CUPS</literal> and scanning with
+ <literal>SANE</literal> are increasingly likely to be possible
+ without the need for any (often non-free) driver specific

... without the need for any driver (often non-free) specific

Or even

... without needing any driver (often non-free) specific

Post by Andrei POPESCU

Post by Justin B Rye
+ to the model of the hardware, especially in the case of devices
marketed in the past five years or so.
</para>

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

[Debian Bug Tracking System]

Your message dated Sat, 20 Mar 2021 20:43:14 +0100
with message-id <fe5cafca-e89d-5455-2a53-***@debian.org>
and subject line Re: Bug#966701: Driverless printing in buster via ipp-usb
has caused the Debian Bug report #966701,
regarding Driverless printing in bullseye via ipp-usb
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Miguel Figueiredo]

Hello,

Às 19:45 de 20/03/21, Debian Bug Tracking System escreveu:

[...]

po4a-updatepo is reporting:
Unexpected closing tag </sysitem> found. The main document may be wrong.

Maybe due to <systemitem></sysitem>

[Paul Gevers]

Hi,

Post by Miguel Figueiredo
[...]
Unexpected closing tag </sysitem> found. The main document may be wrong.
Maybe due to <systemitem></sysitem>

Thanks for reporting. I already fixed it.

Paul