[sane-devel] SANE_NAME_SHADOW vs SANE_NAME_BLACK_LEVEL
Olaf Meeuwissen
paddy-hack at member.fsf.org
Thu Oct 15 09:59:50 BST 2020
Hi Alexander,
Alexander Pevzner writes:
> what is the difference between "shadow" and "black-level" options? And
> the same question regarding "highlight" vs "white-level" options.
Judging from their descriptions (in include/sane/saneopts.h), nothing
save for the command-line option names.
I think this is just a case of independently developed backends where
developer picked different option names for the same thing. A patch is
welcome but note that it would break backward compatibility for a bunch
of unmaintained backends if you simply drop the black- and white-level
options :-o
# The right way to go about this is *add* shadow and highlight to those
# backends, mark the black-level and white-level options deprecated and
# drop them in some release after the next.
FWIW, the version 2 draft of the standard documents shadow and highlight
at
https://sane-project.gitlab.io/standard/draft-2/api.html#shadow-option
https://sane-project.gitlab.io/standard/draft-2/api.html#highlight-option
so keeping that option is probably to be preferred.
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
More information about the sane-devel
mailing list