os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Some typos

Browse source 
- Subtle grammar and style fixes

Submitted by:	Ken Tom <subd@mui.net>
This commit is contained in:
Marc Fonvieille 2004-08-05 12:16:58 +00:00
parent 65a2018fee
commit 2409322e61
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=21830
1 changed files with 11 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
View file

@ -1674,7 +1674,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<sect2> <sect2>
<title>Kernel Configuration</title> <title>Kernel Configuration</title>
<para>As mentionned above both SCSI and USB interfaces are <para>As mentioned above both SCSI and USB interfaces are
supported. According to your scanner interface, different supported. According to your scanner interface, different
device drivers are required.</para> device drivers are required.</para>
@ -1693,7 +1693,7 @@ device ohci
device uscanner</programlisting> device uscanner</programlisting>
<para>Depending upon the USB chipset on your motherboard, you <para>Depending upon the USB chipset on your motherboard, you
only need one of both <literal>device uhci</literal> and will only need either <literal>device uhci</literal> or
<literal>device ohci</literal>, however having both in the <literal>device ohci</literal>, however having both in the
kernel configuration file is harmless.</para> kernel configuration file is harmless.</para>
@ -1793,10 +1793,10 @@ Re-scan of bus 3 was successful</screen>
devices</ulink> list specifies which backend will support your devices</ulink> list specifies which backend will support your
image scanner. It is mandatory to determine the correct image scanner. It is mandatory to determine the correct
backend for your scanner if you want to be able to use your backend for your scanner if you want to be able to use your
device. The frontends part provides a graphical scanning device. The frontends part provides the graphical scanning
interface (<application>xscanimage</application>).</para> interface (<application>xscanimage</application>).</para>
<para>The first thing to do is installing the <filename <para>The first thing to do is install the <filename
role="package">graphics/sane-backends</filename> port or role="package">graphics/sane-backends</filename> port or
package. Then, use the <command>sane-find-scanner</command> package. Then, use the <command>sane-find-scanner</command>
command to check the scanner detection by the command to check the scanner detection by the
@ -1819,7 +1819,7 @@ found SCSI scanner "AGFA SNAPSCAN 600 1.10" at /dev/pass3</screen>
<para>Now we have to check if the scanner will be identified by <para>Now we have to check if the scanner will be identified by
a scanning frontend. By default, the a scanning frontend. By default, the
<application>SANE</application> backends come with a command <application>SANE</application> backends comes with a command
line tool called &man.scanimage.1;. This command allows you line tool called &man.scanimage.1;. This command allows you
to list the devices and to perform an image acquisition from to list the devices and to perform an image acquisition from
the command line. The <option>-L</option> option is used to the command line. The <option>-L</option> option is used to
@ -1835,7 +1835,7 @@ device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
used. The <filename used. The <filename
role="directory">/usr/local/etc/sane.d/</filename> directory role="directory">/usr/local/etc/sane.d/</filename> directory
contains all backends configuration files. This contains all backends configuration files. This
identification problem does appear with some USB identification problem does appear with certain USB
scanners.</para> scanners.</para>
<para>For example, with the USB scanner used in the <xref <para>For example, with the USB scanner used in the <xref
@ -1901,7 +1901,7 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
<para><application>Xsane</application> (<filename <para><application>Xsane</application> (<filename
role="package">graphics/xsane</filename>) is another popular role="package">graphics/xsane</filename>) is another popular
graphical scanning frontend. This frontend offers advanced graphical scanning frontend. This frontend offers advanced
features like various scanning mode (photocopy, fax, etc.), features such as various scanning mode (photocopy, fax, etc.),
color correction, batch scans, etc. Both of these applications color correction, batch scans, etc. Both of these applications
are useable as a <application>GIMP</application> are useable as a <application>GIMP</application>
plugin.</para> plugin.</para>
@ -1910,9 +1910,10 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
<sect2> <sect2>
<title>Allowing Scanner Access to Other Users</title> <title>Allowing Scanner Access to Other Users</title>
<para>All previous operations have been done with the <para>All previous operations have been done with
<username>root</username> privileges, however a user should be <username>root</username> privileges. You may however, need
able to use the scanner. The user will need read and write other users to have access
to the scanner. The user will need read and write
permissions to the device node used by the scanner. As an permissions to the device node used by the scanner. As an
example, our USB scanner uses the device node example, our USB scanner uses the device node
<devicename>/dev/uscanner0</devicename> which is owned by the <devicename>/dev/uscanner0</devicename> which is owned by the