- Changed more (all?) references to actions to the

[privoxy.git] / doc / text / developer-manual.txt

diff --git a/doc/text/developer-manual.txt b/doc/text/developer-manual.txt
index 5541e66..99df01d 100644 (file)
--- a/doc/text/developer-manual.txt
+++ b/doc/text/developer-manual.txt
@@ -1,8 +1,8 @@
 Privoxy Developer Manual
 
 Privoxy Developer Manual
 

-By: Privoxy Developers
+Copyright © 2001, 2002 by Privoxy Developers

 
 

-$Id: developer-manual.sgml,v 1.40 2002/05/04 00:43:43 hal9 Exp $
+$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $

 
 The developer manual gives the users information on how to help the developer
 team. It provides guidance on coding, testing, documentation and other issues.
 
 The developer manual gives the users information on how to help the developer
 team. It provides guidance on coding, testing, documentation and other issues.


@@ -129,9 +129,9 @@ Table of Contents
     8.4. Report ads or other filter problems
     8.5. Other
    
     8.4. Report ads or other filter problems
     8.5. Other
    

-9. Copyright and History
+9. Privoxy Copyright, License and History

    
    

-    9.1. Copyright
+    9.1. License

     9.2. History
    
 10. See also
     9.2. History
    
 10. See also


@@ -296,18 +296,17 @@ sufficient for our purposes.
 
 Some common elements that you likely will use:
 
 
 Some common elements that you likely will use:
 

-, paragraph delimiter. Most text needs to be within paragraph elements (there  
-are some exceptions).                                                          
-, the stylesheets make this italics.                                           
-, files and directories.                                                       
-, command examples.                                                            
-, like                                                                         
-, more or less.                                                                
-, list with bullets.                                                           
-, member of the above.                                                         
-, screen output, implies .                                                     
-, like HTML tag.                                                               
-, for, doh, quoting text.                                                      
+<para></para>, paragraph delimiter. Most text needs to be within paragraph     
+elements (there are some exceptions).                                          
+<emphasis></emphasis>, the stylesheets make this italics.                      
+<filename></filename>, files and directories.                                  
+<command></command>, command examples.                                         
+<literallayout></literallayout>, like <pre>, more or less.                     
+<itemizedlist></itemizedlist>, list with bullets.                              
+<listitem></listitem>, member of the above.                                    
+<screen></screen>, screen output, implies <literallayout>.                     
+<ulink url="example.com"></ulink>, like HTML <a> tag.                          
+<quote></quote>, for, doh, quoting text.                                       

 
 Look at any of the existing docs for examples of all these and more.
 
 
 Look at any of the existing docs for examples of all these and more.
 


@@ -1082,13 +1081,13 @@ other header files.
 
 Example:
 
 
 Example:
 

-#include      /* This is not a local include */                                
+#include <iostream.h>     /* This is not a local include */                    

 #include "config.h"       /* This IS a local include */                        
 
 Exception:
 
 /* This is not a local include, but requires a path element. */                
 #include "config.h"       /* This IS a local include */                        
 
 Exception:
 
 /* This is not a local include, but requires a path element. */                

-#include                                                                       
+#include <sys/fileName.h>                                                      

 
 Note: Please! do not add "-I." to the Makefile without a _very_ good reason.
 This duplicates the #include "file.h" behavior.
 
 Note: Please! do not add "-I." to the Makefile without a _very_ good reason.
 This duplicates the #include "file.h" behavior.


@@ -1371,7 +1370,7 @@ from the project).
 
 Example for file comments:
 
 
 Example for file comments:
 

-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.40 2002/05/04 00:43:43 hal9 Exp $"; 
+const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $"; 

 /*********************************************************************                          
  *                                                                                              
  * File        :  $Source$                                                                      
 /*********************************************************************                          
  *                                                                                              
  * File        :  $Source$                                                                      


@@ -1428,7 +1427,7 @@ Example for file header comments:
 
 #ifndef _FILENAME_H                                                                           
 #define _FILENAME_H                                                                           
 
 #ifndef _FILENAME_H                                                                           
 #define _FILENAME_H                                                                           

-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.40 2002/05/04 00:43:43 hal9 Exp $" 
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $" 

 /*********************************************************************                        
  *                                                                                            
  * File        :  $Source$                                                                    
 /*********************************************************************                        
  *                                                                                            
  * File        :  $Source$                                                                    


@@ -2072,14 +2071,20 @@ too. See the page on Sourceforge.
 
 -------------------------------------------------------------------------------
 
 
 -------------------------------------------------------------------------------
 

-9. Copyright and History
+9. Privoxy Copyright, License and History

 
 

-9.1. Copyright
+Copyright © 2001, 2002 by Privoxy Developers <developers@privoxy.org>
+
+Some source code is based on code Copyright © 1997 by Anonymous Coders and
+Junkbusters, Inc. and licensed under the GNU General Public License.
+
+-------------------------------------------------------------------------------
+
+9.1. License

 
 Privoxy is free software; you can redistribute it and/or modify it under the
 
 Privoxy is free software; you can redistribute it and/or modify it under the

-terms of the GNU General Public License as published by the Free Software
-Foundation; either version 2 of the License, or (at your option) any later
-version.
+terms of the GNU General Public License, version 2, as published by the Free
+Software Foundation.

 
 This program is distributed in the hope that it will be useful, but WITHOUT ANY
 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
 
 This program is distributed in the hope that it will be useful, but WITHOUT ANY
 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A


@@ -2088,8 +2093,12 @@ is available from the Free Software Foundation, Inc, 59 Temple Place - Suite
 330, Boston, MA 02111-1307, USA.
 
 You should have received a copy of the GNU General Public License along with
 330, Boston, MA 02111-1307, USA.
 
 You should have received a copy of the GNU General Public License along with

-this program; if not, write to the Free Software Foundation, Inc., 59 Temple
-Place, Suite 330, Boston, MA 02111-1307 USA.
+this program; if not, write to the
+
+ Free Software
+ Foundation, Inc. 59 Temple Place - Suite 330
+ Boston, MA 02111-1307
+ USA 

 
 -------------------------------------------------------------------------------
 
 
 -------------------------------------------------------------------------------