From 0fe95c6387d3cd7173ad01a09acd06c111b189fe Mon Sep 17 00:00:00 2001 From: swa Date: Wed, 10 Apr 2002 18:45:15 +0000 Subject: [PATCH] generated --- README | 26 +++++---- doc/source/authors.sgml | 4 +- doc/source/developer-manual.sgml | 13 +++-- doc/source/faq.sgml | 9 ++- doc/source/privoxy-man-page.sgml | 4 +- doc/source/readme.sgml | 6 +- doc/source/user-manual.sgml | 9 ++- doc/text/developer-manual.txt | 56 ++++++++++--------- doc/text/faq.txt | 16 +++--- doc/text/user-manual.txt | 40 ++++++------- .../developer-manual/documentation.html | 12 ++-- doc/webserver/faq/index.html | 2 +- doc/webserver/faq/misc.html | 2 +- doc/webserver/index.html | 40 ++++++++----- doc/webserver/user-manual/index.html | 2 +- doc/webserver/user-manual/installation.html | 18 +++--- doc/webserver/user-manual/introduction.html | 2 +- 17 files changed, 146 insertions(+), 115 deletions(-) diff --git a/README b/README index 1dc2a34b..bb5bb1d8 100644 --- a/README +++ b/README @@ -33,7 +33,7 @@ *********************************************************************/ -This README is included with the development version of Privoxy 2.9.14, which +This README is included with the development version of Privoxy 2.9.13, which will eventually become Privoxy v3.0 (and soon we hope!). See http:// www.privoxy.org/ for more information. The current code level is beta, and seems stable to us :). @@ -76,8 +76,8 @@ There are several ways to install Privoxy. To build Privoxy from source, autoconf and GNU make (gmake) are required. Source is available as gzipped tar archives. For this, first unpack the source: - tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz] - cd privoxy-2.9.14-beta + tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz] + cd privoxy-2.9.13-beta For retrieving the current CVS sources, you'll need the CVS package installed @@ -176,12 +176,12 @@ note: * Use the Sourceforge Support Forum to get help: - http://sourceforge.net/tracker/?group_id=11118&atid=211118 + http://sourceforge.net/tracker/?group_id=11118&atid=211118 * Submit bugs only through our Sourceforge Bug Forum: - http://sourceforge.net/tracker/?group_id=11118&atid=111118. + http://sourceforge.net/tracker/?group_id=11118&atid=111118. Make sure that the bug has not already been submitted. Please try to verify @@ -193,19 +193,21 @@ note: platform, browser, any pertinent log data, any other relevant details (please be specific) and, if possible, some way to reproduce the bug. - * Submit feature requests only through our Sourceforge feature request - forum: + * Submit feature requests only through our Sourceforge feature request forum: - http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse. + http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse. - * We will soon have an automated way to submit advertisements, incorrectly - blocked images, popups and the like. Check back. + * Submit missed ads and banners, and incorrectly blocked images, popups, etc: + + http://p.p/, and select "actions file feedback system" + This page can also be reached from many of the internal CGI pages. + * For any other issues, feel free to use the mailing lists: - http://sourceforge.net/mail/?group_id=11118. + http://sourceforge.net/mail/?group_id=11118. Anyone interested in actively participating in development and related @@ -216,5 +218,5 @@ note: ijbswa-developers@lists.sourceforge.net -$Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $ +$Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $ diff --git a/doc/source/authors.sgml b/doc/source/authors.sgml index 9c6d41ab..dca67337 100644 --- a/doc/source/authors.sgml +++ b/doc/source/authors.sgml @@ -3,7 +3,7 @@ Purpose : AUTHORS file for Privoxy - $Id: authors.sgml,v 1.2 2002/04/08 20:48:37 swa Exp $ + $Id: authors.sgml,v 1.3 2002/04/08 22:59:26 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -30,7 +30,7 @@ - + diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 8a5af0ce..5d062d18 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -7,7 +7,7 @@ - + @@ -21,7 +21,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $ + $Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -44,7 +44,7 @@ Privoxy Developer Manual - $Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $ + $Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $ @@ -1628,7 +1628,7 @@ static void unload_re_filterfile( void *f ) { ... } Example for file comments: -const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $"; +const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $"; /********************************************************************* * * File : $Source$ @@ -1688,7 +1688,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $" +#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $" /********************************************************************* * * File : $Source$ @@ -2414,6 +2414,9 @@ zip -r privoxyosx_setup_x.y.z.zip Privoxy.pkg Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: developer-manual.sgml,v $ + Revision 1.28 2002/04/08 22:59:26 hal9 + Version update. Spell chkconfig correctly :) + Revision 1.27 2002/04/08 15:31:18 hal9 Touch ups to documentation section. diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 0a40591f..e80e5706 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -7,7 +7,7 @@ - + @@ -22,7 +22,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $ + $Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -60,7 +60,7 @@ Privoxy Frequently Asked Questions -$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $ +$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $ @@ -1443,6 +1443,9 @@ FIXME: Commented out until we have something to put here. HB 03/18/02. Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: faq.sgml,v $ +Revision 1.47 2002/04/10 04:05:32 hal9 +More on BML, etc. + Revision 1.45 2002/04/08 22:59:26 hal9 Version update. Spell chkconfig correctly :) diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index de360e56..8bb1599b 100644 --- a/doc/source/privoxy-man-page.sgml +++ b/doc/source/privoxy-man-page.sgml @@ -5,7 +5,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: privoxy-man-page.sgml,v 1.2 2002/04/08 20:49:10 swa Exp $ + $Id: privoxy-man-page.sgml,v 1.3 2002/04/08 22:59:26 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -43,7 +43,7 @@ - + diff --git a/doc/source/readme.sgml b/doc/source/readme.sgml index 1ebffc4b..112655ca 100644 --- a/doc/source/readme.sgml +++ b/doc/source/readme.sgml @@ -4,7 +4,7 @@ - + @@ -17,7 +17,7 @@ Purpose : README for Privoxy - $Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $ + $Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -262,7 +262,7 @@ - $Id: readme.sgml,v 1.5 2002/04/08 20:49:38 swa Exp $ + $Id: readme.sgml,v 1.6 2002/04/08 22:59:26 hal9 Exp $ diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index 8f106ba3..a8d9e186 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -8,7 +8,7 @@ - + @@ -24,7 +24,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $ + $Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -47,7 +47,7 @@ Privoxy User Manual -$Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $ +$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $ @@ -3957,6 +3957,9 @@ Requests Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: user-manual.sgml,v $ + Revision 1.72 2002/04/10 04:06:19 hal9 + Added actions feedback to Bookmarklets section + Revision 1.71 2002/04/08 22:59:26 hal9 Version update. Spell chkconfig correctly :) diff --git a/doc/text/developer-manual.txt b/doc/text/developer-manual.txt index 1a807941..fd738596 100644 --- a/doc/text/developer-manual.txt +++ b/doc/text/developer-manual.txt @@ -2,7 +2,7 @@ Privoxy Developer Manual By: Privoxy Developers -$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $ +$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 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. @@ -231,17 +231,18 @@ sufficient for our purposes. 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.                                       
+, 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.                                                      
 
 Look at any of the existing docs for examples of all these and more.
 
