Added note about doxygen configuration for sanei.

Henning Meier-Geinitz <henning@meier-geinitz.de>

doc/backend-writing.txt

@@ -1,4 +1,4 @@
-2002-01-10
+2002-01-24
 
 Here are a few rules and tips that should help writing a
 SANE-conformant backend and including it into the SANE package:
@@ -112,7 +112,11 @@ PROGRAMMING
 
 * Please use sanei functions whenever possible (e.g. 
   sanei_config_read()). This makes porting to other os/platforms much
-  easier.
+  easier. Most of these functions are documented in their respective 
+  header files in include/sane/sanei_*.h. For some of them there is also
+  documentation in doxygen format: http://sanei.meier-geinitz.de/. These
+  HTML pages can be generated by calling "doxygen sanei-doxygen.conf" in
+  the doc/ directory.
 
 * Do make sure that your code is byte-order independent.  This is
   particularly important for networking-related code and when dealing

doc/sane.man

@@ -1,4 +1,4 @@
-.TH sane 7 "12 Jan 2002"
+.TH sane 7 "24 Jan 2002"
 .IX sane
 
 .SH NAME
@@ -43,9 +43,10 @@ website: http://www.mostang.com/sane/html/ (HTML), or
 http://www.mostang.com/sane/sane.ps (Postscript).
 .P
 There is some more information for programmers in
-@DOCDIR@/backend-writing.txt. Before a new backend or frontend project is
-started, have a look at @DOCDIR@/PROJECTS for projects that are planned or not
-yet included into the SANE distribution.
+@DOCDIR@/backend-writing.txt. Some of the internal SANE routines (sanei) are
+documented using doxygen: http://sanei.meier-geinitz.de/ . Before a new
+backend or frontend project is started, have a look at @DOCDIR@/PROJECTS for
+projects that are planned or not yet included into the SANE distribution.
 .P
 Your help is always appreciated. Look at @DOCDIR@/TODO for things that should
 be done. Not only programmers are needed, but also reading and fixing the