X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fdeveloper-manual.sgml;h=ce6aa421e46b7fce1bc79977ac33461d95f7f1ac;hb=871d2748df537ed2d2dc21dc45836a754aaa264e;hp=1376edcf4854b7c664d1cf9f1c666c03ecc6c8f0;hpb=c854049f3f2062748a25f1d57e96b78bd93578e0;p=privoxy.git
diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml
index 1376edcf..ce6aa421 100644
--- a/doc/source/developer-manual.sgml
+++ b/doc/source/developer-manual.sgml
@@ -5,10 +5,7 @@
-
-
-
-
+
@@ -24,7 +21,7 @@
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: developer-manual.sgml,v 2.48 2012/03/20 13:05:39 fabiankeil Exp $
+ $Id: developer-manual.sgml,v 2.57 2013/03/01 17:44:24 fabiankeil Exp $
Copyright (C) 2001-2012 Privoxy Developers http://www.privoxy.org/
See LICENSE.
@@ -45,13 +42,14 @@
- Copyright &my-copy; 2001-2009 by
+ Copyright
+ &my-copy; 2001-2013 by
Privoxy Developers
- $Id: developer-manual.sgml,v 2.48 2012/03/20 13:05:39 fabiankeil Exp $
+ $Id: developer-manual.sgml,v 2.57 2013/03/01 17:44:24 fabiankeil Exp $
@@ -1801,10 +1800,10 @@ static void unload_re_filterfile(void *f) { ... }
Example for file comments:
-const char FILENAME_rcs[] = "$Id$";
+const char FILENAME_rcs[] = "$I<!-- Break CVS Substitution -->d$";
/*********************************************************************
*
- * File : $Source$
+ * File : $S<!-- Break CVS Substitution -->ource$
*
* Purpose : (Fill me in with a good description!)
*
@@ -1855,10 +1854,10 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION;
#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id$"
+#define FILENAME_H_VERSION "$I<!-- Break CVS Substitution -->d$"
/*********************************************************************
*
- * File : $Source$
+ * File : $S<!-- Break CVS Substitution -->ource$
*
* Purpose : (Fill me in with a good description!)
*
@@ -2151,7 +2150,7 @@ at sourceforge. Three simple steps:
Finished docs should be then be committed to CVS (for those
without the ability to build these). Some docs may require
rather obscure processing tools. config,
- the man page (and the html version of the man page), and the PDF docs
+ the man page (and the html version of the man page)
fall in this category. REAMDE, the man page, AUTHORS, and config
should all also be committed to CVS for other packagers. The
formal docs should be uploaded to the webserver. See the
@@ -2729,7 +2728,7 @@ at sourceforge. Three simple steps:
The module contains complete instructions on its usage in its
- README file. The end result will be the the
+ README file. The end result will be the
exported version of Privoxy installed on the build machine.
@@ -2935,14 +2934,13 @@ at sourceforge. Three simple steps:
- make dok dok-pdf # (or 'make redhat-dok dok-pdf' if 'make dok' doesn't work for you)
+ make dok
That will generate doc/webserver/user-manual,
doc/webserver/developer-manual,
doc/webserver/faq,
- doc/pdf/*.pdf and
doc/webserver/index.html automatically.
@@ -2979,46 +2977,6 @@ at sourceforge. Three simple steps:
-
- Contacting the developers, Bug Reporting and Feature Requests
-
- &contacting;
-
-
-
-
-
-Privoxy Copyright, License and History
-
-
- ©right;
-
-
-
-License
-
- &license;
-
-
-
-
-
-History
-
- &history;
-
-
-
-
-
-
- See also
-
- &seealso;
-
-
-
-