> Am 31.03.2015 um 08:44 schrieb sam...@openvpn.net: >> From: Samuli Seppänen <sam...@openvpn.net> >> >> This patch is against the release/2.3 branch >> >> Trac: 512 >> Signed-off-by: Samuli Seppänen <sam...@openvpn.net> >> --- >> doc/openvpn.8 | 1800 >> ++++++++++++++++++++++++++++----------------------------- >> 1 file changed, 900 insertions(+), 900 deletions(-) >> >> diff --git a/doc/openvpn.8 b/doc/openvpn.8 >> index a95d353..bcd2d76 100644 >> --- a/doc/openvpn.8 >> +++ b/doc/openvpn.8 >> @@ -37,7 +37,7 @@ >> .TH openvpn 8 "17 November 2008" >> .\"********************************************************* >> .SH NAME >> -openvpn \- secure IP tunnel daemon. >> +openvpn - secure IP tunnel daemon. > I am concerned this will cause misformattings and inability to search > for options with leading dashes on some systems - I don't recall > versions, but I do know that some systems used some sort of Unicode > (soft?) hyphen for a simple non-escaped MINUS character (ASCII 0x2B). > > So, for the release/2.3 branch, NAK for now, and more questions on the > 2.4/trunk. > > My objections will be void the moment that we can be sure that those > (major) distributions that played with the Unicode outside-ASCII hyphens > in *roff have gone out of support, and supported versions no longer > modify the plain ASCII minus, but render it verbatim. Matthias: I did additional research and it seems that escaping dashes in _options_ (but nowhere else) is the correct approach, see
<https://community.openvpn.net/openvpn/ticket/512#comment:9> Any objections to this approach? -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
signature.asc
Description: OpenPGP digital signature
