Ignore:
Timestamp:
09/20/2003 02:02:43 PM (18 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, ken/refactor-virt, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
616ce29
Parents:
d4f610c
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pst/scanning/sane/sane-intro.xml

    rd4f610c rec3c746  
    11<sect2>
    2 <title>Introduction to sane</title>
     2<title>Introduction to <application>sane</application></title>
    33
    4 <screen>Download location (HTTP):       <ulink url="&sane-download-http;"/>
    5 Download location (FTP):        <ulink url="&sane-be-download-ftp;"/>
    6 Download location (FTP):        <ulink url="&sane-fe-download-ftp;"/>
    7 Version used:                   &sane-version;
    8 Package size:                   &sane-be-size; (Backends), &sane-fe-size; (Frontends)
    9 Estimated Disk space required:  &sane-be-buildsize; (Backends), &sane-fe-buildsize; (Frontends)</screen>
     4<para><acronym>SANE</acronym> is short an acronym Scanner Access Now Easy.
     5Scanner access, however, is far from easy, since every vendor has own
     6protocols. The only known protocol that should bring some unity into this
     7chaos is the <acronym>TWAIN</acronym> interface, but this is too imprecise to
     8allow a stable scanning framework. Therefore, <acronym>SANE</acronym> comes
     9with 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
     12backends are drivers for the supported scanners. The frontends are user
     13interfaces to access the backends.</para>
    1014
    11 <para>SANE is short for Scanner Access Now Easy. Alas, scanner access is
    12 not really easy, since every vendor has own protocols. The only known
    13 protocol that should bring some unity into this chaos is the TWAIN interface,
    14 but this is too imprecise to allow a stable scanning framework. Therefore,
    15 SANE comes with its own protocol, so the vendor drivers can't be used.</para>
     15<sect3><title>Package information</title>
     16<itemizedlist spacing='compact'>
     17<listitem><para>Download (HTTP): <ulink
     18url="&sane-download-http;"/></para></listitem>
     19<listitem><para>Download (FTP): <ulink
     20url="&sane-be-download-ftp;"/></para></listitem>
     21<listitem><para>Download (FTP): <ulink
     22url="&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
     34linkend="gimp"/></para></sect4>
     35</sect3>
    1636
    17 <para>SANE is split into backends and frontends. The backends are drivers
    18 for the supported scanners. The frontends are user interfaces to access the
    19 backends.</para>
    20 
    21 <screen>SANE will utilize:
    22 <xref linkend="xfree86"/>, <xref linkend="GTK"/> and <xref linkend="gimp"/></screen>
    2337
    2438</sect2>
Note: See TracChangeset for help on using the changeset viewer.