generated

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

diff --git a/doc/text/user-manual.txt b/doc/text/user-manual.txt
index e86afeb..ebc0bba 100644 (file)
--- 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