Changeset fa3edfef for pst/scanning


Ignore:
Timestamp:
03/25/2020 12:06:24 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
81a73ed8
Parents:
47274444
Message:

Format pst

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

Location:
pst/scanning
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • pst/scanning/sane.xml

    r47274444 rfa3edfef  
    3737    <title>Introduction to SANE</title>
    3838
    39     <para><application>SANE</application> is short for Scanner Access Now Easy.
    40     Scanner access, however, is far from easy, since every vendor has their own
    41     protocols. The only known protocol that should bring some unity into this
    42     chaos is the TWAIN interface, but this is too imprecise to allow a stable
    43     scanning framework. Therefore, <application>SANE</application> comes with
    44     its own protocol, and the vendor drivers can't be used.</para>
    45 
    46     <para><application>SANE</application> is split into back ends and front
    47     ends. The back ends are drivers for the supported scanners and cameras. The
    48     front ends are user interfaces to access the backends.</para>
     39    <para>
     40      <application>SANE</application> is short for Scanner Access Now Easy.
     41      Scanner access, however, is far from easy, since every vendor has their
     42      own protocols. The only known protocol that should bring some unity into
     43      this chaos is the TWAIN interface, but this is too imprecise to allow a
     44      stable scanning framework. Therefore, <application>SANE</application>
     45      comes with its own protocol, and the vendor drivers can't be used.
     46    </para>
     47
     48    <para>
     49      <application>SANE</application> is split into back ends and front ends.
     50      The back ends are drivers for the supported scanners and cameras. The
     51      front ends are user interfaces to access the backends.
     52    </para>
    4953
    5054    &lfs91_checked;
    … …  
    5357    <itemizedlist spacing='compact'>
    5458      <listitem>
    55         <para>Download (HTTP): <ulink url="&sane-be-download-http;"/></para>
    56       </listitem>
    57       <listitem>
    58         <para>Download (FTP): <ulink url="&sane-be-download-ftp;"/></para>
    59       </listitem>
    60       <listitem>
    61         <para>Download MD5 sum: &sane-be-md5sum;</para>
    62       </listitem>
    63       <listitem>
    64         <para>Download size: &sane-be-size;</para>
    65       </listitem>
    66       <listitem>
    67         <para>Estimated disk space required: &sane-be-buildsize;</para>
    68       </listitem>
    69       <listitem>
    70         <para>Estimated build time: &sane-be-time;</para>
     59        <para>
     60          Download (HTTP): <ulink url="&sane-be-download-http;"/>
     61        </para>
     62      </listitem>
     63      <listitem>
     64        <para>
     65          Download (FTP): <ulink url="&sane-be-download-ftp;"/>
     66        </para>
     67      </listitem>
     68      <listitem>
     69        <para>
     70          Download MD5 sum: &sane-be-md5sum;
     71        </para>
     72      </listitem>
     73      <listitem>
     74        <para>
     75          Download size: &sane-be-size;
     76        </para>
     77      </listitem>
     78      <listitem>
     79        <para>
     80          Estimated disk space required: &sane-be-buildsize;
     81        </para>
     82      </listitem>
     83      <listitem>
     84        <para>
     85          Estimated build time: &sane-be-time;
     86        </para>
    7187      </listitem>
    7288    </itemizedlist>
    … …  
    7591    <itemizedlist spacing='compact'>
    7692      <listitem>
    77         <para>Download (HTTP): <ulink url="&sane-fe-download-http;"/></para>
    78       </listitem>
    79       <listitem>
    80         <para>Download (FTP): <ulink url="&sane-fe-download-ftp;"/></para>
    81       </listitem>
    82       <listitem>
    83         <para>Downlaod MD5 sum: &sane-fe-md5sum;</para>
    84       </listitem>
    85       <listitem>
    86         <para>Download size: &sane-fe-size;</para>
    87       </listitem>
    88       <listitem>
    89         <para>Estimated disk space required: &sane-fe-buildsize;</para>
    90       </listitem>
    91       <listitem>
    92         <para>Estimated build time: &sane-fe-time;</para>
     93        <para>
     94          Download (HTTP): <ulink url="&sane-fe-download-http;"/>
     95        </para>
     96      </listitem>
     97      <listitem>
     98        <para>
     99          Download (FTP): <ulink url="&sane-fe-download-ftp;"/>
     100        </para>
     101      </listitem>
     102      <listitem>
     103        <para>
     104          Downlaod MD5 sum: &sane-fe-md5sum;
     105        </para>
     106      </listitem>
     107      <listitem>
     108        <para>
     109          Download size: &sane-fe-size;
     110        </para>
     111      </listitem>
     112      <listitem>
     113        <para>
     114          Estimated disk space required: &sane-fe-buildsize;
     115        </para>
     116      </listitem>
     117      <listitem>
     118        <para>
     119          Estimated build time: &sane-fe-time;
     120        </para>
    93121      </listitem>
    94122    </itemizedlist>
    … …  
    129157    </indexterm>
    130158
    131     <para>To access your scanner, you will probably need the related kernel
    132     drivers and/or additional support packages. A SCSI scanner will need SCSI
    133     drivers, a parallel port scanner needs parallel port support (you should
    134     use enhanced EPP modes) and perhaps <ulink
    135     url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>, and a USB
    136     scanner will need the <xref linkend="libusb"/> package. For HP devices, you
    137     may need <ulink
    138     url="http://sourceforge.net/projects/hplip/files/hplip/">hplip</ulink>.
    139     Ensure you have the necessary drivers properly configured to access
    140     the devices.</para>
     159    <para>
     160      To access your scanner, you will probably need the related kernel
     161      drivers and/or additional support packages. A SCSI scanner will need SCSI
     162      drivers, a parallel port scanner needs parallel port support (you should
     163      use enhanced EPP modes) and perhaps <ulink
     164      url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>, and a USB
     165      scanner will need the <xref linkend="libusb"/> package. For HP devices,
     166      you may need <ulink
     167      url="http://sourceforge.net/projects/hplip/files/hplip/">hplip</ulink>.
     168      Ensure you have the necessary drivers properly configured to access
     169      the devices.
     170    </para>
    141171
    142172  </sect2>
    … …  
    148178      <title>Installation of SANE Back Ends</title>
    149179
    150       <para>The <application>SANE</application> daemon should run with its own
    151       group.  Create this group by issuing the following commands as the
    152       <systemitem class="username">root</systemitem> user:</para>
     180      <para>
     181        The <application>SANE</application> daemon should run with its own
     182        group.  Create this group by issuing the following commands as the
     183        <systemitem class="username">root</systemitem> user:
     184      </para>
    153185
    154186<screen role="root"><userinput>groupadd -g 70 scanner</userinput></screen>
    … …  
    167199      </note>
    168200
    169       <para>For a USB scanner, if you are linking to <xref linkend="libusb"/>,
    170       include the configure switch --enable-libusb_1_0. Install
    171       <application>SANE</application>-backends by running the following
    172       commands:</para>
     201      <para>
     202        For a USB scanner, if you are linking to <xref linkend="libusb"/>,
     203        include the configure switch --enable-libusb_1_0. Install
     204        <application>SANE</application>-backends by running the following
     205        commands:
     206      </para>
    173207
    174208<screen><userinput>sg scanner -c "                  \
    … …  
    180214make</userinput></screen>
    181215
    182       <para>To test the results, issue: <command>make check</command>.</para>
    183 
    184       <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     216      <para>
     217        To test the results, issue: <command>make check</command>.
     218      </para>
     219
     220      <para>
     221        Now, as the <systemitem class="username">root</systemitem> user:
     222      </para>
    185223
    186224<screen role="root"><userinput>make install                                         &amp;&amp;
    … …  
    189227chgrp -v scanner  /var/lock/sane</userinput></screen>
    190228
    191       <para>With the scanner on, run <command>scanimage -L</command> and the
    192       name and location of the device should appear. Of course, you need the
    193       device drivers configured, in order to run this test.</para>
     229      <para>
     230        With the scanner on, run <command>scanimage -L</command> and the
     231        name and location of the device should appear. Of course, you need the
     232        device drivers configured, in order to run this test.
     233      </para>
    194234
    195235    </sect3>
    … …  
    198238      <title>Installation of SANE Front Ends</title>
    199239
    200       <para>The <application>SANE</application>-frontends package
    201       includes the graphical frontends <command>xscanimage</command> and
    202       <command>xcam</command>, and a command-line frontend
    203       <command>scanadf</command>. You don't need this package if you intend
    204       to use one of the more advanced graphical frontends like
    205       <xref linkend="xsane"/>. For a list of frontend packages, see
    206       <ulink url="http://www.sane-project.org/sane-frontends.html"/>.</para>
    207 
    208       <para>To install <application>SANE</application>-frontends,
    209       use the following commands:</para>
     240      <para>
     241        The <application>SANE</application>-frontends package
     242        includes the graphical frontends <command>xscanimage</command> and
     243        <command>xcam</command>, and a command-line frontend
     244        <command>scanadf</command>. You don't need this package if you intend
     245        to use one of the more advanced graphical frontends like
     246        <xref linkend="xsane"/>. For a list of frontend packages, see
     247        <ulink url="http://www.sane-project.org/sane-frontends.html"/>.
     248      </para>
     249
     250      <para>
     251        To install <application>SANE</application>-frontends,
     252        use the following commands:
     253      </para>
    210254
    211255<screen><userinput>tar -xf ../sane-frontends-&sane-fe-version;.tar.gz &amp;&amp;
    … …  
    216260make</userinput></screen>
    217261
    218       <para>This package does not come with a test suite.</para>
    219 
    220       <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     262      <para>
     263        This package does not come with a test suite.
     264      </para>
     265
     266      <para>
     267        Now, as the <systemitem class="username">root</systemitem> user:
     268      </para>
    221269
    222270<screen role="root"><userinput>make install &amp;&amp;
    … …  
    224272    /usr/share/sane</userinput></screen>
    225273
    226       <para>If <application>GIMP</application> was linked into the build and
    227       you wish <application>GIMP</application> to use
    228       <command>xscanimage</command> as a scanning plugin, issue the following
    229       command as the <systemitem class="username">root</systemitem> user:</para>
     274      <para>
     275        If <application>GIMP</application> was linked into the build and
     276        you wish <application>GIMP</application> to use
     277        <command>xscanimage</command> as a scanning plugin, issue the following
     278        command as the <systemitem class="username">root</systemitem> user:
     279      </para>
    230280
    231281<screen role="root"><userinput>ln -v -s ../../../../bin/xscanimage /usr/lib/gimp/2.0/plug-ins</userinput></screen>
    … …  
    254304    </para>
    255305
    256     <para><parameter>--sysconfdir=/etc</parameter>: This switch installs the
    257     configuration files in <filename class="directory">/etc/sane.d</filename>
    258     instead of <filename class="directory">/usr/etc/sane.d</filename>.</para>
    259 
    260     <para><parameter>--with-group=scanner</parameter>: This parameter causes
    261     the directory created for the locking files to be group owned by the
    262     <systemitem class="groupname">scanner</systemitem> group instead of the
    263     default <systemitem class="groupname">uucp</systemitem> group.</para>
    264 
    265     <para><command>exit</command>: This command is used to exit the shell
    266     created by the <command>su</command> command.</para>
     306    <para>
     307      <parameter>--sysconfdir=/etc</parameter>: This switch installs the
     308      configuration files in <filename class="directory">/etc/sane.d</filename>
     309      instead of <filename class="directory">/usr/etc/sane.d</filename>.
     310    </para>
     311
     312    <para>
     313      <parameter>--with-group=scanner</parameter>: This parameter causes
     314      the directory created for the locking files to be group owned by the
     315      <systemitem class="groupname">scanner</systemitem> group instead of the
     316      default <systemitem class="groupname">uucp</systemitem> group.
     317    </para>
     318
     319    <para>
     320      <command>exit</command>: This command is used to exit the shell
     321      created by the <command>su</command> command.
     322    </para>
    267323  </sect2>
    268324
    … …  
    273329      <title>Config Files</title>
    274330
    275       <para><filename>/etc/sane.d/*.conf</filename></para>
     331      <para>
     332        <filename>/etc/sane.d/*.conf</filename>
     333      </para>
    276334
    277335      <indexterm zone="sane sane-config">
    … …  
    287345        <title>Backend Configuration</title>
    288346
    289         <para>The backend configuration files are located in
    290         <filename class='directory'>/etc/sane.d</filename>. Information
    291         for configuring the various backends can be found by using the man(5)
    292         page for the desired backend. Run
    293         <command>man sane-<replaceable>&lt;backend&gt;</replaceable></command>,
    294         substituting the desired backend.</para>
    295 
    296         <para>Add any desired users to the <systemitem
    297         class="groupname">scanner</systemitem> group.</para>
    298 
    299         <para>If you want to access a network scanner, include two lines in
    300         <filename>net.conf</filename>, as <systemitem class="username">root</systemitem> user
    301         (make sure to replace &lt;server_ip&gt; by the actual value, below):</para>
     347        <para>
     348          The backend configuration files are located in
     349          <filename class='directory'>/etc/sane.d</filename>. Information
     350          for configuring the various backends can be found by using the man(5)
     351          page for the desired backend. Run
     352          <command>
     353            man sane-<replaceable>&lt;backend&gt;</replaceable></command>,
     354          substituting the desired backend.
     355        </para>
     356
     357        <para>
     358          Add any desired users to the <systemitem
     359          class="groupname">scanner</systemitem> group.
     360        </para>
     361
     362        <para>
     363          If you want to access a network scanner, include two lines in
     364          <filename>net.conf</filename>, as <systemitem
     365          class="username">root</systemitem> user (make sure to replace
     366          &lt;server_ip&gt; by the actual value, below):
     367        </para>
    302368
    303369<screen role="root"><userinput>cat &gt;&gt; /etc/sane.d/net.conf &lt;&lt; "EOF"
    … …  
    306372EOF</userinput></screen>
    307373
    308         <para>On the server side, include the client ip in the access list of
    309         <filename>/etc/sane.d/saned.conf</filename>, restart the
    310         <command>saned</command> daemon, and make sure the firewall, if any, is
    311         open to the client.</para>
     374        <para>
     375          On the server side, include the client ip in the access list of
     376          <filename>/etc/sane.d/saned.conf</filename>, restart the
     377          <command>saned</command> daemon, and make sure the firewall, if any,
     378          is open to the client.
     379        </para>
    312380
    313381      </sect4>
    … …  
    344412        <title>General Information</title>
    345413
    346         <para>For general information about configuring and using
    347         <application>SANE</application>, see <command>man sane</command>.
    348         Linux-2.6.x brings some special issues into the picture. See
    349         <ulink url="http://www.sane-project.org/README.linux"/> for
    350         information about using <application>SANE</application> with the
    351         Linux-2.6.x kernel. For information about USB scanning devices,
    352         run <command>man sane-usb</command>. For information about SCSI
    353         devices, run <command>man sane-scsi</command>.</para>
     414        <para>
     415          For general information about configuring and using
     416          <application>SANE</application>, see <command>man sane</command>.
     417          For information about USB scanning devices,
     418          run <command>man sane-usb</command>. For information about SCSI
     419          devices, run <command>man sane-scsi</command>.
     420        </para>
    354421
    355422      </sect4>
    … …  
    358425        <title>Configuration and setup of the 'saned' daemon</title>
    359426
    360         <para>The <command>saned</command> daemon is not meant to be used for
    361         untrusted clients. You should provide <xref linkend="fw-firewall"/>
    362         protection to ensure only trusted
    363         clients access the daemon. Due to the complex security requirements to
    364         ensure only trusted clients access the daemon, BLFS does not provide
    365         instructions to configure the <command>saned</command> daemon. If you
    366         desire to make the daemon available, ensure you provide adequate
    367         security, configure your <filename>[x]inetd.conf</filename> file and
    368         send a <userinput>SIGHUP</userinput> to the [x]inetd daemon. Some good
    369         information for setting up and securing the <command>saned</command>
    370         daemon can be found at
    371         <ulink url="http://penguin-breeder.org/sane/saned/"/>.</para>
     427        <para>
     428          The <command>saned</command> daemon is not meant to be used for
     429          untrusted clients. You should provide <xref linkend="fw-firewall"/>
     430          protection to ensure only trusted clients access the daemon. Due to
     431          the complex security requirements to ensure only trusted clients
     432          access the daemon, BLFS does not provide
     433          instructions to configure the <command>saned</command> daemon.
     434          Some good (but outdated)
     435          information for setting up and securing the <command>saned</command>
     436          daemon can be found at
     437          <ulink url="http://penguin-breeder.org/sane/saned/"/>.
     438        </para>
    372439
    373440      </sect4>
    … …  
    417484        <term><command>gamma4scanimage</command></term>
    418485        <listitem>
    419           <para>creates a gamma table in the format expected by
    420           <command>scanimage</command>.</para>
     486          <para>
     487            creates a gamma table in the format expected by
     488            <command>scanimage</command>.
     489          </para>
    421490          <indexterm zone="sane gamma4scanimage">
    422491            <primary sortas="b-gamma4scanimage">gamma4scanimage</primary>
    … …  
    428497        <term><command>sane-config</command></term>
    429498        <listitem>
    430           <para>is a tool used to determine the compiler and linker
    431           flags that should be used to compile and link
    432           <application>SANE</application>.</para>
     499          <para>
     500            is a tool used to determine the compiler and linker
     501            flags that should be used to compile and link
     502            <application>SANE</application>.
     503          </para>
    433504          <indexterm zone="sane sane-config-prog">
    434505            <primary sortas="b-sane-config">sane-config</primary>
    … …  
    440511        <term><command>saned</command></term>
    441512        <listitem>
    442           <para>is the <application>SANE</application> daemon that
    443           allows remote clients to access image acquisition devices
    444           available on the local host.</para>
     513          <para>
     514            is the <application>SANE</application> daemon that
     515            allows remote clients to access image acquisition devices
     516            available on the local host.
     517          </para>
    445518          <indexterm zone="sane saned">
    446519            <primary sortas="b-saned">saned</primary>
    … …  
    452525        <term><command>sane-find-scanner</command></term>
    453526        <listitem>
    454           <para>is a command-line tool to find SCSI and
    455           USB scanners and determine their device files. Its primary
    456           purpose is to make sure that scanners can be detected by
    457           <application>SANE</application> backends.</para>
     527          <para>
     528            is a command-line tool to find SCSI and
     529            USB scanners and determine their device files. Its primary
     530            purpose is to make sure that scanners can be detected by
     531            <application>SANE</application> backends.
     532          </para>
    458533          <indexterm zone="sane sane-find-scanner">
    459534            <primary sortas="b-sane-find-scanner">sane-find-scanner</primary>
    … …  
    465540        <term><command>scanadf</command></term>
    466541        <listitem>
    467           <para>is a command-line interface to control image acquisition
    468           devices which are equipped with an automatic document feeder
    469           (ADF).</para>
     542          <para>
     543            is a command-line interface to control image acquisition
     544            devices which are equipped with an automatic document feeder (ADF).
     545          </para>
    470546          <indexterm zone="sane scanadf">
    471547            <primary sortas="b-scanadf">scanadf</primary>
    … …  
    477553        <term><command>scanimage</command></term>
    478554        <listitem>
    479           <para>is a command line interface for scanning from image acquisition
    480           devices such as flatbed scanners or cameras. It is also used to list
    481           the available backend devices.</para>
     555          <para>
     556            is a command line interface for scanning from image acquisition
     557            devices such as flatbed scanners or cameras. It is also used to
     558            list the available backend devices.
     559          </para>
    482560          <indexterm zone="sane scanimage">
    483561            <primary sortas="b-scanimage">scanimage</primary>
    … …  
    489567        <term><command>xcam</command></term>
    490568        <listitem>
    491           <para>is a graphical camera front end for
    492           <application>SANE</application>.</para>
     569          <para>
     570            is a graphical camera front end for
     571            <application>SANE</application>.
     572          </para>
    493573          <indexterm zone="sane xcam">
    494574            <primary sortas="b-xcam">xcam</primary>
    … …  
    500580        <term><command>xscanimage</command></term>
    501581        <listitem>
    502           <para>is a graphical user interface for scanning.</para>
     582          <para>
     583            is a graphical user interface for scanning.
     584          </para>
    503585          <indexterm zone="sane xscanimage">
    504586            <primary sortas="b-xscanimage">xscanimage</primary>
    … …  
    510592        <term><filename class='libraryfile'>libsane.so</filename></term>
    511593        <listitem>
    512           <para>is the application programming interface that is used to
    513           communicate between frontends and backends.</para>
     594          <para>
     595            is the application programming interface that is used to
     596            communicate between frontends and backends.
     597          </para>
    514598          <indexterm zone="sane libsane">
    515599            <primary sortas="c-libsane">libsane.so</primary>
    … …  
    521605        <term><filename class='libraryfile'>libsane-*.so</filename></term>
    522606        <listitem>
    523           <para>modules are backend scanning library plugins used to interface
    524           with scanning devices. See
    525           <ulink url="http://www.sane-project.org/sane-supported-devices.html"/>
    526           for a list of supported backends.</para>
     607          <para>
     608            modules are backend scanning library plugins used to interface
     609            with scanning devices. See <ulink
     610            url="http://www.sane-project.org/sane-supported-devices.html"/>
     611            for a list of supported backends.
     612          </para>
    527613          <indexterm zone="sane libsane-module">
    528614            <primary sortas="c-libsane-module">libsane-*.so</primary>

  • pst/scanning/scanning.xml

    r47274444 rfa3edfef  
    1616  <title>Scanning</title>
    1717
    18   <para>This chapter contains scanning applications which allow you to
    19   convert printed documents into formatted documents readable by other
    20   applications.</para>
     18  <para>
     19    This chapter contains scanning applications which allow you to
     20    convert printed documents into formatted documents readable by other
     21    applications.
     22  </para>
    2123
    2224  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sane.xml"/>

  • pst/scanning/xsane.xml

    r47274444 rfa3edfef  
    3030    <title>Introduction to XSane</title>
    3131
    32     <para><application>XSane</application> is another front end for
    33     <xref linkend="sane"/>. It has additional features to improve the image
    34     quality and ease of use compared to <command>xscanimage</command>.</para>
     32    <para>
     33      <application>XSane</application> is another front end for
     34      <xref linkend="sane"/>. It has additional features to improve the image
     35      quality and ease of use compared to <command>xscanimage</command>.
     36    </para>
    3537
    3638    &lfs91_checked;
    … …  
    3941    <itemizedlist spacing="compact">
    4042      <listitem>
    41         <para>Download (HTTP): <ulink url="&xsane-download-http;"/></para>
    42       </listitem>
    43       <listitem>
    44         <para>Download (FTP): <ulink url="&xsane-download-ftp;"/></para>
    45       </listitem>
    46       <listitem>
    47         <para>Download MD5 sum: &xsane-md5sum;</para>
    48       </listitem>
    49       <listitem>
    50         <para>Download size: &xsane-size;</para>
    51       </listitem>
    52       <listitem>
    53         <para>Estimated disk space required: &xsane-buildsize;</para>
    54       </listitem>
    55       <listitem>
    56         <para>Estimated build time: &xsane-time;</para>
     43        <para>
     44          Download (HTTP): <ulink url="&xsane-download-http;"/>
     45        </para>
     46      </listitem>
     47      <listitem>
     48        <para>
     49          Download (FTP): <ulink url="&xsane-download-ftp;"/>
     50        </para>
     51      </listitem>
     52      <listitem>
     53        <para>
     54          Download MD5 sum: &xsane-md5sum;
     55        </para>
     56      </listitem>
     57      <listitem>
     58        <para>
     59          Download size: &xsane-size;
     60        </para>
     61      </listitem>
     62      <listitem>
     63        <para>
     64          Estimated disk space required: &xsane-buildsize;
     65        </para>
     66      </listitem>
     67      <listitem>
     68        <para>
     69          Estimated build time: &xsane-time;
     70        </para>
    5771      </listitem>
    5872    </itemizedlist>
    … …  
    8599    <title>Installation of XSane</title>
    86100
    87     <para>Install <application>XSane</application> by running the following
    88     commands:</para>
     101    <para>
     102      Install <application>XSane</application> by running the following
     103      commands:
     104    </para>
    89105
    90106<!--sed -i -e 's/netscape/xdg-open/'                   src/xsane.h      &amp;&amp;-->
    … …  
    93109make</userinput></screen>
    94110
    95     <para>This package does not come with a test suite.</para>
    96 
    97     <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     111    <para>
     112      This package does not come with a test suite.
     113    </para>
     114
     115    <para>
     116      Now, as the <systemitem class="username">root</systemitem> user:
     117    </para>
    98118
    99119<screen role="root"><userinput>make xsanedocdir=/usr/share/doc/xsane-&xsane-version; install &amp;&amp;
    100120ln -v -s ../../doc/xsane-&xsane-version; /usr/share/sane/xsane/doc</userinput></screen>
    101121<!--
    102     <para>If you have not installed <xref linkend="xdg-utils"/> and have not
    103     issued the first sed:</para>-->
    104     <para>A browser of your choice can be used to get inline help, using the
    105     following command,  as the <systemitem class="username">root</systemitem>
    106     user:</para>
     122    <para>
     123      If you have not installed <xref linkend="xdg-utils"/> and have not
     124      issued the first sed:
     125    </para>-->
     126    <para>
     127      A browser of your choice can be used to get inline help, using the
     128      following command,  as the <systemitem class="username">root</systemitem>
     129      user:
     130    </para>
    107131
    108132<screen role="root"><userinput>ln -v -s &lt;browser&gt; /usr/bin/netscape</userinput></screen>
    109133
    110     <note><para>Be sure to replace &lt;browser&gt; with the browser of your
    111     choice on your system.</para></note>
    112 
    113     <para>Alternatively, if the environment variable BROWSER is set to the
    114     browser you want to use, eg, BROWSER="/usr/bin/firefox", the first time you
    115     run <command>xsane</command>, it will be recorded in ~/.sane/xsane/xsane.rc.
    116     If you wish to change it, edit this file, or remove it, and use the
    117     instructions above, so that a new one is created.</para>
    118 
    119     <para>If <application>GIMP</application> is installed, issue the following
    120     command as the <systemitem class="username">root</systemitem> user:</para>
     134    <note>
     135      <para>
     136        Be sure to replace &lt;browser&gt; with the browser of your
     137        choice on your system.
     138      </para>
     139    </note>
     140
     141    <para>
     142      Alternatively, if the environment variable BROWSER is set to the browser
     143      you want to use, eg, BROWSER="/usr/bin/firefox", the first time you run
     144      <command>xsane</command>, it will be recorded in <filename>
     145      ~/.sane/xsane/xsane.rc</filename>. If you wish to change it, edit this
     146      file, or remove it, and use the instructions above, so that a new one is
     147      created.
     148    </para>
     149
     150    <para>
     151      If <application>GIMP</application> is installed, issue the following
     152      command as the <systemitem class="username">root</systemitem> user:
     153    </para>
    121154
    122155<screen role="root"><userinput>ln -v -s /usr/bin/xsane /usr/lib/gimp/2.0/plug-ins/</userinput></screen>
    … …  
    127160    <title>Command Explanations</title>
    128161<!--
    129     <para><command>sed -i -e 's/netscape/xdg-open/' src/xsane.h </command>:
    130     This is to use <command>xdg-open</command> for the help documentation,
    131     instead of the hardcoded browser.</para>-->
    132 
    133     <para><command>ln -v -s ../../doc/xsane-&xsane-version;
    134     /usr/share/sane/xsane/doc</command>: This symlink is created to ensure that
    135     any program that looks for the <application>XSane</application>
    136     documentation in the default location will find it, as the documentation
    137     is installed in an alternate location specified in the
    138     <command>make install</command> command.</para>
    139 
    140     <para><command>ln -v -s /usr/bin/xsane /usr/lib/gimp/2.0/plug-ins/</command>:
    141     This creates a link in the system-wide <application>GIMP</application>
    142     <filename class='directory'>plug-ins</filename> directory so that users can
    143     access <application>XSane</application> directly from
    144     <application>GIMP</application>. <application>GIMP</application> must be
    145     available before building <application>XSane</application> for this to work.
    146     Alternatively, create the link in <filename
    147     class='directory'>~/.gimp-2.0/plug-ins/</filename> to provide individual
    148     user access. <command>man xsane</command> for additional information.</para>
     162    <para>
     163      <command>sed -i -e 's/netscape/xdg-open/' src/xsane.h </command>:
     164      This is to use <command>xdg-open</command> for the help documentation,
     165      instead of the hardcoded browser.
     166    </para>-->
     167
     168    <para>
     169      <command>ln -v -s ../../doc/xsane-&xsane-version;
     170      /usr/share/sane/xsane/doc</command>: This symlink is created to ensure
     171      that any program that looks for the <application>XSane</application>
     172      documentation in the default location will find it, as the documentation
     173      is installed in an alternate location specified in the <command>make
     174      install</command> command.
     175    </para>
     176
     177    <para>
     178      <command>ln -v -s /usr/bin/xsane /usr/lib/gimp/2.0/plug-ins/</command>:
     179      This creates a link in the system-wide <application>GIMP</application>
     180      <filename class='directory'>plug-ins</filename> directory so that users
     181      can access <application>XSane</application> directly from
     182      <application>GIMP</application>. <application>GIMP</application> must
     183      be available before building <application>XSane</application> for this
     184      to work. Alternatively, create the link in <filename
     185      class='directory'>~/.gimp-2.0/plug-ins/</filename> to provide individual
     186      user access. <command>man xsane</command> for additional information.
     187    </para>
    149188
    150189  </sect2>
    … …  
    174213        <term><command>xsane</command></term>
    175214        <listitem>
    176           <para>is a graphical user-interface to control an image acquisition
    177           device such as a flatbed scanner.</para>
     215          <para>
     216            is a graphical user-interface to control an image acquisition
     217            device such as a flatbed scanner.
     218          </para>
    178219          <indexterm zone="xsane xsane-prog">
    179220            <primary sortas="b-xsane">xsane</primary>
Note: See TracChangeset for help on using the changeset viewer.