From 6e1450955c9fac7b1edd19f119ff75bd6dd38fdb Mon Sep 17 00:00:00 2001 From: Jan Engelhardt Date: Tue, 24 Oct 2023 15:00:42 +0200 Subject: man: encode emdash the way groff/man requires it Unlike LaTeX, two/three U+002D in the source do not translate to an en and em-dash in man. Using \(en and \(em, respectively, addresses this. Signed-off-by: Jan Engelhardt Signed-off-by: Phil Sutter --- extensions/libxt_hashlimit.man | 2 +- extensions/libxt_limit.man | 2 +- extensions/libxt_rateest.man | 2 +- extensions/libxt_time.man | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) (limited to 'extensions') diff --git a/extensions/libxt_hashlimit.man b/extensions/libxt_hashlimit.man index 627fcd0a..b95a52d2 100644 --- a/extensions/libxt_hashlimit.man +++ b/extensions/libxt_hashlimit.man @@ -20,7 +20,7 @@ Maximum initial number of packets to match: this number gets recharged by one every time the limit specified above is not reached, up to this number; the default is 5. When byte-based rate matching is requested, this option specifies the amount of bytes that can exceed the given rate. This option should be used -with caution -- if the entry expires, the burst value is reset too. +with caution \(em if the entry expires, the burst value is reset too. .TP \fB\-\-hashlimit\-mode\fP {\fBsrcip\fP|\fBsrcport\fP|\fBdstip\fP|\fBdstport\fP}\fB,\fP... A comma-separated list of objects to take into consideration. If no diff --git a/extensions/libxt_limit.man b/extensions/libxt_limit.man index 6fb94ccf..b477dd94 100644 --- a/extensions/libxt_limit.man +++ b/extensions/libxt_limit.man @@ -4,7 +4,7 @@ It can be used in combination with the .B LOG target to give limited logging, for example. .PP -xt_limit has no negation support - you will have to use \-m hashlimit ! +xt_limit has no negation support \(em you will have to use \-m hashlimit ! \-\-hashlimit \fIrate\fP in this case whilst omitting \-\-hashlimit\-mode. .TP \fB\-\-limit\fP \fIrate\fP[\fB/second\fP|\fB/minute\fP|\fB/hour\fP|\fB/day\fP] diff --git a/extensions/libxt_rateest.man b/extensions/libxt_rateest.man index 367b8d09..e5bcae3f 100644 --- a/extensions/libxt_rateest.man +++ b/extensions/libxt_rateest.man @@ -68,7 +68,7 @@ The names of the two rate estimators for relative mode. \fB\-\-rateest\-pps2\fP [\fIvalue\fP] Compare the estimator(s) by bytes or packets per second, and compare against the chosen value. See the above bullet list for which option is to be used in -which case. A unit suffix may be used - available ones are: bit, [kmgt]bit, +which case. A unit suffix may be used \(em available ones are: bit, [kmgt]bit, [KMGT]ibit, Bps, [KMGT]Bps, [KMGT]iBps. .PP Example: This is what can be used to route outgoing data connections from an diff --git a/extensions/libxt_time.man b/extensions/libxt_time.man index 4c0cae06..5b749a48 100644 --- a/extensions/libxt_time.man +++ b/extensions/libxt_time.man @@ -58,7 +58,7 @@ rest of the system uses). The caveat with the kernel timezone is that Linux distributions may ignore to set the kernel timezone, and instead only set the system time. Even if a particular distribution does set the timezone at boot, it is usually does not -keep the kernel timezone offset - which is what changes on DST - up to date. +keep the kernel timezone offset \(em which is what changes on DST \(em up to date. ntpd will not touch the kernel timezone, so running it will not resolve the issue. As such, one may encounter a timezone that is always +0000, or one that is wrong half of the time of the year. As such, \fBusing \-\-kerneltz is highly -- cgit v1.2.3