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

<sect2>
<title>Introduction to <application><acronym>SANE</acronym></application></title>

<para><acronym>SANE</acronym> is short for Scanner Access Now Easy. 
Scanner access, however, is far from easy, since every vendor has their own 
protocols. The only known protocol that should bring some unity into this 
chaos is the TWAIN 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 back ends and front ends. The 
back ends are drivers for the supported scanners. The front ends are user 
interfaces to access the backends.</para>

<sect3><title>Package information</title>
<itemizedlist spacing='compact'>
<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; (Back ends), &sane-fe-size;
(Front ends)</para></listitem>
<listitem><para>Estimated Disk space required:
&sane-be-buildsize; (Back ends), &sane-fe-buildsize; (Front ends)</para></listitem>
<listitem><para>Estimated build time:
&sane-be-time; (Back ends), &sane-fe-time; (Front ends)</para></listitem></itemizedlist>
</sect3>
                                                                                
<sect3><title><application><acronym>SANE</acronym></application> dependencies</title>
<sect4><title>Optional</title>
<para><xref linkend="xfree86"/>, <xref linkend="GTK"/> and <xref
linkend="gimp"/></para></sect4>
</sect3>

</sect2>