@@ -1012,13 +1013,13 @@ other header files.
 
 Example:
 
-#include      /* This is not a local include */                    
+#include      /* 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                                                       
+#include                                                                       
 
 Note: Please! do not add "-I." to the Makefile without a _very_ good reason.
 This duplicates the #include "file.h" behaviour.
@@ -1301,7 +1302,7 @@ from the project).
 
 Example for file comments:
 
-const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $"; 
+const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $"; 
 /*********************************************************************                          
  *                                                                                              
  * File        :  $Source$                                                                      
@@ -1357,7 +1358,7 @@ Example for file header comments:
 
 #ifndef _FILENAME_H                                                                           
 #define _FILENAME_H                                                                           
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.27 2002/04/08 15:31:18 hal9 Exp $" 
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.28 2002/04/08 22:59:26 hal9 Exp $" 
 /*********************************************************************                        
  *                                                                                            
  * File        :  $Source$                                                                    
@@ -1877,12 +1878,12 @@ note:
 
   *  Use the Sourceforge Support Forum to get help:
        
-     http://sourceforge.net/tracker/?group_id=11118&atid=211118
+        http://sourceforge.net/tracker/?group_id=11118&atid=211118
        
    
   *  Submit bugs only through our Sourceforge Bug Forum:
      
-     http://sourceforge.net/tracker/?group_id=11118&atid=111118. 
+        http://sourceforge.net/tracker/?group_id=11118&atid=111118. 
         
    
     Make sure that the bug has not already been submitted. Please try to verify
@@ -1894,19 +1895,21 @@ note:
     platform, browser, any pertinent log data, any other relevant details
     (please be specific) and, if possible, some way to reproduce the bug.
    
-  *  Submit feature requests only through our Sourceforge feature request 
-     forum:
+  *  Submit feature requests only through our Sourceforge feature request forum:
      
-     http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
+        http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse.
        
    
-  * We will soon have an automated way to submit advertisements, incorrectly
-    blocked images, popups and the like. Check back.
+  *  Submit missed ads and banners, and incorrectly blocked images, popups, etc:
+          
+        http://p.p/, and select "actions file feedback system"
        
    
+    This page can also be reached from many of the internal CGI pages.
+   
   *  For any other issues, feel free to use the mailing lists:
      
-     http://sourceforge.net/mail/?group_id=11118.
+        http://sourceforge.net/mail/?group_id=11118.
      
    
     Anyone interested in actively participating in development and related
@@ -1941,7 +1944,7 @@ Place, Suite 330, Boston, MA 02111-1307 USA.
 Privoxy is evolved, and derived from, the Internet Junkbuster, with many
 improvments and enhancements over the original.
 
-Junkbuster was originally written by Anonymous Coders and Junkbuster's
+Junkbuster was originally written by Anonymous Coders and Junkbusters
 Corporation, and was released as free open-source software under the GNU GPL. 
 Stefan Waldherr made many improvements, and started the SourceForge project
 Privoxy to rekindle development. There are now several active developers
@@ -1962,6 +1965,9 @@ Sourceforge.
 http://p.p/, access Privoxy from your browser. Alternately, http://            
 config.privoxy.org may work in some situations where the first does not.       
 
+http://p.p/, and select "actions file feedback system" to submit "misses" to   
+the developers.                                                                
+
 http://www.junkbusters.com/ht/en/cookies.html
 
 http://www.waldherr.org/junkbuster/
diff --git a/doc/text/faq.txt b/doc/text/faq.txt
index 50e9f4c9..75032934 100644
--- a/doc/text/faq.txt
+++ b/doc/text/faq.txt
@@ -2,7 +2,7 @@ Privoxy Frequently Asked Questions
 
 By: Privoxy Developers
 
-$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $
+$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $
 
 This FAQ gives users and developers alike answers to frequently asked questions
 about Privoxy .
@@ -124,12 +124,12 @@ Table of Contents
 
 1.1. What is this new version of Privoxy?
 
-The original Internet JunkbusterTM (tm) is a copyrighted product of Junkbusters
-Corporation. Development of this effort stopped some time ago as of version
-2.0.2. Stefan Waldherr started the ijbswa project on Sourceforge to rekindle
-development. Other developers subsequently joined with Stefan, and have since
-added many new features, refinements and enhancements. The result of this
-effort is Privoxy.
+The original Internet Junkbuster™ (tm) is a copyrighted product of 
+Junkbusters Corporation. Development of this effort stopped some time ago as of
+version 2.0.2. Stefan Waldherr started the ijbswa project on Sourceforge to
+rekindle development. Other developers subsequently joined with Stefan, and
+have since added many new features, refinements and enhancements. The result of
+this effort is Privoxy.
 
 Privoxy has evolved from the Junkbuster 2.0.2 code base, and has advanced
 significantly at this point.
@@ -687,7 +687,7 @@ Privoxy.
 
 If you have version 2.0.2, then the equivalent is http://example.com/
 show-proxy-args (but you get far less information, and you should really
-consider upgrading to 2.9.14).
+consider upgrading to 2.9.13).
 
 -------------------------------------------------------------------------------
 
diff --git a/doc/text/user-manual.txt b/doc/text/user-manual.txt
index e86afeb7..ebc0bba0 100644
--- a/doc/text/user-manual.txt
+++ b/doc/text/user-manual.txt
@@ -2,7 +2,7 @@ Privoxy User Manual
 
 By: Privoxy Developers
 
-$Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $
+$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $
 
 The user manual gives users information on how to install, configure and use
 Privoxy.
@@ -89,7 +89,7 @@ Table of Contents
 1. Introduction
 
 This documentation is included with the current beta version of Privoxy,
-v.2.9.14, and is mostly complete at this point. The most up to date reference
+v.2.9.13, and is mostly complete at this point. The most up to date reference
 for the time being is still the comments in the source files and in the
 individual configuration files. Development of version 3.0 is currently nearing
 completion, and includes many significant changes and enhancements over earlier
@@ -166,8 +166,8 @@ There are several ways to install Privoxy.
 To build Privoxy from source, autoconf and GNU make (gmake) are required.
 Source is available as gzipped tar archives. For this, first unpack the source:
 
- tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]                           
- cd privoxy-2.9.14-beta                                                        
+ tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]                           
+ cd privoxy-2.9.13-beta                                                        
                                                                                
 
 For retrieving the current CVS sources, you'll need the CVS package installed
@@ -214,13 +214,13 @@ To build Redhat RPM packages from source, install source as above. Then:
 
 This will create both binary and src RPMs in the usual places. Example:
 
-   /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+   /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
 
-   /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm
+   /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm
 
 To install, of course:
 
- rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm                  
+ rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm                  
                                                                                
 
 This will place the Privoxy configuration files in /etc/privoxy/, and log files
@@ -241,13 +241,13 @@ To build SuSE RPM packages, install source as above. Then:
 
 This will create both binary and src RPMs in the usual places. Example:
 
-   /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+   /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
 
-   /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm
+   /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm
 
 To install, of course:
 
- rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm                
+ rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm                
                                                                                
 
 This will place the Privoxy configuration files in /etc/privoxy/, and log files
@@ -259,7 +259,7 @@ in /var/log/privoxy/.
 
 Privoxy is packaged in a WarpIN self- installing archive. The self-installing
 program will be named depending on the release version, something like:
-privoxyos2_setup_2.9.14.exe. In order to install it, simply run this executable
+privoxyos2_setup_2.9.13.exe. In order to install it, simply run this executable
 or double-click on its icon and follow the WarpIN installation panels. A shadow
 of the Privoxy executable will be placed in your startup folder so it will
 start automatically whenever OS/2 starts.
@@ -449,7 +449,7 @@ Privoxy can be reached by the special URL http://p.p/ (or alternately http://
 config.privoxy.org/), which is an internal page. You will see the following
 section: 
 
-Please choose from the following options:                                      
+ Please choose from the following options:                                     
                                                                                
     * Show information about the current configuration                         
     * Show the source code version numbers                                     
@@ -2100,7 +2100,7 @@ basically what Privoxy would do if there were not any "actions" defined, i.e.
 it does nothing. Every action is disabled. This is not particularly informative
 for our purposes here. OK, next section:
 
- Matches for http://google.com:                                                
+  Matches for http://google.com:                                               
                                                                                
  { -add-header -block +deanimate-gifs -downgrade +fast-redirects               
    +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}          
@@ -2140,7 +2140,7 @@ referenced in these sections.
 And now we pull it altogether in the bottom section and summarize how Privoxy
 is appying all its "actions" to "google.com": 
 
- Final results:                                                                
+  Final results:                                                               
                                                                                
  -add-header -block -deanimate-gifs -downgrade -fast-redirects                 
  +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}            
@@ -2154,7 +2154,7 @@ is appying all its "actions" to "google.com":
 
 Now another example, "ad.doubleclick.net":
 
- { +block +image }                                                             
+  { +block +image }                                                            
   .ad.doubleclick.net                                                          
                                                                                
  { +block +image }                                                             
@@ -2181,7 +2181,7 @@ defined as "ad.doubleclick.net" is done here -- as both a "+block" and an
 One last example. Let's try "http://www.rhapsodyk.net/adsl/HOWTO/". This one is
 giving us problems. We are getting a blank page. Hmmm...
 
- Matches for http://www.rhapsodyk.net/adsl/HOWTO/:                             
+  Matches for http://www.rhapsodyk.net/adsl/HOWTO/:                            
                                                                                
  { -add-header -block +deanimate-gifs -downgrade +fast-redirects               
    +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}          
@@ -2202,7 +2202,7 @@ see why we get the blank page. We could now add a new action below this that
 explictly does not block (-block) pages with "adsl". There are various ways to
 handle such exceptions. Example:
 
- { -block }                                                                    
+  { -block }                                                                   
   /adsl                                                                        
                                                                                
                                                                                
@@ -2213,7 +2213,7 @@ such changes. Or, try using Shift+Reload.
 But now what about a situation where we get no explicit matches like we did
 with:
 
- { -block }                                                                    
+  { -block }                                                                   
   /adsl                                                                        
                                                                                
                                                                                
@@ -2225,7 +2225,7 @@ and maybe a little trial and error to isolate the offending rule. One likely
 cause would be one of the "{+filter}" actions. Try adding the URL for the site
 to one of aliases that turn off "+filter":
 
- {shop}                                                                        
+  {shop}                                                                       
  .quietpc.com                                                                  
  .worldpay.com   # for quietpc.com                                             
  .jungle.com                                                                   
@@ -2237,7 +2237,7 @@ to one of aliases that turn off "+filter":
 "{shop}" is an "alias" that expands to "{ -filter -no-cookies -no-cookies-keep
 }". Or you could do your own exception to negate filtering: 
 
- {-filter}                                                                     
+  {-filter}                                                                    
  .forbes.com                                                                   
                                                                                
                                                                                
diff --git a/doc/webserver/developer-manual/documentation.html b/doc/webserver/developer-manual/documentation.html
index 9eeab323..1112292b 100644
--- a/doc/webserver/developer-manual/documentation.html
+++ b/doc/webserver/developer-manual/documentation.html
@@ -377,7 +377,7 @@ CLASS="LITERAL"
 >  <itemizedlist></itemizedlist><itemizedlist></itemizdelist>, list with bullets.
   
     version string, e.g. "2.9.14""2.9.13".
    : the project status, either 
     "alpha""ALPHA", "beta""BETA", or "stable""STABLE".
    "not stable" releases (e.g. "beta""BETA").
    
$Id: faq.sgml,v 1.45 2002/04/08 22:59:26 hal9 Exp $
$Id: faq.sgml,v 1.47 2002/04/10 04:05:32 hal9 Exp $
 If you have version 2.0.2, then the equivalent is
  http://example.com/show-proxy-args (but you get far less information, and
- you should really consider upgrading to 2.9.14).
Copyright
History
 Use the Sourceforge Support Forum to get help:

    

- http://sourceforge.net/tracker/?group_id=11118&atid=211118 Submit bugs only through our Sourceforge Bug Forum:

  

- http://sourceforge.net/tracker/?group_id=11118&atid=111118
  •  Submit feature requests only through our Sourceforge feature request 
    
- forum:
    
+> Submit feature requests only through our Sourceforge feature request forum:
    
  
    
- http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse
  • We will soon have an automated way to submit advertisements, incorrectly
    
-blocked images, popups and the like. Check back.
    
+> Submit missed ads and banners, and incorrectly blocked images, popups, etc:
    
+      
    
+    http://p.p/, and select "actions file feedback system"
    
    
        This page can also be reached from many of the internal CGI pages.
+   
  •  For any other issues, feel free to use the mailing lists:
    
  
    
- http://sourceforge.net/mail/?group_id=11118
    Copyright
    History
    Junkbuster's
+>Junkbusters
  Corporation, and was released as free open-source software under the
  GNU GPL. 
    • $Id: user-manual.sgml,v 1.71 2002/04/08 22:59:26 hal9 Exp $
    $Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $
     tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz]
- cd privoxy-2.9.14-beta
+> tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.13-beta
  
     This will create both binary and src RPMs in the usual places. Example:
        /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
        /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
        /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm
        /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm
     To install, of course:
     rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+> rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm
  
     This will create both binary and src RPMs in the usual places. Example:
        /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
        /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
        /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm
        /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm
     To install, of course:
     rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm
+> rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm
  
    privoxyos2_setup_2.9.14.exeprivoxyos2_setup_2.9.13.exe.  In order to install it, simply
  run this executable or double-click on its icon and follow the WarpIN
  installation panels.  A shadow of the Privoxy, v.2.9.14, 
+>, v.2.9.13, 
  and is mostly complete at this point. The most up to date reference for the
  time being is still the comments in the source files and in the individual
  configuration files. Development of version 3.0 is currently nearing
-- 
2.39.2