All formal documents are maintained in Docbook SGML and located in the doc/source/* directory. You will need doc/source/* directory. You will need Docbook, the Docbook DTD's and the Docbook modular stylesheets (or comparable alternatives), and either jade or openjade (recommended) installed in order to build docs from source. Currently there is config requires some special handling. The reason it is maintained this way is so that the extensive comments in the file mirror those in user-manual. But the conversion process requires going from SGML to HTML to text to special formatting required for the embedded comments. Some of this - does not survive so well. Especially some of the examples that are longer than 80 characters. The build process for - this file outputs to config.new, which should be reviewed for errors and mis-formatting. - Once satisfied that it is correct, then it should be hand copied to config.
+ does not survive so well. Especially some of the examples that are longer than 80 characters.Other, less formal documents (e.g. LICENSE) are maintained as plain text files in the top-level source directory.
Packagers are encouraged to include this documentation. For those without the ability to build the docs locally, @@ -63,7 +61,7 @@
Run make webserver which copies all files from doc/webserver to the sourceforge webserver via scp.
+ "COMPUTEROUTPUT">doc/webserver to the sourceforge webserver via ssh.Finished docs should be occasionally submitted to Git (doc/webserver/*/*.html) so that @@ -209,7 +207,7 @@
Privoxy documentation is using a number of customized "entities" to facilitate documentation maintenance.
We are using a set of "boilerplate" files with generic text, that is used by