Changeset f051506c for pst/scanning


Ignore:
Timestamp:
11/12/2004 10:26:49 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
f6f2121
Parents:
ddfee75
Message:

Updated to SANE-1.0.15

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2929 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • pst/scanning/sane.xml

    rddfee75 rf051506c  
    33  <!ENTITY % general-entities SYSTEM "../../general.ent">
    44  %general-entities;
    5  
    6   <!ENTITY sane-download-http "http://gd.tuwien.ac.at/api/sane/sane-backends-&sane-version;/sane-backends-&sane-version;.tar.gz">
    7   <!ENTITY sane-download-ftp  "ftp://ftp.sane-project.org/pub/sane/sane-backends-&sane-version;/sane-backends-&sane-version;.tar.gz">
    8   <!ENTITY sane-size          "3.1 MB">
    9   <!ENTITY sane-buildsize     "42 MB">
    10   <!ENTITY sane-time          "1.77 SBU">
     5
     6  <!ENTITY sane-be-download-http "http://gd.tuwien.ac.at/api/sane/sane-backends-&sane-version;/sane-backends-&sane-version;.tar.gz">
     7  <!ENTITY sane-be-download-ftp  "ftp://ftp.sane-project.org/pub/sane/sane-backends-&sane-version;/sane-backends-&sane-version;.tar.gz">
     8  <!ENTITY sane-be-md5sum        "3b804f35cdfbc5ad2d201ffe078bbac9">
     9  <!ENTITY sane-be-size          "3.2 MB">
     10  <!ENTITY sane-be-buildsize     "50 MB">
     11  <!ENTITY sane-be-time          "1.26 SBU">
     12
     13  <!ENTITY sane-fe-version       "1.0.13">
     14  <!ENTITY sane-fe-download-http "http://gd.tuwien.ac.at/api/sane/sane-frontends-&sane-fe-version;/sane-frontends-&sane-fe-version;.tar.gz">
     15  <!ENTITY sane-fe-download-ftp  "ftp://ftp.sane-project.org/pub/sane/sane-frontends-&sane-fe-version;/sane-frontends-&sane-fe-version;.tar.gz">
     16  <!ENTITY sane-fe-md5sum        "2930626e627df49b45192a722cedc8a6">
     17  <!ENTITY sane-fe-size          "210 KB">
     18  <!ENTITY sane-fe-buildsize     "2.6 MB">
     19  <!ENTITY sane-fe-time          "0.09 SBU">
    1120]>
    1221
    … …  
    2029
    2130<sect2>
    22 <title>Introduction to <application><acronym>SANE</acronym></application></title>
    23 
    24 <para><acronym>SANE</acronym> is short for Scanner Access Now Easy.
    25 Scanner access, however, is far from easy, since every vendor has their own
    26 protocols. The only known protocol that should bring some unity into this
    27 chaos is the TWAIN interface, but this is too imprecise to
    28 allow a stable scanning framework. Therefore, <acronym>SANE</acronym> comes
    29 with its own protocol, so the vendor drivers can't be used.</para>
    30                                                                                
    31 <para><acronym>SANE</acronym> is split into back ends and front ends. The
    32 back ends are drivers for the supported scanners. The front ends are user
    33 interfaces to access the backends.</para>
    34 
    35 <sect3><title>Package information</title>
     31<title>Introduction to
     32<application><acronym>SANE</acronym></application></title>
     33
     34<para><application><acronym>SANE</acronym></application> is short for Scanner
     35Access Now Easy. Scanner access, however, is far from easy, since every vendor
     36has their own protocols. The only known protocol that should bring some unity
     37into this chaos is the TWAIN interface, but this is too imprecise to allow a
     38stable scanning framework. Therefore, <acronym>SANE</acronym> comes with its
     39own protocol, and the vendor drivers can't be used.</para>
     40
     41<para><acronym>SANE</acronym> is split into back ends and front ends. The back
     42ends are drivers for the supported scanners and cameras. The front ends are
     43user interfaces to access the backends.</para>
     44
     45<sect3><title>Back ends package information</title>
    3646<itemizedlist spacing='compact'>
    3747<listitem><para>Download (HTTP): <ulink
    38 url="&sane-download-http;"/></para></listitem>
     48url="&sane-be-download-http;"/></para></listitem>
    3949<listitem><para>Download (FTP): <ulink
    40 url="&sane-download-ftp;"/></para></listitem>
    41 <listitem><para>Download size: &sane-size;</para></listitem>
    42 <listitem><para>Estimated Disk space required: &sane-buildsize;</para></listitem>
    43 <listitem><para>Estimated build time: &sane-time;</para></listitem></itemizedlist>
    44 </sect3>
    45 
    46 <sect3><title>Additional downloads</title>
     50url="&sane-be-download-ftp;"/></para></listitem>
     51<listitem><para>MD5 sum: &sane-be-md5sum;</para></listitem>
     52<listitem><para>Download size: &sane-be-size;</para></listitem>
     53<listitem><para>Estimated disk space required:
     54&sane-be-buildsize;</para></listitem>
     55<listitem><para>Estimated build time:
     56&sane-be-time;</para></listitem></itemizedlist>
     57</sect3>
     58
     59<sect3><title>Front ends package information</title>
    4760<itemizedlist spacing='compact'>
    48 <listitem><para>Front ends: <ulink
    49 url="ftp://ftp.sane-project.org/pub/sane/sane-frontends-1.0.12/sane-frontends-1.0.12.tar.gz"/></para></listitem>
    50 </itemizedlist>
    51 </sect3>
    52                                                                                
    53 <sect3><title><application><acronym>SANE</acronym></application> dependencies</title>
    54 <sect4><title>Optional</title>
    55 <para><xref linkend="libusb"/>,
    56 <ulink url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>,
    57 <ulink url="http://www.gphoto.org/">gPhoto2</ulink>,
    58 X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>), <xref linkend="GTK2"/> and <xref
    59 linkend="gimp"/></para></sect4>
    60 </sect3>
    61 
    62 </sect2>
    63 
    64 <sect2>
    65 <title>Installation of <application><acronym>SANE</acronym></application></title>
     61<listitem><para>Download (HTTP): <ulink
     62url="&sane-fe-download-http;"/></para></listitem>
     63<listitem><para>Download (FTP): <ulink
     64url="&sane-fe-download-ftp;"/></para></listitem>
     65<listitem><para>MD5 sum: &sane-fe-md5sum;</para></listitem>
     66<listitem><para>Download size: &sane-fe-size;</para></listitem>
     67<listitem><para>Estimated disk space required:
     68&sane-fe-buildsize;</para></listitem>
     69<listitem><para>Estimated build time:
     70&sane-fe-time;</para></listitem></itemizedlist>
     71</sect3>
     72
     73<sect3><title><application><acronym>SANE</acronym></application>
     74dependencies</title>
     75<sect4><title>Optional (back ends)</title>
     76<para><xref linkend="libjpeg"/>,
     77<xref linkend="libusb"/>,
     78<ulink url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>,
     79<ulink url="http://www.gphoto.org/">gPhoto2</ulink>
     80(requires <ulink url="http://www.gphoto.org/">libgphoto2</ulink>) and
     81<xref linkend="pst-typesetting-tex"/></para>
     82</sect4>
     83
     84<sect4><title>Optional (front ends)</title>
     85<para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>),
     86<xref linkend="GTK2"/> and
     87<xref linkend="gimp"/></para>
     88</sect4>
     89</sect3>
     90
     91</sect2>
     92
     93<sect2>
     94<title>Installation of
     95<application><acronym>SANE</acronym></application></title>
    6696
    6797<sect3><title>Preparing your system for scanner access</title>
    6898<para>To access your scanner, you will probably need the related kernel
    69 drivers. A <acronym>SCSI</acronym> scanner will need <acronym>SCSI</acronym>
    70  drivers, a parallel port scanner needs parallel port support (you should use
    71 enhanced <acronym>EPP</acronym> modes) and an <acronym>USB</acronym> scanner
    72 will need the <acronym>USB</acronym> scanner module and a <acronym>SCSI
    73 </acronym> system for emulation. Be sure that you have got the necessary
    74 devices to access the drivers.</para>
    75 </sect3>
    76 
    77 <sect3><title>Installation of <application><acronym>SANE</acronym></application> backends</title>
    78 
    79 <para>Install <application><acronym>SANE</acronym></application> backends by
     99drivers or additional support packages (<application>libusb</application>).
     100A <acronym>SCSI</acronym> scanner will need <acronym>SCSI</acronym>
     101drivers, a parallel port scanner needs parallel port support (you should use
     102enhanced <acronym>EPP</acronym> modes) and a <acronym>USB</acronym> scanner
     103will need the <application>libusb</application> package and a
     104<acronym>SCSI</acronym> system for emulation. Be sure that you have got the
     105necessary drivers to access the devices.</para>
     106</sect3>
     107
     108<sect3><title>Installation of
     109<application><acronym>SANE</acronym></application> back ends</title>
     110
     111<para>Install <application><acronym>SANE</acronym></application>-backends by
    80112running the following commands:</para>
    81113
    … …  
    83115make &amp;&amp;
    84116make install</command></userinput></screen>
    85 
    86 </sect3>
    87 
    88 <sect3><title>Installation of <application><acronym>SANE</acronym></application> front ends</title>
    89 
    90 <para>To install <application><acronym>SANE</acronym></application> front ends, use the following
    91 commands:</para>
     117</sect3>
     118
     119<sect3><title>Installation of
     120<application><acronym>SANE</acronym></application> front ends</title>
     121
     122<para>The <application><acronym>SANE</acronym></application>-frontends package
     123includes the graphical frontends <command>xscanimage</command> and
     124<command>xcam</command>, and a command-line frontend
     125<command>scanadf</command>. You don't need this package if you intend to use
     126one of the more advanced graphical frontends like <xref linkend="xsane"/>. For
     127a list of frontend packages, see
     128<ulink url="http://www.sane-project.org/sane-frontends.html"/>.</para>
     129
     130<para>To install <application><acronym>SANE</acronym></application>-frontends,
     131use the following commands:</para>
    92132
    93133<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
    … …  
    95135make install</command></userinput></screen>
    96136
    97 </sect3>
    98 
    99 </sect2>
    100 
    101 <sect2>
    102 <title>Installation command explanations</title>
     137<para>If <application>GIMP</application> was linked into the build and you
     138wish <application>GIMP</application> to use <command>xscanimage</command> as
     139a scanning plugin, issue the following command:</para>
     140
     141<screen><userinput><command>ln -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins</command></userinput></screen>
     142</sect3>
     143
     144</sect2>
     145
     146<sect2>
     147<title>Command explanations</title>
    103148
    104149<para><parameter>--sysconfdir=/etc</parameter>: This switch installs the
    … …  
    109154
    110155<sect2>
     156<title>Configuring <application><acronym>SANE</acronym></application></title>
     157
     158<sect3><title>Config files</title>
     159<para><filename>/etc/sane.d/*.conf</filename></para>
     160</sect3>
     161
     162<sect3><title>Configuration information</title>
     163<sect4><title>Backend configuration</title>
     164<para>The backend configuration files are located in
     165<filename class='directory'>/etc/sane.d</filename>. Information for configuring
     166the various backends can be found by using the man(5) page for the desired
     167backend. Run <command>man sane-<replaceable>[backend]</replaceable></command>,
     168substituting the desired backend.</para>
     169</sect4>
     170
     171<sect4><title>General information</title>
     172<para>For general information about configuring and using
     173<application><acronym>SANE</acronym></application>, see
     174<command>man sane</command>. Linux-2.6.x brings some special issues into the
     175picture. See <ulink url="http://www.sane-project.org/README.linux"/> for
     176information about using <application><acronym>SANE</acronym></application>
     177with the Linux-2.6.x kernel. For information about <acronym>USB</acronym>
     178scanning devices, run <command>man sane-usb</command>. For information about
     179<acronym>SCSI</acronym> devices, run <command>man sane-scsi</command>.</para>
     180</sect4>
     181
     182<sect4><title>Configuration and setup of the <command>saned</command>
     183daemon</title>
     184<para>The <command>saned</command> daemon is not meant to be used for untrusted
     185clients. You should provide <application>tcpwrapper</application> and/or
     186firewall protection to insure only trusted clients access the daemon. Due to
     187the complex security requirements to insure only trusted clients access the
     188daemon, <acronym>BLFS</acronym> does not provide a bootscript for the
     189<command>saned</command> daemon. If you desire to run the daemon, ensure you
     190provide adequate security and start the daemon manually, or create your own
     191bootscript to start the daemon at system boot time. Some good information for
     192setting up and securing the <command>saned</command> daemon can be found at
     193<ulink url="http://penguin-breeder.org/sane/saned/"/>.</para>
     194</sect4>
     195</sect3>
     196
     197</sect2>
     198
     199<sect2>
    111200<title>Contents</title>
    112201
    113202<sect3><title>Back ends:</title>
    114 <para>See <ulink url="http://www.sane-project.org/sane-supported-devices.html"/>
    115 for a list of available backends.</para>
     203<para>The <application><acronym>SANE</acronym></application>-backends package
     204contains
     205<command>gamma4scanimage</command>,
     206<command>sane-config</command>,
     207<command>saned</command>,
     208<command>sane-find-scanner</command>,
     209<command>scanimage</command>,
     210the <filename class='libraryfile'>libsane</filename> library and
     211numerous scanner backend modules. See
     212<ulink url="http://www.sane-project.org/sane-supported-devices.html"/>
     213for a list of supported backends.</para>
    116214</sect3>
    117215
    118216<sect3><title>Front ends:</title>
    119 <para><command>scanimage</command>: Command line interface for
    120 scanning.</para>
    121 <para><command>xscanimage</command>: Graphical user interface for
    122 scanning.</para>
    123 <para><command>gimp-plugin</command>: xscanimage as
    124 <application><acronym>GIMP</acronym></application> plugin.</para>
    125 </sect3>
     217<para>The <application><acronym>SANE</acronym></application>-frontends package
     218contains
     219<command>scanadf</command>,
     220<command>xcam</command>,
     221<command>xscanimage</command> and a <application>GIMP</application> plugin
     222imbedded in <command>xscanimage</command>.</para>
     223</sect3>
     224
     225</sect2>
     226
     227<sect2>
     228<title>Description</title>
     229
     230<sect3><title>gamma4scanimage</title>
     231<para><command>gamma4scanimage</command> creates a gamma table in the format
     232expected by <command>scanimage</command>.</para></sect3>
     233
     234<sect3><title>sane-config</title>
     235<para><command>sane-config</command> is a tool used to determine the compiler
     236and linker flags that should be used to compile and link
     237<application><acronym>SANE</acronym></application>.</para></sect3>
     238
     239<sect3><title>saned</title>
     240<para><command>saned</command> is the
     241<application><acronym>SANE</acronym></application> daemon that allows remote
     242clients to access image acquisition devices available on the local
     243host.</para></sect3>
     244
     245<sect3><title>sane-find-scanner</title>
     246<para><command>sane-find-scanner</command> is a command-line tool to find
     247<acronym>SCSI</acronym> and <acronym>USB</acronym> scanners and determine
     248their device files. Its primary aim is to make sure that scanners can be
     249detected by <application><acronym>SANE</acronym></application>
     250backends.</para></sect3>
     251
     252<sect3><title>scanadf</title>
     253<para><command>scanadf</command> is a command-line interface to control image
     254acquisition devices which are equipped with an automatic document feeder
     255(<acronym>ADF</acronym>).</para></sect3>
     256
     257<sect3><title>scanimage</title>
     258<para><command>scanimage</command> is a command line interface for scanning
     259from image acquisition devices such as flatbed scanners or cameras. It is
     260also used to list the available backend devices.</para></sect3>
     261
     262<sect3><title>xcam</title>
     263<para><command>xcam</command> is a graphical camera front end for
     264<application><acronym>SANE</acronym></application>.</para></sect3>
     265
     266<sect3><title>xscanimage</title>
     267<para><command>xscanimage</command> is a graphical user interface for
     268scanning.</para></sect3>
    126269
    127270</sect2>
Note: See TracChangeset for help on using the changeset viewer.