2003-09-23 17:03:44 +00:00 · 2003-09-23 17:03:44 +00:00 · bb8a4165b0
commit bb8a4165b0
--- a/icons/contents.gif
+++ b/icons/contents.gif
--- a/icons/next.gif
+++ b/icons/next.gif
--- a/icons/previous.gif
+++ b/icons/previous.gif
--- a/icons/up.gif
+++ b/icons/up.gif
--- a/lj98/doc000.html
+++ b/lj98/doc000.html
@ -0,0 +1,24 @@
+<html><body>
+<a href="doc001.html"><img src=../icons/next.gif alt="Next"></a>
+<img src=../icons/up_gr.gif border=2 alt="Previous"></a>
+<img src=../icons/previous_gr.gif border=2 alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+<title>Contents</title>
+<h1>Contents</h1><p>
+
+<table>
+<tr></tr><tr><td colspan=20>1<tt>   </tt><a href="doc002.html#s1"><b>Introduction</b></a></td></tr>
+<tr></tr><tr><td colspan=20>2<tt>   </tt><a href="doc003.html#s2"><b>Using SANE</b></a></td></tr>
+<tr></tr><tr><td colspan=20>3<tt>   </tt><a href="doc004.html#s3"><b>What Else Comes with SANE?</b></a></td></tr>
+<tr></tr><tr><td colspan=20>4<tt>   </tt><a href="doc005.html#s4"><b>How Does It Work?</b></a></td></tr>
+<tr></tr><tr><td colspan=20>5<tt>   </tt><a href="doc006.html#s5"><b>Programming With SANE</b></a></td></tr>
+<tr></tr><tr><td colspan=20>6<tt>   </tt><a href="doc007.html#s6"><b>SANE and Commercial Applications/Drivers</b></a></td></tr>
+<tr></tr><tr><td colspan=20>7<tt>   </tt><a href="doc008.html#s7"><b>Future Plans</b></a></td></tr>
+</table><p><hr>
+<a href="doc001.html"><img src=../icons/next.gif alt="Next"></a>
+<img src=../icons/up_gr.gif border=2 alt="Previous"></a>
+<img src=../icons/previous_gr.gif border=2 alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc001.html
+++ b/lj98/doc001.html
@ -0,0 +1,52 @@
+<html><body>
+<a href="doc002.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc000.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+<title>sane</title>
+
+
+<p>
+
+
+
+
+
+<p>
+
+
+
+<p>
+
+
+
+
+<p><center><h1>The SANE Scanner Interface</h1></center>
+<center>David Mosberger<br>
+  <tt><font size=-1><a href="mailto:David.Mosberger@acm.org">David.Mosberger@acm.org</a></font></tt><br><spacer type=vertical size=20> <i>This article
+    originally appeared in Linux Journal Issue 47, March 1998</i></center>
+<center></center>
+
+
+<p>
+
+<p><center><b>Abstract</b></center><blockquote>
+  SANE stands for ``Scanner Access Now Easy''. It is a universal
+  interface that enables you to acquire images from any device that
+  produces raster images, including flatbed scanners, video and still
+  cameras and frame grabbers. The intent of SANE is to make it
+  possible to write image-processing applications without having to
+  worry about peculiarities of individual devices. Looking at it from
+  the other side, SANE makes it possible to write a device driver once
+  and only once. That same device driver can then be used by any
+  SANE-compliant application.
+</blockquote
+
+<p><h2><a href="doc002.html">1 Introduction</a></h2><h2><a href="doc003.html">2 Using SANE</a></h2><h2><a href="doc004.html">3 What Else Comes with SANE?</a></h2><h2><a href="doc005.html">4 How Does It Work?</a></h2><h2><a href="doc006.html">5 Programming With SANE</a></h2><h2><a href="doc007.html">6 SANE and Commercial Applications/Drivers</a></h2><h2><a href="doc008.html">7 Future Plans</a></h2><h2><a href="doc009.html"> Acknowledgments</h2><p><hr>
+<a href="doc002.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc000.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc002.html
+++ b/lj98/doc002.html
@ -0,0 +1,62 @@
+<html><body>
+<a href="doc003.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc001.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>Introduction</title>
+<h2><a name="s1">1 Introduction</a></h2>
+
+<p>Have you ever wanted to scan an image under Linux? If so, you
+probably know the feeling of being faced by a bewildering number of
+scanner-driver packages. At the time of this writing, there exist
+at least fourteen different scanner packages for Linux. While each
+individual package is usually of high quality, it is often difficult
+to determine which package should be used for which scanner.
+Furthermore, some packages come with a command-line interface, others
+include tcl/tk based graphical front ends, still others come with
+full-featured, graphical front ends. While variety is said to make life
+sweet, in this case it's more likely to cause a sizeable headache.
+
+<p>SANE was created to provide a solution to this dilemma. The basic idea is
+simple: if there were a general and well-defined application
+programming interface (API), it would be easy to write applications
+independently from scanner drivers. Thus, the author of a new scanner
+driver would not have to worry about writing an application for the
+driver. There are benefits for the application programmer as
+well; since SANE is universal, an application can be written
+independently of the devices that it will eventually control. Suppose
+we wanted five applications to support ten different devices. With the
+old approach, 5*10=50 programs would have to be written. With SANE,
+only 5+10=15 programs have to be written. SANE has advantages for the
+user too. It gives the user the liberty to choose whichever application
+he likes best, and that one application can be used to control
+all image-acquisition devices the user can access. Thus, SANE
+makes it possible to present the same consistent interface independent
+of the particular device that is in use.
+
+<p>Of course, SANE is not the first attempt to create such a universal
+interface. You may have heard of TWAIN, PINT or the Linux hand-scanner
+interface. The problem is that these older interfaces prove to be
+lacking in one way or another. For example, PINT is really a somewhat
+primitive kernel-level interface and the hand-scanner interface by
+definition is limited to hand-scanners. In contrast, SANE is general
+enough to support any device that acquires raster images. The closest
+thing to SANE is probably TWAIN. The fact that the two rhyme is not
+coincidental, but that's a different story. The main reason TWAIN is
+not SANE is that TWAIN puts the graphical user-interface to control
+the device in the driver instead of the application. This makes it
+unsuitable for Linux or networked environments where the scanner
+driver might run on one machine and the application on another. In
+contrast, SANE enforces a strict separation between the actual driver
+and the user-interface for its controls. Indeed, the current SANE
+distribution includes support for network-transparent scanning.
+
+<p><p><hr>
+<a href="doc003.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc001.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc003.html
+++ b/lj98/doc003.html
@ -0,0 +1,242 @@
+<html><body>
+<a href="doc004.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc002.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>Using SANE</title>
+<h2><a name="s2">2 Using SANE</a></h2>
+
+<p>To start using SANE, fetch the latest version of the distribution from
+the ftp directory:
+<center>
+  <a href="ftp://ftp.mostang.com/pub/sane/"><tt>ftp://ftp.mostang.com/pub/sane/</tt></a>
+</center>
+
+<p>If you want to build the graphical-user-interface programs that come
+with SANE, you will also need to fetch, build and install the GIMP or,
+at a minimum, the GTK distribution.  Both GIMP and GTK are available
+at <a href="ftp://ftp.gimp.org/">ftp://ftp.gimp.org/</a>. GTK
+is the user-interface toolkit that originally has been developed for
+the GIMP, but is now being adopted by many other projects, including
+SANE.  Note that the SANE distribution will build just fine without
+the GIMP/GTK libraries.  However, that way none of the nice
+graphical-user-interface programs will be built, thus taking away much
+of the fun. So, unless you are building SANE for a server only, I
+recommend that you install at least GTK, if not GIMP.
+
+<p>After fetching the SANE distribution, unpack the compressed tar file
+and follow the instructions in the README file. The README explains
+how to build and install SANE. Also, take a look at the file called
+PROBLEMS; it contains a list of known problems and their work arounds.
+
+<p>Note that you don't have to own a scanner or a camera to play
+with SANE. The distribution includes a pseudo-driver that simulates a
+scanner by reading portable ``anymap'' (PNM) files. Also,
+SANE is not limited to Linux. Besides Linux for Alpha, x86 and m68k,
+it includes support for AIX, Digital Unix, FreeBSD, HP-UX, IRIX,
+NetBSD, SCO, Solaris, SunOS, and even OS/2.
+
+<p>After installing SANE, you should be able to type the command
+<blockquote>
+<pre>
+scanimage --list-devices
+</pre>
+</blockquote>
+and get the output shown below:
+<blockquote><font size=-1>
+<pre>
+device `mustek:/dev/scanner' is a Mustek MFC-06000CZ flatbed scanner
+device `pnm:0' is a Noname PNM file reader virtual device
+device `pnm:1' is a Noname PNM file reader virtual device
+</pre>
+</font></blockquote>
+
+As the listing shows, in this particular case, a Mustek scanner is
+available under name <tt>mustek:/dev/scanner</tt> and two fake devices
+called <tt>pnm:0</tt> and <tt>pnm:1</tt> are available that can be used to
+read PNM files.  To get list of all options for a particular device,
+for example <tt>pnm:0</tt>, simply type:
+<blockquote>
+<pre>
+scanimage --device pnm:0 --help
+</pre>
+</blockquote>
+This will produce the help message shown in Figure <a href="doc003.html#f1">1</a>.
+
+<p><p><a name="f1"></a>
+  <blockquote>
+    <font size=-1>
+<pre>
+Usage: scanimage [OPTION]...
+
+Start image acquisition on a scanner device and write PNM image data to
+standard output.
+
+-d, --device-name=DEVICE   use a given scanner device
+-h, --help                 display this help message and exit
+-L, --list-devices         show available scanner devices
+-v, --verbose              give even more status messages
+-V, --version              print version information
+
+Options specific to device `pnm':
+  Source Selection:
+    --filename &lt;\&lt;&gt;string&gt; [/tmp/input.ppm]
+        The filename of the image to be loaded.
+  Image Enhancement:
+    --brightness -100...100% [0]
+        Controls the brightness of the acquired image.
+    --contrast -100...100% [0]
+        Controls the contrast of the acquired image.
+    --grayify[=(yes|no)] [no]
+        Load the image as grayscale.
+    --three-pass[=(yes|no)] [no]
+        Simulate a three-pass scanner by returning 3 separate frames.  For
+        kicks, it returns green, then blue, then red.
+    --hand-scanner[=(yes|no)] [no]
+        Simulate a hand-scanner.  Hand-scanners often do not know the image
+        height a priori.  Instead, they return a height of -1.  Setting this
+        option allows one to test whether a front end can handle this
+        correctly.
+    --default-enhancements
+        Set default values for enhancement controls (brightness &amp; contrast).
+    
+</pre>
+  </font></blockquote>
+  <p><center>Figure 1: Scanimage Help Message For <tt>pnm:0</tt> Pseudo-Device</center>
+  
+<p>
+
+<p>The SANE package comes with a detailed man page that explains the
+specifics of the <tt>scanimage</tt> program. As an example, suppose we
+had a PPM file named <tt>input.ppm</tt>. We can use the scanimage
+program to ``scan'' that image and increase its brightness by 50%
+using the following command:
+<blockquote>
+<pre>
+scanimage --device pnm --brightness 50 input.ppm &gt; output.ppm
+</pre>
+</blockquote>
+If you look at file <tt>output.ppm</tt> with an image viewer such as xv,
+you should be able to see that <tt>output.ppm</tt> is noticeably
+brighter.
+
+<p><p><a name="f2"></a>
+  <center>
+    
+    <img width=500 height=672 src="img000.gif">
+    <p><center>Figure 2: SANE Dialog Window</center>
+    
+  </center>
+<p>
+
+<p><p><a name="f3"></a>
+  <center>
+    
+    <img width=780 height=881 src="img001.gif">
+    <p><center>Figure 3: SANE Preview Window</center>
+    
+  </center>
+<p>
+
+<p>You may say: cool, but where is the graphical user-interface?
+Assuming you had the GTK libraries installed when SANE was built, you
+can invoke a program called <tt>xscanimage</tt> that will present you
+with a dialog box containing a list of available devices. If you
+double-click on the ``pnm:0'' entry, you'll get the dialog shown in
+Figure <a href="doc003.html#f2">2</a>. As you can see, the dialog includes two
+text-entry boxes labeled ``Filename'' and a slider labelled
+``Brightness''. If you enter <tt>output.ppm</tt> in the first text-entry
+box and <tt>input.ppm</tt> in the second box and move the brightness
+slider to 50.0, you can press the Scan button at the bottom left and
+get the same result as with the scanimage command line shown above. Of
+course, before doing the actual scanning, you could press the Preview
+button at the bottom right to pop up a preview window (see
+Figure <a href="doc003.html#f3">3</a>).  In the preview window, you can push the
+Acquire-&gt;Preview button to obtain a low-resolution preview
+of the final image.  For example, by moving the brightness slider
+around, you can see how the brightness of the image is affected. After
+moving the slider, you'll need to press the Acquire Preview button to
+get an updated preview.
+
+<p>When scanning an image with a real scanner or camera, you'll usually
+want to enhance it in various ways, such as making it appear sharper.
+The nice thing about the xscanimage program is that it can also be run
+as a GIMP extension. To do this, simply create a symlink from the GIMP
+plug-ins directory to the xscanimage binary. Assuming the SANE
+installation defaults, you could do this with the following command:
+<blockquote>
+<pre>
+ln -s /usr/local/bin/xscanimage ~/.gimp/plug-ins
+</pre>
+</blockquote>
+
+<p><p><a name="f4"></a>
+  <center>
+    
+    <img width=565 height=699 src="img002.gif">
+    <p><center>Figure 4: Mustek Dialog Window for <tt>xscanimage</tt></center>
+    
+  </center>
+<p>
+
+<p>After making this link, xscanimage will attach itself to the GIMP's
+``Xtns'' menu the next time you start it. This makes it possible to
+invoke, for example, the PNM pseudo-device by selecting
+``Xtns-&gt;Acquire Image-&gt;pnm:0''. When invoked in
+this manner, pressing the Scan button will put the newly scanned image
+inside a GIMP window (instead of saving it to disk). Now, the usual
+GIMP image-manipulation functions can be used to enhance the acquired
+image before saving it.
+
+<p>The PNM pseudo-device may be fun, but what does a real scanner
+interface look like? Figure <a href="doc003.html#f4">4</a> shows the xscanimage
+dialog as it appears for Mustek flatbed scanners. The figure also
+demonstrates another feature of xscanimage: tool tips (also known as
+``balloon help''). Tool tips make it easier for new users to get
+acquainted with the capabilities of their scanner or camera. In the
+figure, the mouse points to the Scan Source menu and, as a result, the
+help information for that menu is shown in the yellow box below the
+mouse pointer. Tool tips are handy for new users, but after a while,
+they tend to get in your way. Thus, xscanimage allows advanced users
+to turn off the tool tips using the Preferences sub-menu.
+
+<p><p><a name="f5"></a>
+  <center>
+    
+    <img width=780 height=546 src="img003.gif">
+    <p><center>Figure 5: Mustek Dialog With Gamma Table Editor</center>
+    
+  </center>
+<p>
+
+<p>As you can see, the Mustek dialog looks quite different from the PNM
+pseudo-device interface. This is because the underlying devices have
+different capabilities. In fact, the device dialog depends not only on
+the selected device, but also on the mode of the device. For example,
+when turning on the ``Use custom gamma table'' option near the bottom
+of the dialog, the interface changes, and the result is shown in
+Figure <a href="doc003.html#f5">5</a>. As you can see, the right half of the dialog
+now contains a graph editor that allows the user to modify the
+intensity, red, green or blue gamma table. In other words, xscanimage
+displays precisely the options that are active or meaningful for a
+given scan mode, greatly reducing the likelihood of confusing the
+user.
+
+<p>Looking at the image-intensity gamma table in the right half of the
+figure, you can probably imagine that it would be rather annoying to
+define the gamma tables each time you started xscanimage.  Once the
+ideal tables have been found, it would be nice if it were possible to
+save them. For this purpose, xscanimage allows saving the current
+device settings through an entry in the Preferences sub-menu. Once
+saved, whenever xscanimage is started, it automatically restores the
+last saved option values for that device.
+
+<p><p><hr>
+<a href="doc004.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc002.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc004.html
+++ b/lj98/doc004.html
@ -0,0 +1,52 @@
+<html><body>
+<a href="doc005.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc003.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>What Else Comes with SANE?</title>
+<h2><a name="s3">3 What Else Comes with SANE?</a></h2>
+
+<p>Now that you have seen how to use some of the programs that come with
+the SANE distribution, it is time to tell you what else is included.
+At the time of this writing, the package includes drivers for the
+following devices:
+
+<p><ul>
+<li>Connectix QuickCam (color and monochrome).
+<li>Some Epson SCSI scanners.
+<li>Hewlett-Packard ScanJet SCSI scanners.
+<li>Microtek SCSI scanners.
+<li>Mustek SCSI flatbed scanners (both one-pass and three-pass
+  scanners are supported).
+<li>PINT devices: PINT is a Unix-kernel interface for NetBSD,
+  OpenBSD and SunOS. SANE's PINT driver provides access to any scanner
+  for which there is PINT support.
+<li>Most UMAX SCSI scanners.
+</ul>
+
+<p>Support for many other scanners and cameras is planned and some of
+them should be ready by the time you read this article. For the latest
+information, please visit the web page listed in the References.
+
+<p>Available applications are the command-line <tt>scanimage</tt>, the
+graphical <tt>xscanimage</tt> (either stand-alone or as a GIMP
+extension) and <tt>xcam</tt>, a graphical user interface suitable for
+cameras which produce a continuous stream of images (such as the
+Connectix QuickCam).
+
+<p>In addition, there are SANE API bindings for Python and Java API and a
+network daemon called <tt>saned</tt> that provides network-transparent
+access to remote devices. Assuming you have the appropriate
+permissions, this makes it possible to control a camera running in the
+U.S. from a machine running in Europe---all courtesy of SANE and the
+Internet.
+
+<p><p><hr>
+<a href="doc005.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc003.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc005.html
+++ b/lj98/doc005.html
@ -0,0 +1,80 @@
+<html><body>
+<a href="doc006.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc004.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>How Does It Work?</title>
+<h2><a name="s4">4 How Does It Work?</a></h2>
+
+<p>When building a SANE application, it must be linked against the shared
+library called libsane.so. In reality, libsane.so is just a symlink to
+one of the SANE drivers. Since every SANE driver exports the exact
+same interface, you can change the libsane.so symlink at any time and
+effectively change which driver the application is using.  While this
+is useful in the sense that it allows upgrading to a different driver
+without having to relink all the applications, it would not be very
+convenient if you had to change a symlink whenever you wished to
+switch the scanning device. For this reason, SANE supports two
+pseudo-drivers called <tt>dll</tt> and <tt>net</tt>. They are
+pseudo-drivers because rather than talking to physical devices, they
+talk to other SANE drivers, as illustrated in
+Figure <a href="doc005.html#f6">6</a>.
+
+<p>For machine A, the libsane.so symlink points to the dll pseudo-driver
+(called libsane-dll.so). That pseudo-driver uses dynamically linked
+libraries (dll) to access other SANE drivers. In the example, dll is
+configured to use the pnm, mustek and net drivers. The net driver is
+again a pseudo-driver; it provides access to remote scanners by
+connecting to the SANE daemon (saned) running on machine B. Machine B
+in turn uses dll again to provide access to a variety of other
+drivers. As you might imagine, the exact configuration is entirely up
+to the system administrator(s) of machines A and B. It is fairly
+typical to have libsane.so be a symlink to the dll pseudo-driver, but
+there is no reason it couldn't point to the net pseudo-driver or just
+the mustek driver. Of course, in the latter case the implication would
+be that applications could access the mustek driver only---but that's
+perfectly reasonable for certain environments.
+
+<p><p><a name="f6"></a>
+  <center>
+    
+    <img width=780 height=384 src="img004.gif">
+    <p><center>Figure 6: Possible SANE Hierarchy</center>
+    
+  </center>
+<p>
+
+<p>This approach is very flexible, but it raises an interesting question:
+how do we name devices in such an environment? The answer is that
+every real driver has its own device name space. For example, the
+Mustek and HP drivers use the path for the Unix special device that
+controls the device, such as <tt>/dev/scanner</tt>. With pseudo-drivers,
+things get a bit more interesting. Since dll must guarantee that each
+device name is unique, it simply prefixes the name of each subordinate
+device with the name of the subordinate driver, separated by a colon.
+Thus, on machine A, the mustek scanner would be called
+<tt>mustek:/dev/scanner</tt>. The net pseudo-driver does something
+similar: it prefixes the remote device name with the remote host name
+(again using a colon as a separator). For example, HP scanner 1 on
+machine B would appear on machine A under the name
+<tt>net:B.domain.com:hp:/dev/scanner1</tt>.  While this doesn't make for
+the world's prettiest names, the information contained in the names is
+actually quite useful. In essence, much like a Unix path name, the
+device names convey the path through the SANE hierarchy that leads to
+a particular device. For example, if you know that machine B is down,
+it's pretty obvious that <tt>net:B.domain.com:hp:/dev/scanner1</tt> will
+be down as well. If someone feels strongly about these names, it is
+possible for an application to let a user or system administrator
+define aliases that are more concise. For example, an application
+could let a user rename the above device to ``HP Scanner 1'', which
+may be easier for beginners.
+
+<p><p><hr>
+<a href="doc006.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc004.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc006.html
+++ b/lj98/doc006.html
@ -0,0 +1,64 @@
+<html><body>
+<a href="doc007.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc005.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>Programming With SANE</title>
+<h2><a name="s5">5 Programming With SANE</a></h2>
+
+<p>By definition, SANE is only as good as the programs that use
+it. This means the more applications and the more devices that use SANE,
+the merrier. The SANE distribution comes with a detailed document
+that explains the SANE API; however, the interface is quite simple.
+The six main functions are listed below:
+
+<p><blockquote>
+<dl>
+
+<p><dt><i>handle</i> &lt;- <tt>sane_open</tt> (<i>device-name</i>):<dd>
+  allows you to open a SANE device by name (e.g., pnm:0).
+
+<p><dt><tt>sane_close</tt> (<i>handle</i>):<dd> allows you to close a SANE
+  device.
+
+<p><dt><tt>sane_get_option_descriptor</tt> (<i>handle</i>,
+  <i>option-number</i>):<dd> is used to query the controls available to
+  the device (such as the brightness control in the PNM pseudo-device
+  driver).
+
+<p><dt><tt>sane_control_option</tt> (<i>handle</i>, <i>option-number</i>,
+  <i>action</i>, <i>value</i>):<dd> is used to get or set the value of an
+  option. For example, it can be used to set the value of the
+  brightness option to 50 percent. In addition, some options support
+  an auto-mode where the driver picks a reasonable value.  For such
+  options, <tt>sane_control_option()</tt> can also be used to turn
+  auto-mode on or off.
+
+<p><dt><tt>sane_start</tt> (<i>handle</i>):<dd> is used to start the
+  acquisition of an image.
+
+<p><dt><i>bytes-read</i> &lt;- <tt>sane_read</tt> (<i>handle</i>,
+  <i>buffer</i>, <i>buffer-size</i>):<dd> is used to read the actual image
+  data until the entire image has been acquired.
+
+<p></dl>
+</blockquote>
+
+<p>The SANE API is simple by design. The goal was to make it possible to
+accomplish a simple task in a small amount of time while still
+providing enough functionality to enable sophisticated drivers and
+applications. The simplicity is best evidenced by the fact that it
+took just two evening sessions to convert the <tt>hpscanpbm</tt> program
+into a SANE driver for HP scanners. On the other end of the spectrum,
+the Mustek driver and xscanimage are fairly complicated programs and
+SANE had no problems accommodating them.
+
+<p><p><hr>
+<a href="doc007.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc005.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc007.html
+++ b/lj98/doc007.html
@ -0,0 +1,37 @@
+<html><body>
+<a href="doc008.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc006.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>SANE and Commercial Applications/Drivers</title>
+<h2><a name="s6">6 SANE and Commercial Applications/Drivers</a></h2>
+
+<p>What's our position with respect to commercial SANE drivers or
+applications? In the spirit of the GNU Public License, it is
+preferrable to have the source for SANE programs available.
+However, it is permissible to write a dynamically loaded,
+commercial SANE driver on Linux and other platforms that support
+dynamic loading. (Drivers are always dynamically loaded, so this
+doesn't cause any extra work.) By the same token, it is also proper
+to write a commercial application that links with the libsane.so
+shared library. The basic ideas supporting this position are:
+
+<p><ol>
+
+<p><li>Healthy competition between commercial and free programs is an
+  asset, not a liability.
+
+<p><li>The more wide-spread use SANE finds, the better for the
+  Linux/Unix community.
+
+<p></ol>
+
+<p><p><hr>
+<a href="doc008.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc006.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc008.html
+++ b/lj98/doc008.html
@ -0,0 +1,36 @@
+<html><body>
+<a href="doc009.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc007.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>Future Plans</title>
+<h2><a name="s7">7 Future Plans</a></h2>
+
+<p>In the immediate future, the plan is to add support for many more
+devices.  For example, Agfa and Plustek scanner and Nikon filmscanner
+drivers are planned, and there is hope that drivers for some of the
+more popular digital cameras will materialize soon as well.  To get
+the ultimate in network connectivity, there are also plans to
+implement a scanner application in Java, making it possible to control
+your scanner from your favorite Java-enabled web browser.
+
+<p>In the long term, it would be interesting to generalize SANE to
+embrace other multimedia devices including audio sources or video tape
+recorders.
+
+<p>In other words, SANE has just started, and there are many exciting
+projects to come. If you're interested in pursuing some of these by
+all means get in touch with other developers through the SANE mailing
+list.  The mailing list and other valuable resources can be found at
+the SANE home page at
+<a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>.
+
+<p><p><hr>
+<a href="doc009.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc007.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/doc009.html
+++ b/lj98/doc009.html
@ -0,0 +1,27 @@
+<html><body>
+<img src=../icons/next_gr.gif border=2 alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc008.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+
+<title>Acknowledgments</title>
+<h2><a name="s7"> Acknowledgments</h2>
+
+<p>The SANE project would not have been possible without the continued
+support of many people. In particular the contributions by Andreas
+Beck, Gordon Matzigkeit, Patrick Reynolds, and Tristan Tarrant were
+crucial to transforming SANE from a dream into reality.
+
+<p>I would also like to thank Michael K. Johnson and Jeremy Rosenberger
+for their feedback on an early draft version of this article.
+
+<p>
+
+<p><p><hr>
+<img src=../icons/next_gr.gif border=2 alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc008.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>
--- a/lj98/img000.gif
+++ b/lj98/img000.gif
--- a/lj98/img001.gif
+++ b/lj98/img001.gif
--- a/lj98/img002.gif
+++ b/lj98/img002.gif
--- a/lj98/img003.gif
+++ b/lj98/img003.gif
--- a/lj98/img004.gif
+++ b/lj98/img004.gif
--- a/lj98/index.html
+++ b/lj98/index.html
@ -0,0 +1,52 @@
+<html><body>
+<a href="doc002.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc000.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+<title>sane</title>
+
+
+<p>
+
+
+
+
+
+<p>
+
+
+
+<p>
+
+
+
+
+<p><center><h1>The SANE Scanner Interface</h1></center>
+<center>David Mosberger<br>
+  <tt><font size=-1><a href="mailto:David.Mosberger@acm.org">David.Mosberger@acm.org</a></font></tt><br><spacer type=vertical size=20> <i>This article
+    originally appeared in Linux Journal Issue 47, March 1998</i></center>
+<center></center>
+
+
+<p>
+
+<p><center><b>Abstract</b></center><blockquote>
+  SANE stands for ``Scanner Access Now Easy''. It is a universal
+  interface that enables you to acquire images from any device that
+  produces raster images, including flatbed scanners, video and still
+  cameras and frame grabbers. The intent of SANE is to make it
+  possible to write image-processing applications without having to
+  worry about peculiarities of individual devices. Looking at it from
+  the other side, SANE makes it possible to write a device driver once
+  and only once. That same device driver can then be used by any
+  SANE-compliant application.
+</blockquote
+
+<p><h2><a href="doc002.html">1 Introduction</a></h2><h2><a href="doc003.html">2 Using SANE</a></h2><h2><a href="doc004.html">3 What Else Comes with SANE?</a></h2><h2><a href="doc005.html">4 How Does It Work?</a></h2><h2><a href="doc006.html">5 Programming With SANE</a></h2><h2><a href="doc007.html">6 SANE and Commercial Applications/Drivers</a></h2><h2><a href="doc008.html">7 Future Plans</a></h2><h2><a href="doc009.html"> Acknowledgments</h2><p><hr>
+<a href="doc002.html"><img src=../icons/next.gif alt="Next"></a>
+<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
+<a href="doc000.html"><img src=../icons/previous.gif alt="Previous"></a>
+<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
+<hr>
+</body></html>