1 | <sect2>
|
---|
2 | <title>Introduction to <application>sane</application></title>
|
---|
3 |
|
---|
4 | <para><acronym>SANE</acronym> is short for Scanner Access Now Easy.
|
---|
5 | Scanner access, however, is far from easy, since every vendor has their own
|
---|
6 | protocols. The only known protocol that should bring some unity into this
|
---|
7 | chaos is the <acronym>TWAIN</acronym> interface, but this is too imprecise to
|
---|
8 | allow a stable scanning framework. Therefore, <acronym>SANE</acronym> comes
|
---|
9 | with its own protocol, so the vendor drivers can't be used.</para>
|
---|
10 |
|
---|
11 | <para><acronym>SANE</acronym> is split into backends and frontends. The
|
---|
12 | backends are drivers for the supported scanners. The frontends are user
|
---|
13 | interfaces to access the backends.</para>
|
---|
14 |
|
---|
15 | <sect3><title>Package information</title>
|
---|
16 | <itemizedlist spacing='compact'>
|
---|
17 | <listitem><para>Download (HTTP): <ulink
|
---|
18 | url="&sane-download-http;"/></para></listitem>
|
---|
19 | <listitem><para>Download (FTP): <ulink
|
---|
20 | url="&sane-be-download-ftp;"/></para></listitem>
|
---|
21 | <listitem><para>Download (FTP): <ulink
|
---|
22 | url="&sane-fe-download-ftp;"/></para></listitem>
|
---|
23 | <listitem><para>Download size: &sane-be-size; (Backends), &sane-fe-size;
|
---|
24 | (Frontends)</para></listitem>
|
---|
25 | <listitem><para>Estimated Disk space required:
|
---|
26 | &sane-be-buildsize; (Backends), &sane-fe-buildsize; (Frontends)</para></listitem>
|
---|
27 | <listitem><para>Estimated build time:
|
---|
28 | &sane-time;</para></listitem></itemizedlist>
|
---|
29 | </sect3>
|
---|
30 |
|
---|
31 | <sect3><title><application>sane</application> dependencies</title>
|
---|
32 | <sect4><title>Optional</title>
|
---|
33 | <para><xref linkend="xfree86"/>, <xref linkend="GTK"/> and <xref
|
---|
34 | linkend="gimp"/></para></sect4>
|
---|
35 | </sect3>
|
---|
36 |
|
---|
37 |
|
---|
38 | </sect2>
|
---|