Oliver Schwartz writes:

> Olaf,
>
>  Would you mind adding your notes on firmware file names to the
>  snapscan.desc file so that everyone can see them? They can go in the
>  :comment.
>
>  If you can do so before 2020-08-22, please push your changes on the
>  release/1.0.31 branch.
>
>  Doh! I just stumbled upon #293 again which I had decided to take care
>  of for our upcoming 1.0.31 release (and promptly forgotten about until
>  looked at the milestone five minutes ago :-o).
>
>  https://gitlab.com/sane-project/backends/-/issues/293
>
>  I'll assign that to you in addition to myself.
>
> I’ve created a merge request for this issue and added the PHOTO suffix to 
> some of the epson scanner models so the names match the ones from the epson2 
> backend. The firmware file names have also been
> added. I’ll merge this if I don’t hear objections.
>
> I’m wondering though if the “unsupported” entries from the epson2 backend 
> should be removed.

They should stay because the device is *not* supported by the epson2
backend.  Or the entries should be removed completely.  Or the entries
should point to a backend that does support the device.

Especially with backends named after vendors, people tend to jump to the
conclusion that such a backend supports any hardware the vendor throw at
them.  As a result, they may only be looking at said backend's info to
decide whether or not their device is supported.  It is probably better
to point people to a supporting backend and/or make it very clear that
their device is not supported by the backend they're looking at.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join

Reply via email to