mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-02-07 09:37:17 +08:00
7008de18ae
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@557 af4574ff-66df-0310-9fd7-8a98e5e911e0
26 lines
1.2 KiB
XML
26 lines
1.2 KiB
XML
<sect2>
|
|
<title>Introduction to sane</title>
|
|
|
|
<screen>Required:
|
|
Download location (HTTP): <ulink url="&sane-download-http;"/>
|
|
Download location (FTP): <ulink url="&sane-be-download-ftp;"/>
|
|
<ulink url="&sane-fe-download-ftp;"/>
|
|
Version used: &sane-version;
|
|
Package size: &sane-be-size; (Backends), &sane-fe-size; (Frontends)
|
|
Estimated Disk space required: &sane-be-buildsize; (Backends), &sane-fe-buildsize; (Frontends)</screen>
|
|
|
|
<para>SANE is short for Scanner Access Now Easy. Alas, scanner access is
|
|
not really easy, since every vendor has own protocols. The only known
|
|
protocol that should bring some unity into this chaos is the TWAIN interface,
|
|
but this is too unprecise to allow a stable scanning framework. Therefore,
|
|
SANE comes with its own protocol, so the vendor drivers can't be used.</para>
|
|
|
|
<para>SANE is split into backends and frontends. The backends are drivers
|
|
for the supported scanners. The frontends are user interfaces to access the
|
|
backends.</para>
|
|
|
|
<screen>The frontends will utilize:
|
|
<xref linkend="xfree86"/>, <xref linkend="GTK"/>, <xref linkend="gimp"/></screen>
|
|
|
|
</sect2>
|