===================================================================
RCS file: /cvs/pod2mdoc/pod2mdoc.1,v
retrieving revision 1.8
retrieving revision 1.15
diff -u -p -r1.8 -r1.15
--- pod2mdoc/pod2mdoc.1	2014/04/02 20:32:41	1.8
+++ pod2mdoc/pod2mdoc.1	2015/02/13 15:35:15	1.15
@@ -1,4 +1,4 @@
-.\"	$Id: pod2mdoc.1,v 1.8 2014/04/02 20:32:41 kristaps Exp $
+.\"	$Id: pod2mdoc.1,v 1.15 2015/02/13 15:35:15 schwarze Exp $
 .\"
 .\" Copyright (c) 2014 Kristaps Dzonsons <kristaps@bsd.lv>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: April 2 2014 $
+.Dd $Mdocdate: February 13 2015 $
 .Dt POD2MDOC 1
 .Os
 .Sh NAME
@@ -50,7 +50,7 @@ For compatibility with
 Ignored.
 .It Fl d Ar date
 Set the document date
-.Pq Sq Dd
+.Pq Sq \&Dd
 to
 .Ar date
 .Po
@@ -64,7 +64,7 @@ uses the file modification date or the current date if
 standard input.
 .It Fl n Ar title
 Set the document title
-.Pq Sq Dt
+.Pq Sq \&Dt
 to
 .Ar title .
 If unspecified,
@@ -77,7 +77,7 @@ if reading from standard input
 .Pq you probably don't want that .
 .It Fl s Ar section
 Set the document section
-.Pq Sq Dt
+.Pq Sq \&Dt
 to
 .Ar section .
 If unspecified,
@@ -101,6 +101,12 @@ Specifically, within each paragraph of the SYNOPSIS se
 following occur:
 .Bl -bullet
 .It
+If any number of
+.Li #include <foo.h>
+lines are found at the start of a verbatim paragraph, they're rendered
+with
+.Sq \&In .
+.It
 An initial
 .Li B<>
 format code is rendered as
@@ -135,7 +141,7 @@ Thus, the input
 .Li B<foo> [B<-bar baz>]
 is rendered as follows:
 .Bd -literal
-\&.Nm foo 
+\&.Nm foo
 \&.Oo
 \&.Fl bar Ar baz
 \&.Oc
@@ -158,6 +164,48 @@ will be rendered as follows:
 .Ed
 .Pp
 Multiple names separated by a comma are properly handled.
+.Pp
+In any section, the
+.Li L<>
+format code is considered a
+.Sq \&Lk
+link if beginning with
+.Li http: ,
+.Li https: ,
+.Li ftp: ,
+.Li sftp: ,
+.Li smb: ,
+or
+.Li afs: .
+If beginning with
+.Li mailto: ,
+it is considered a
+.Sq \&Mt
+link.
+Otherwise, it is considered a
+.Sq \&Xr
+manpage in section 3P if containing double-colons or section 1
+otherwise.
+The section may be overriden as
+.Li L<foo(5)> .
+If only a section appears, such as in
+.Li </section> ,
+the link is rendered with
+.Sq \&Sx .
+.Pp
+Words followed by
+.Qq Pq
+that match function names listed in the SYNOPSIS section are marked up with
+.Sq \&Fn .
+.Pp
+If the contents of a
+.Li B<>
+format code matches a type name mentioned in the SYNOPSIS section,
+it is rendered as
+.Sq \&Vt .
+If it matches a function argument name mentioned there,
+it is rendered as
+.Sq \&Fa .
 .Sh EXIT STATUS
 .Ex -std
 .Sh EXAMPLES
@@ -201,13 +249,12 @@ does, append a POD ERRORS section in the output manpag
 .Sh AUTHORS
 .Nm
 was written by
-.Ar Kristaps Dzonsons ,
-.Mt kristaps@bsd.lv .
+.An Kristaps Dzonsons Aq Mt kristaps@bsd.lv .
 .Sh CAVEATS
 By way of being a presentational language, POD is not well-represented
 by
 .Xr mdoc 7 .
-Semantic content will be necessarily lost.
+Semantic content must be inferred and may be wrong.
 .Pp
 .Nm
 only supports the named
@@ -225,9 +272,6 @@ The
 .Li S<>
 escape is discarded.
 .Pp
-Lastly, only the
-.Li L<Perl::Manpage>
-and
-.Li L<manpage(1)>
-links are understood and properly rendered as
-.Sq \&Xr .
+Unless solely a section link, the text and section parts of
+.Li L<text|link/section>
+are discarded.