pod2mdoc/pod2mdoc.1 - diff

Return to pod2mdoc.1 CVS log

Up to [cvsweb.bsd.lv] / pod2mdoc

Diff for /pod2mdoc/pod2mdoc.1 between version 1.8 and 1.11

-version 1.8, 2014/04/02 20:32:41
+version 1.11, 2014/04/03 11:55:01
 Line 158  will be rendered as follows:
 Line 158  will be rendered as follows:
 Line 158  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 .
  .Sh EXIT STATUS
  .Ex -std
  .Sh EXAMPLES
-Line 207  was written by
+Line 235  was written by
 Line 207  was written by
 Line 235  was written by
  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
-Line 225  The
+Line 253  The
 Line 225  The
 Line 253  The
  .Li S<>
  escape is discarded.
  .Pp
- Lastly, only the
+ Unless solely a section link, the text and section parts of
- .Li L<Perl::Manpage>
+ .Li L<text|link/section>
- and
+ are discarded.
- .Li L<manpage(1)>
+ Moreover, nested format codes, e.g.
- links are understood and properly rendered as
+ .Li L<B<foo>|bar> ,
- .Sq \&Xr .
+ are not supported.

CVSweb