Update references to the SANE standard

The authors have been added to SANE standard itself, pointers to the
standard now point to the published version and/or the project that
isnow used for its maintenance as appropriate.  References to input
files and installation locations have been removed.
merge-requests/350/head
Olaf Meeuwissen 2020-03-05 21:14:34 +09:00
rodzic 2db06a272e
commit d4d5d76e83
6 zmienionych plików z 12 dodań i 24 usunięć

Wyświetl plik

@ -1,7 +1,3 @@
Authors of the SANE standard:
Andreas Beck and David Mosberger
Backends: Backends:
abaton: David Huggins-Daines abaton: David Huggins-Daines

Wyświetl plik

@ -30,6 +30,9 @@ terms:
to implement SANE interface conforming applications or libraries in to implement SANE interface conforming applications or libraries in
any way he or she sees fit. any way he or she sees fit.
The standard is maintained at https://gitlab.com/sane-project/standard
and published at https://sane-project.gitlab.io/standard/.
Frequently Asked Questions about the SANE licensing: Frequently Asked Questions about the SANE licensing:
* Why don't you use the GNU LPGL ? * Why don't you use the GNU LPGL ?

Wyświetl plik

@ -34,8 +34,8 @@
#include "../include/sane/sanei_debug.h" #include "../include/sane/sanei_debug.h"
/* SANE backend operations, see Sane standard 1.04 documents (sane_dev.pdf) /* SANE backend operations, see SANE Standard for details
for details */ https://sane-project.gitlab.io/standard/ */
/* Init the KV-S1025 SANE backend. This function must be called before any other /* Init the KV-S1025 SANE backend. This function must be called before any other
SANE function can be called. */ SANE function can be called. */

Wyświetl plik

@ -12,6 +12,7 @@ GETTING STARTED
about it. You should mention that the code will be open-source, however. about it. You should mention that the code will be open-source, however.
* Read the SANE standard. * Read the SANE standard.
See https://sane-project.gitlab.io/standard/
* One approach is to write a stand-alone scanning program first. Debugging * One approach is to write a stand-alone scanning program first. Debugging
this program is usually easier than using the SANE libraries. However, keep this program is usually easier than using the SANE libraries. However, keep
@ -157,8 +158,6 @@ sane-backends/doc/
Used by doxygen to create the documentation of the sanei code. Used by doxygen to create the documentation of the sanei code.
* releases.txt: * releases.txt:
Explains how to make releases of sane-backends. Explains how to make releases of sane-backends.
* sane.tex, net.tex:
Contains the LaTeX source of the SANE standard.
* descriptions/ (directory) * descriptions/ (directory)
Contains the .desc files for every backend that is included into Contains the .desc files for every backend that is included into
sane-backends. sane-backends.

Wyświetl plik

@ -40,9 +40,8 @@ provides some means to manage one or more other backends.
.SH "SOFTWARE PACKAGES" .SH "SOFTWARE PACKAGES"
The package The package
.RB ` sane\-backends ' .RB ` sane\-backends '
contains a lot of backends, documentation (including the contains a lot of backends, documentation, networking support, and the
.B SANE command line frontend
standard), networking support, and the command line frontend
.RB ` scanimage '. .RB ` scanimage '.
The frontends The frontends
.RB ` xscanimage "', `" xcam "', and `" scanadf ' .RB ` xscanimage "', `" xcam "', and `" scanadf '
@ -65,7 +64,7 @@ A name with a number in parenthesis (e.g.
points to a manual page. In this case points to a manual page. In this case
.RB ` "man 5 sane\-dll" ' .RB ` "man 5 sane\-dll" '
will display the page. Entries like will display the page. Entries like
.RI ` @DOCDIR@/sane.tex ' .RI ` @DOCDIR@/README '
are references to text files that were copied to the are references to text files that were copied to the
.B SANE .B SANE
documentation directory documentation directory
@ -665,14 +664,7 @@ The
.B SANE .B SANE
standard defines the application programming interface (API) that is used to standard defines the application programming interface (API) that is used to
communicate between frontends and backends. It can be found at communicate between frontends and backends. It can be found at
.I @DOCDIR@/sane.ps .I http://sane\-project.gitlab.io/standard/ .
(if latex is installed on your system) and on the
.B SANE
website:
.I http://www.sane\-project.org/html/
(HTML), or
.I http://www.sane\-project.org/sane.ps
(Postscript).
.PP .PP
There is some more information for programmers in There is some more information for programmers in
.IR @DOCDIR@/backend\-writing.txt . .IR @DOCDIR@/backend\-writing.txt .
@ -712,7 +704,7 @@ support dynamic loading).
.TP .TP
.I @DOCDIR@/* .I @DOCDIR@/*
.B SANE .B SANE
documentation: The standard, READMEs, text files for backends etc. documentation: The READMEs, text files for backends etc.
.SH "PROBLEMS" .SH "PROBLEMS"
If your device isn't found but you know that it is supported, make If your device isn't found but you know that it is supported, make

Wyświetl plik

@ -65,9 +65,7 @@
* This documentation is far from complete. Any help is appreciated. * This documentation is far from complete. Any help is appreciated.
* *
* @section additional Additional documentation * @section additional Additional documentation
* - The SANE standard can be found at <a * - The <a href="https://sane-project.gitlab.io/standard/">SANE Standard</a>.
* href="http://www.sane-project.org/html/">the SANE webserver</a>,
* though the PostScript version produced from the source may be more recent.
* - Information on how to write a backend: <a * - Information on how to write a backend: <a
* href="../backend-writing.txt">backend-writing.txt</a>. * href="../backend-writing.txt">backend-writing.txt</a>.
* - General SANE documentation is on <a * - General SANE documentation is on <a