parse_numeric_value(): Expect a base-ten number

[privoxy.git] / privoxy.8

diff --git a/privoxy.8 b/privoxy.8
index b7d0480..6ca56b4 100644 (file)
--- a/privoxy.8
+++ b/privoxy.8
@@ -1,6 +1,6 @@
 .\" This manpage has been generated by docbook2man-spec.pl
 .\" (included in the Privoxy source tarball) from a DocBook document.
 .\" This manpage has been generated by docbook2man-spec.pl
 .\" (included in the Privoxy source tarball) from a DocBook document.

-.TH "PRIVOXY" "8" "03 February 2021" "Privoxy 3.0.32 UNRELEASED" ""
+.TH "PRIVOXY" "8" "05 February 2023" "Privoxy 3.0.34" ""

 .SH NAME
 privoxy \- Privacy Enhancing Proxy
 .SH SYNOPSIS
 .SH NAME
 privoxy \- Privacy Enhancing Proxy
 .SH SYNOPSIS


@@ -172,9 +172,6 @@ automatically. Signals other than the ones listed above aren't explicitly
 handled and result in the default action defined by the operating system.
 .SH "NOTES"
 .PP
 handled and result in the default action defined by the operating system.
 .SH "NOTES"
 .PP

-This is a UNRELEASED version of \fBPrivoxy\fR. Not
-all features are well tested.
-.PP

 Please see the \fIUser Manual\fR on how to contact the
 developers, for feature requests, reporting problems, and other questions.
 .SH "SEE ALSO"
 Please see the \fIUser Manual\fR on how to contact the
 developers, for feature requests, reporting problems, and other questions.
 .SH "SEE ALSO"


@@ -213,7 +210,7 @@ configuration related suggestions to the developers.
 .SH "COPYRIGHT AND LICENSE"
 .SS "COPYRIGHT"
 .PP
 .SH "COPYRIGHT AND LICENSE"
 .SS "COPYRIGHT"
 .PP

-Copyright (C) 2001-2021 by Privoxy Developers <privoxy-devel@lists.privoxy.org>
+Copyright (C) 2001-2023 by Privoxy Developers <privoxy-devel@lists.privoxy.org>

 .PP
 Some source code is based on code Copyright (C) 1997 by Anonymous Coders
 and Junkbusters, Inc.
 .PP
 Some source code is based on code Copyright (C) 1997 by Anonymous Coders
 and Junkbusters, Inc.


@@ -227,7 +224,8 @@ of the license, or (at your option) any later version.
 .PP
 The same is true for \fBPrivoxy\fR binaries
 unless they are linked with a
 .PP
 The same is true for \fBPrivoxy\fR binaries
 unless they are linked with a

-mbed TLS version
+mbed TLS or
+OpenSSL version

 that is licensed under the Apache 2.0 license in which
 case you can redistribute and/or modify the \fBPrivoxy\fR
 binaries under the terms of the \fIGNU General Public License\fR
 that is licensed under the Apache 2.0 license in which
 case you can redistribute and/or modify the \fBPrivoxy\fR
 binaries under the terms of the \fIGNU General Public License\fR