glfs/pst/scanning/sane/sane-intro.xml
Larry Lawrence ec3c746578 updated to sane-1.0.12, xsane-0.91 and updated xpdf intro
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1129 af4574ff-66df-0310-9fd7-8a98e5e911e0
2003-09-20 14:02:43 +00:00

39 lines
1.7 KiB
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>