Hello Brian,
thanks for your hint. Like Olaf Meeuwissen I am of the opinion that sane-airscan is best integrated into sane. This has been communicated to the upstream author on 11.07.2020. Unfortunately this is not yet done and, what is even more important for me, the mentioned bugs are not yet solved. I refer to [1]. So I think that I do not set sane-airscan as recommended package at the moment. [1] https://gitlab.com/sane-project/backends/-/issues/202 CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key : 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype: joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. Am Sonntag, den 04.10.2020, 13:02 +0100 schrieb Brian Potkin: > Package: libsane1 > Version: 1.0.31-2 > Severity: wishlist > > > > I wonder whether the sane-airscan backend would be a useful addition > for a user to have by default in addition to to the sane-escl backend? > > Both backends can scan via the eSCL protocol. However, sane-airscan > also uses the WSD protocol, which is often found to be available on > early modern devices that do not offer eSCL. This brings many more > devices within the orbit of SANE. > > Also, sane-airscan is a competent backend in its own right and is well- > supported by its author. > > Regards, > > Brian.
signature.asc
Description: This is a digitally signed message part
