glfs/pst/scanning/sane/sane-intro.xml

<sect2>
<title>Introduction to <application>sane</application></title>

<para><acronym>SANE</acronym> is short an acronym Scanner Access Now Easy. 
Scanner access, however, is far from easy, since every vendor has own 
protocols. The only known protocol that should bring some unity into this 
chaos is the <acronym>TWAIN</acronym> interface, but this is too imprecise to 
allow a stable scanning framework. Therefore, <acronym>SANE</acronym> comes 
with its own protocol, so the vendor drivers can't be used.</para>
                                                                                
<para><acronym>SANE</acronym> is split into backends and frontends. The 
backends are drivers for the supported scanners. The frontends are user 
interfaces to access the backends.</para>

<sect3><title>Package information</title>
<itemizedlist spacing='compact'>
<listitem><para>Download (HTTP): <ulink
url="&sane-download-http;"/></para></listitem>
<listitem><para>Download (FTP): <ulink
url="&sane-be-download-ftp;"/></para></listitem>
<listitem><para>Download (FTP): <ulink
url="&sane-fe-download-ftp;"/></para></listitem>
<listitem><para>Download size: &sane-be-size; (Backends), &sane-fe-size;
(Frontends)</para></listitem>
<listitem><para>Estimated Disk space required:
&sane-be-buildsize; (Backends), &sane-fe-buildsize; (Frontends)</para></listitem>
<listitem><para>Estimated build time:
&sane-time;</para></listitem></itemizedlist>
</sect3>
                                                                                
<sect3><title><application>sane</application> dependencies</title>
<sect4><title>Optional</title>
<para><xref linkend="xfree86"/>, <xref linkend="GTK"/> and <xref
linkend="gimp"/></para></sect4>
</sect3>


</sect2>