test1173: make it also check all libcurl option man pages

... and adjust those that cause errors

Closes #4116

docs/libcurl/opts/CURLINFO_TLS_SSL_PTR.3

@@ -95,26 +95,26 @@ If the \fIinternals\fP pointer is NULL then either the SSL backend is not
 supported, an SSL session has not yet been established or the connection is no
 longer associated with the easy handle (eg curl_easy_perform has returned).
 .SH LIMITATIONS
-\fBThis option has some limitations that could make it unsafe when it comes to
+This option has some limitations that could make it unsafe when it comes to
-the manual verification of certificates.\fP
+the manual verification of certificates.
 
 This option only retrieves the first in-use SSL session pointer for your easy
 handle, however your easy handle may have more than one in-use SSL session if
 using FTP over SSL. That is because the FTP protocol has a control channel and
-a data channel and one or both may be over SSL. \fBCurrently there is no way to
+a data channel and one or both may be over SSL. Currently there is no way to
-retrieve a second in-use SSL session associated with an easy handle.\fP
+retrieve a second in-use SSL session associated with an easy handle.
 
-This option has not been thoroughly tested with plaintext protocols that can be
+This option has not been thoroughly tested with plaintext protocols that can
-upgraded/downgraded to/from SSL: FTP, SMTP, POP3, IMAP when used with
+be upgraded/downgraded to/from SSL: FTP, SMTP, POP3, IMAP when used with
 \fICURLOPT_USE_SSL(3)\fP. Though you will be able to retrieve the SSL pointer,
-it's possible that before you can do that \fBdata (including auth) may have
+it's possible that before you can do that data (including auth) may have
-already been sent over a connection after it was upgraded.\fP
+already been sent over a connection after it was upgraded.
 
 Renegotiation. If unsafe renegotiation or renegotiation in a way that the
 certificate is allowed to change is allowed by your SSL library this may occur
-and the certificate may change, and \fBdata may continue to be sent or received
+and the certificate may change, and data may continue to be sent or received
 after renegotiation but before you are able to get the (possibly) changed SSL
-pointer,\fP with the (possibly) changed certificate information.
+pointer, with the (possibly) changed certificate information.
 
 If you are using OpenSSL or wolfSSL then \fICURLOPT_SSL_CTX_FUNCTION(3)\fP can
 be used to set a certificate verification callback in the CTX. That is safer

docs/libcurl/opts/CURLOPT_MAIL_RCPT.3

@@ -5,7 +5,7 @@
 .\" *                            | (__| |_| |  _ <| |___
 .\" *                             \___|\___/|_| \_\_____|
 .\" *
-.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <daniel@haxx.se>, et al.
+.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <daniel@haxx.se>, et al.
 .\" *
 .\" * This software is licensed as described in the file COPYING, which
 .\" * you should have received as part of this distribution. The terms
@@ -31,9 +31,10 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_MAIL_RCPT,
                           struct curl_slist *rcpts);
 .SH DESCRIPTION
 Pass a pointer to a linked list of recipients to pass to the server in your
-SMTP mail request. The linked list should be a fully valid list of \fBstruct
+SMTP mail request. The linked list should be a fully valid list of
-curl_slist\fP structs properly filled in. Use \fIcurl_slist_append(3)\fP to
+\fBstruct curl_slist\fP structs properly filled in. Use
-create the list and \fIcurl_slist_free_all(3)\fP to clean up an entire list.
+\fIcurl_slist_append(3)\fP to create the list and \fIcurl_slist_free_all(3)\fP
+to clean up an entire list.
 
 When performing a mail transfer, each recipient should be specified within a
 pair of angled brackets (<>), however, should you not use an angled bracket as

docs/libcurl/opts/CURLOPT_PROXY_SSL_OPTIONS.3

@@ -39,13 +39,10 @@ lessens the security, and by setting this option to 1 you ask for exactly
 that.  This option is only supported for DarwinSSL, NSS and OpenSSL.
 
 \fICURLSSLOPT_NO_REVOKE\fP tells libcurl to disable certificate revocation
-checks for those SSL backends where such behavior is present. \fBCurrently
+checks for those SSL backends where such behavior is present. This option is
-this option is only supported for Schannel (the native Windows SSL library),
+only supported for Schannel (the native Windows SSL library), with an
-with an exception in the case of Windows' Untrusted Publishers blacklist which
+exception in the case of Windows' Untrusted Publishers blacklist which it
-it seems can't be bypassed.\fP This option may have broader support to
+seems can't be bypassed.
-accommodate other SSL backends in the future.
-https://curl.haxx.se/docs/ssl-compared.html
-
 .SH DEFAULT
 0
 .SH PROTOCOLS

docs/libcurl/opts/CURLOPT_RTSP_REQUEST.3

@@ -5,7 +5,7 @@
 .\" *                            | (__| |_| |  _ <| |___
 .\" *                             \___|\___/|_| \_\_____|
 .\" *
-.\" * Copyright (C) 1998 - 2014, 2017, Daniel Stenberg, <daniel@haxx.se>, et al.
+.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <daniel@haxx.se>, et al.
 .\" *
 .\" * This software is licensed as described in the file COPYING, which
 .\" * you should have received as part of this distribution. The terms
@@ -33,15 +33,15 @@ enum values as a long in the \fIrequest\fP argument. Unless noted otherwise,
 commands require the Session ID to be initialized.
 .IP CURL_RTSPREQ_OPTIONS
 Used to retrieve the available methods of the server. The application is
-responsible for parsing and obeying the response. \fB(The session ID is not
+responsible for parsing and obeying the response. The session ID is not needed
-needed for this method.)\fP
+for this method.
 .IP CURL_RTSPREQ_DESCRIBE
 Used to get the low level description of a stream. The application should note
 what formats it understands in the \fI'Accept:'\fP header. Unless set
-manually, libcurl will automatically fill in \fI'Accept:
+manually, libcurl will automatically fill in \fI'Accept: application/sdp'\fP.
-application/sdp'\fP. Time-condition headers will be added to Describe requests
+Time-condition headers will be added to Describe requests if the
-if the \fICURLOPT_TIMECONDITION(3)\fP option is active. \fB(The session ID is
+\fICURLOPT_TIMECONDITION(3)\fP option is active. \fB(The session ID is not
-not needed for this method)\fP
+needed for this method)\fP
 .IP CURL_RTSPREQ_ANNOUNCE
 When sent by a client, this method changes the description of the session. For
 example, if a client is using the server to record a meeting, the client can
@@ -53,8 +53,8 @@ Setup is used to initialize the transport layer for the session. The
 application must set the desired Transport options for a session by using the
 \fICURLOPT_RTSP_TRANSPORT(3)\fP option prior to calling setup. If no session
 ID is currently set with \fICURLOPT_RTSP_SESSION_ID(3)\fP, libcurl will
-extract and use the session ID in the response to this request. \fB(The
+extract and use the session ID in the response to this request. The session ID
-session ID is not needed for this method).\fP
+is not needed for this method.
 .IP CURL_RTSPREQ_PLAY
 Send a Play command to the server. Use the \fICURLOPT_RANGE(3)\fP option to
 modify the playback time (e.g. 'npt=10-15').

docs/libcurl/opts/CURLOPT_RTSP_STREAM_URI.3

@@ -5,7 +5,7 @@
 .\" *                            | (__| |_| |  _ <| |___
 .\" *                             \___|\___/|_| \_\_____|
 .\" *
-.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <daniel@haxx.se>, et al.
+.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <daniel@haxx.se>, et al.
 .\" *
 .\" * This software is licensed as described in the file COPYING, which
 .\" * you should have received as part of this distribution. The terms
@@ -42,7 +42,7 @@ examples might be set to \fIrtsp://foo/twister\fP
 The application does not have to keep the string around after setting this
 option.
 .SH DEFAULT
-'*'
+\&'*'
 .SH PROTOCOLS
 RTSP
 .SH EXAMPLE

docs/libcurl/opts/CURLOPT_SSL_OPTIONS.3

@@ -41,12 +41,10 @@ This option is only supported for DarwinSSL, NSS and OpenSSL.
 Added in 7.44.0:
 
 \fICURLSSLOPT_NO_REVOKE\fP tells libcurl to disable certificate revocation
-checks for those SSL backends where such behavior is present. \fBCurrently this
+checks for those SSL backends where such behavior is present. This option is
-option is only supported for Schannel (the native Windows SSL library), with an
+only supported for Schannel (the native Windows SSL library), with an
-exception in the case of Windows' Untrusted Publishers blacklist which it seems
+exception in the case of Windows' Untrusted Publishers blacklist which it
-can't be bypassed.\fP This option may have broader support to accommodate other
+seems can't be bypassed.
-SSL backends in the future.
-https://curl.haxx.se/docs/ssl-compared.html
 .SH DEFAULT
 0
 .SH PROTOCOLS

tests/data/test1173

@@ -19,7 +19,7 @@ Basic man page syntax check
  </name>
 
 <command type="perl">
-%SRCDIR/manpage-syntax.pl %SRCDIR/../docs/*.1  %SRCDIR/../docs/libcurl/*.3
+%SRCDIR/manpage-syntax.pl %SRCDIR/../docs/*.1  %SRCDIR/../docs/libcurl/*.3 %SRCDIR/../docs/libcurl/opts/*.3
 </command>
 </client>