Docs+Packaging: Convert our man pages to Asciidoctor.

Convert doc/*.pod to Asciidoctor. This:

* Means we use the same markup for our man pages, the guides, and
  release notes.
* Lets us add versions to our man pages.
* Gives us more formatting options, e.g. AsciiDoc supports `commands`,
  nested lists and makes it easy to include version information. The
  manpage backend doesn't seem to support tables very well,
  unfortunately.

Convert our CMake configuration to produce *roff and html man pages
using Asciidoctor. Add a "manarg" block macro which makes our synopses
wrap correctly.

Similar to the release notes, guides, and FAQ, if Asciidoctor isn't
found the man pages won't be generated or installed.

Move Asciidoctor to the list of package build dependencies in various
places.

This commit includes the conversion script (pod2adoc.py), which will be
removed later.

Line count sanity check:

Man page         .pod .adoc
androiddump       260  280
asn2deb            93  105
capinfos          401  471
captype            54   55
ciscodump         241  269
dftest             42   42
dpauxmon          153  169
dumpcap           464  534
editcap           528  583
etwdump           136  156
extcap            157  181
idl2deb            91  103
idl2wrs           120  100
mergecap          206  207
mmdbresolve        75   75
randpkt           107  111
randpktdump       158  184
rawshark          558  610
reordercap         76   78
sdjournal         145  157
sshdump           272  302
text2pcap         274  312
tshark           2135 2360
udpdump           133  151
wireshark-filter  486  479
wireshark        2967 3420

1 files changed, 249 insertions, 194 deletions

diff --git a/doc/editcap.adoc b/doc/editcap.adoc
index d24576f86c..cb4445153b 100644
--- a/doc/editcap.adoc
+++ b/doc/editcap.adoc
@@ -1,105 +1,110 @@
-=begin man
+= editcap(1)
+:doctype: manpage
+include::../docbook/attributes.adoc[]
+:stylesheet: ws.css
+:linkcss:
+:copycss: ../docbook/{stylesheet}
 
-=encoding utf8
-
-=end man
-
-=head1 NAME
+== NAME
 
 editcap - Edit and/or translate the format of capture files
 
-=head1 SYNOPSIS
-
-B<editcap>
-S<[ B<-a> E<lt>frame:commentE<gt> ]>
-S<[ B<-A> E<lt>start timeE<gt> ]>
-S<[ B<-B> E<lt>stop timeE<gt> ]>
-S<[ B<-c> E<lt>packets per fileE<gt> ]>
-S<[ B<-C> [offset:]E<lt>choplenE<gt> ]>
-S<[ B<-E> E<lt>error probabilityE<gt> ]>
-S<[ B<-F> E<lt>file formatE<gt> ]>
-S<[ B<-h> ]>
-S<[ B<-i> E<lt>seconds per fileE<gt> ]>
-S<[ B<-o> E<lt>change offsetE<gt> ]>
-S<[ B<-L> ]>
-S<[ B<-r> ]>
-S<[ B<-s> E<lt>snaplenE<gt> ]>
-S<[ B<-S> E<lt>strict time adjustmentE<gt> ]>
-S<[ B<-t> E<lt>time adjustmentE<gt> ]>
-S<[ B<-T> E<lt>encapsulation typeE<gt> ]>
-S<[ B<-v> ]>
-S<[ B<--inject-secrets> E<lt>secrets typeE<gt>,E<lt>fileE<gt> ]>
-S<[ B<--discard-all-secrets> ]>
-S<[ B<--capture-comment> E<lt>commentE<gt> ]>
-S<[ B<--discard-capture-comment> ]>
-I<infile>
-I<outfile>
-S<[ I<packet#>[-I<packet#>] ... ]>
-
-B<editcap>
-S< B<-d> > |
-S< B<-D> E<lt>dup windowE<gt> > |
-S< B<-w> E<lt>dup time windowE<gt> >
-S<[ B<-v> ]>
-S<[ B<-I> E<lt>bytes to ignoreE<gt> ]>
-S<[ B<--skip-radiotap-header> ]>
-I<infile>
-I<outfile>
-
-B<editcap>
-S<[ B<-V> ]>
-
-=head1 DESCRIPTION
-
-B<Editcap> is a program that reads some or all of the captured packets from the
-I<infile>, optionally converts them in various ways and writes the
-resulting packets to the capture I<outfile> (or outfiles).
-
-By default, it reads all packets from the I<infile> and writes them to the
-I<outfile> in pcapng file format.
-
-The B<-A> and B<-B> option allow you to limit the time range from which packets
-are read from the I<infile>.
+== SYNOPSIS
+
+[manarg]
+*editcap*
+[ *-a* <frame:comment> ]
+[ *-A* <start time> ]
+[ *-B* <stop time> ]
+[ *-c* <packets per file> ]
+[ *-C* [offset:]<choplen> ]
+[ *-E* <error probability> ]
+[ *-F* <file format> ]
+[ *-h* ]
+[ *-i* <seconds per file> ]
+[ *-o* <change offset> ]
+[ *-L* ]
+[ *-r* ]
+[ *-s* <snaplen> ]
+[ *-S* <strict time adjustment> ]
+[ *-t* <time adjustment> ]
+[ *-T* <encapsulation type> ]
+[ *-v* ]
+[ *--inject-secrets* <secrets type>,<file> ]
+[ *--discard-all-secrets* ]
+[ *--capture-comment* <comment> ]
+[ *--discard-capture-comment* ]
+__infile__
+__outfile__
+[ __packet#__[-__packet#__] ... ]
+
+[manarg]
+*editcap*
+*-d*
+*-D* <dup window>
+*-w* <dup time window>
+[ *-v* ]
+[ *-I* <bytes to ignore> ]
+[ *--skip-radiotap-header* ]
+__infile__
+__outfile__
+
+[manarg]
+*editcap*
+[ *-V* ]
+
+== DESCRIPTION
+
+*Editcap* is a program that reads some or all of the captured packets from the
+__infile__, optionally converts them in various ways and writes the
+resulting packets to the capture __outfile__ (or outfiles).
+
+By default, it reads all packets from the __infile__ and writes them to the
+__outfile__ in pcapng file format.
+
+The *-A* and *-B* option allow you to limit the time range from which packets
+are read from the __infile__.
 
 An optional list of packet numbers can be specified on the command tail;
 individual packet numbers separated by whitespace and/or ranges of packet
-numbers can be specified as I<start>-I<end>, referring to all packets from
-I<start> to I<end>.  By default the selected packets with those numbers will
-I<not> be written to the capture file.  If the B<-r> flag is specified, the
-whole packet selection is reversed; in that case I<only> the selected packets
+numbers can be specified as __start__-__end__, referring to all packets from
+__start__ to __end__.  By default the selected packets with those numbers will
+__not__ be written to the capture file.  If the *-r* flag is specified, the
+whole packet selection is reversed; in that case __only__ the selected packets
 will be written to the capture file.
 
-B<Editcap> can also be used to remove duplicate packets.  Several different
-options (B<-d>, B<-D> and B<-w>) are used to control the packet window
+*Editcap* can also be used to remove duplicate packets.  Several different
+options (*-d*, *-D* and *-w*) are used to control the packet window
 or relative time window to be used for duplicate comparison.
 
-B<Editcap> can be used to assign comment strings to frame numbers.
+*Editcap* can be used to assign comment strings to frame numbers.
 
-B<Editcap> is able to detect, read and write the same capture files that
-are supported by B<Wireshark>.
+*Editcap* is able to detect, read and write the same capture files that
+are supported by *Wireshark*.
 The input file doesn't need a specific filename extension; the file
 format and an optional gzip, zstd or lz4 compression will be automatically detected.
-Near the beginning of the DESCRIPTION section of wireshark(1) or
-L<https://www.wireshark.org/docs/man-pages/wireshark.html>
-is a detailed description of the way B<Wireshark> handles this, which is
-the same way B<Editcap> handles this.
+Near the beginning of the DESCRIPTION section of xref:wireshark.html[wireshark](1) or
+https://www.wireshark.org/docs/man-pages/wireshark.html
+is a detailed description of the way *Wireshark* handles this, which is
+the same way *Editcap* handles this.
 
-B<Editcap> can write the file in several output formats. The B<-F>
+*Editcap* can write the file in several output formats. The *-F*
 flag can be used to specify the format in which to write the capture
-file; B<editcap -F> provides a list of the available output formats.
-
-=head1 OPTIONS
+file; *editcap -F* provides a list of the available output formats.
 
-=over 4
-
-=item -a  E<lt>framenum:commentE<gt>
+== OPTIONS
 
+-a  <framenum:comment>::
++
+--
 For the specified frame number, assign the given comment string.
 Can be repeated for multiple frames.  Quotes should be used with comment
 strings that include spaces.
+--
 
-=item -A  E<lt>start timeE<gt>
-
+-A  <start time>::
++
+--
 Reads only the packets whose timestamp is on or after start time.
 The time is given in ISO 8601 format, either
 YYYY-MM-DD HH:MM:SS[.nnnnnnnnn][Z|±hh:mm] or
@@ -107,9 +112,11 @@ YYYY-MM-DDTHH:MM:SS[.nnnnnnnnn][Z|±hh:mm] .
 The fractional seconds are optional, as is the time zone offset from UTC
 (in which case local time is assumed). Unix epoch timestamps
 (floating point format) are also accepted.
+--
 
-=item -B  E<lt>stop timeE<gt>
-
+-B  <stop time>::
++
+--
 Reads only the packets whose timestamp is before stop time.
 The time is given in ISO 8601 format, either
 YYYY-MM-DD HH:MM:SS[.nnnnnnnnn][Z|±hh:mm] or
@@ -117,24 +124,28 @@ YYYY-MM-DDTHH:MM:SS[.nnnnnnnnn][Z|±hh:mm] .
 The fractional seconds are optional, as is the time zone offset from UTC
 (in which case local time is assumed). Unix epoch timestamps
 (floating point format) are also accepted.
+--
 
-=item -c  E<lt>packets per fileE<gt>
-
+-c  <packets per file>::
++
+--
 Splits the packet output to different files based on uniform packet counts
 with a maximum of <packets per file> each.
 
 Each output file will be created with an infix _nnnnn[_YYYYmmddHHMMSS] inserted
-before the file extension (which may be null) of I<outfile>.  The infix
+before the file extension (which may be null) of __outfile__.  The infix
 consists of the ordinal number of the output file, starting with 00000,
 followed by the timestamp of its first packet.  The timestamp is omitted if
 the input file does not contain timestamp information.
 
 After the specified number of packets is written to the output file, the next
 output file is opened.  The default is to use a single output file.
-This option conflicts with B<-i>.
-
-=item -C  [offset:]E<lt>choplenE<gt>
+This option conflicts with *-i*.
+--
 
+-C  [offset:]<choplen>::
++
+--
 Sets the chop length to use when writing the packet data. Each packet is
 chopped by <choplen> bytes of data. Positive values chop at the packet
 beginning while negative values chop at the packet end.
@@ -153,21 +164,25 @@ bytes from up to two different areas of a packet in a single pass provided that
 you specify at least one chop length as a positive value and at least one as a
 negative value.  All positive chop lengths are added together as are all
 negative chop lengths.
+--
 
-=item -d
-
+-d::
++
+--
 Attempts to remove duplicate packets.  The length and MD5 hash of the
 current packet are compared to the previous four (4) packets.  If a
 match is found, the current packet is skipped.  This option is equivalent
-to using the option B<-D 5>.
-
-=item -D  E<lt>dup windowE<gt>
+to using the option *-D 5*.
+--
 
+-D  <dup window>::
++
+--
 Attempts to remove duplicate packets.  The length and MD5 hash of the
 current packet are compared to the previous <dup window> - 1 packets.
 If a match is found, the current packet is skipped.
 
-The use of the option B<-D 0> combined with the B<-v> option is useful
+The use of the option *-D 0* combined with the *-v* option is useful
 in that each packet's Packet number, Len and MD5 Hash will be printed
 to standard out.  This verbose output (specifically the MD5 hash strings)
 can be useful in scripts to identify duplicate packets across trace
@@ -176,75 +191,93 @@ files.
 The <dup window> is specified as an integer value between 0 and 1000000 (inclusive).
 
 NOTE: Specifying large <dup window> values with large tracefiles can
-result in very long processing times for B<editcap>.
-
-=item -E  E<lt>error probabilityE<gt>
+result in very long processing times for *editcap*.
+--
 
+-E  <error probability>::
++
+--
 Sets the probability that bytes in the output file are randomly changed.
-B<Editcap> uses that probability (between 0.0 and 1.0 inclusive)
+*Editcap* uses that probability (between 0.0 and 1.0 inclusive)
 to apply errors to each data byte in the file.  For instance, a
 probability of 0.02 means that each byte has a 2% chance of having an error.
 
 This option is meant to be used for fuzz-testing protocol dissectors.
+--
 
-=item -F  E<lt>file formatE<gt>
-
+-F  <file format>::
++
+--
 Sets the file format of the output capture file.
-B<Editcap> can write the file in several formats, B<editcap -F>
+*Editcap* can write the file in several formats, *editcap -F*
 provides a list of the available output formats. The default
-is the B<pcapng> format.
-
-=item -h
+is the *pcapng* format.
+--
 
+-h::
++
+--
 Prints the version and options and exits.
+--
 
-=item -i  E<lt>seconds per fileE<gt>
-
+-i  <seconds per file>::
++
+--
 Splits the packet output to different files based on uniform time
 intervals using a maximum interval of <seconds per file> each.  Floating
 point values (e.g. 0.5) are allowed.
 
 Each output file will be created with an infix _nnnnn[_YYYYmmddHHMMSS] inserted
-before the file extension (which may be null) of I<outfile>.  The infix
+before the file extension (which may be null) of __outfile__.  The infix
 consists of the ordinal number of the output file, starting with 00000,
 followed by the timestamp of its first packet.  The timestamp is omitted if
 the input file does not contain timestamp information.
 
 After packets for the specified time interval are written to the output file,
 the next output file is opened.  The default is to use a single output file.
-This option conflicts with B<-c>.
-
-=item -I  E<lt>bytes to ignoreE<gt>
+This option conflicts with *-c*.
+--
 
+-I  <bytes to ignore>::
++
+--
 Ignore the specified number of bytes at the beginning of the frame during MD5 hash calculation,
 unless the frame is too short, then the full frame is used.
 Useful to remove duplicated packets taken on several routers (different mac addresses for example)
 e.g. -I 26 in case of Ether/IP will ignore ether(14) and IP header(20 - 4(src ip) - 4(dst ip)).
 The default value is 0.
+--
 
-=item -L
-
+-L::
++
+--
 Adjust the original frame length accordingly when chopping and/or snapping
 (in addition to the captured length, which is always adjusted regardless of
-whether B<-L> is specified or not).  See also B<-C <choplen>> and B<-s <snaplen>>.
-
-=item -o  E<lt>change offsetE<gt>
+whether *-L* is specified or not).  See also *-C <choplen*> and *-s <snaplen*>.
+--
 
+-o  <change offset>::
++
+--
 When used in conjunction with -E, skip some bytes from the beginning of the packet
 from being changed. In this way some headers don't get changed, and the fuzzer is
 more focused on a smaller part of the packet. Keeping a part of the packet fixed
 the same dissector is triggered, that make the fuzzing more precise.
+--
 
-=item -r
-
+-r::
++
+--
 Reverse the packet selection.
 Causes the packets whose packet numbers are specified on the command
 line to be written to the output capture file, instead of discarding them.
+--
 
-=item -s  E<lt>snaplenE<gt>
-
+-s  <snaplen>::
++
+--
 Sets the snapshot length to use when writing the data.
-If the B<-s> flag is used to specify a snapshot length, packets in the
+If the *-s* flag is used to specify a snapshot length, packets in the
 input file with more captured data than the specified snapshot length
 will have only the amount of data specified by the snapshot length
 written to the output file.
@@ -255,32 +288,38 @@ to read the output file cannot handle packets larger than a certain size
 appear to reject Ethernet packets larger than the standard Ethernet MTU,
 making them incapable of handling gigabit Ethernet captures if jumbo
 packets were used).
+--
 
-=item --seed  E<lt>seedE<gt>
-
+--seed  <seed>::
++
+--
 When used in conjunction with -E, set the seed for the pseudo-random number generator.
 This is useful for recreating a particular sequence of errors.
+--
 
-=item --skip-radiotap-header
-
+--skip-radiotap-header::
++
+--
 Skip the radiotap header of each frame when checking for packet duplicates. This is useful
 when processing a capture created by combining outputs of multiple capture devices on the same
 channel in the vicinity of each other.
+--
 
-=item -S  E<lt>strict time adjustmentE<gt>
-
+-S  <strict time adjustment>::
++
+--
 Time adjust selected packets to ensure strict chronological order.
 
 The <strict time adjustment> value represents relative seconds
-specified as [-]I<seconds>[I<.fractional seconds>].
+specified as [-]__seconds__[__.fractional seconds__].
 
 As the capture file is processed each packet's absolute time is
-I<possibly> adjusted to be equal to or greater than the previous
+__possibly__ adjusted to be equal to or greater than the previous
 packet's absolute timestamp depending on the <strict time
 adjustment> value.
 
 If <strict time adjustment> value is 0 or greater (e.g. 0.000001)
-then B<only> packets with a timestamp less than the previous packet
+then *only* packets with a timestamp less than the previous packet
 will adjusted.  The adjusted timestamp value will be set to be
 equal to the timestamp value of the previous packet plus the value
 of the <strict time adjustment> value.  A <strict time adjustment>
@@ -289,38 +328,42 @@ necessary to ensure that the resulting capture file is in
 strict chronological order.
 
 If <strict time adjustment> value is specified as a
-negative value, then the timestamp values of B<all>
+negative value, then the timestamp values of *all*
 packets will be adjusted to be equal to the timestamp value
 of the previous packet plus the absolute value of the
-E<lt>strict time adjustmentE<gt> value. A <strict time
+<strict time adjustment> value. A <strict time
 adjustment> value of -0 will result in all packets
 having the timestamp value of the first packet.
 
 This feature is useful when the trace file has an occasional
 packet with a negative delta time relative to the previous
 packet.
+--
 
-=item -t  E<lt>time adjustmentE<gt>
-
+-t  <time adjustment>::
++
+--
 Sets the time adjustment to use on selected packets.
-If the B<-t> flag is used to specify a time adjustment, the specified
+If the *-t* flag is used to specify a time adjustment, the specified
 adjustment will be applied to all selected packets in the capture file.
-The adjustment is specified as [-]I<seconds>[I<.fractional seconds>].
-For example, B<-t> 3600 advances the timestamp on selected packets by one
-hour while B<-t> -0.5 reduces the timestamp on selected packets by
+The adjustment is specified as [-]__seconds__[__.fractional seconds__].
+For example, *-t* 3600 advances the timestamp on selected packets by one
+hour while *-t* -0.5 reduces the timestamp on selected packets by
 one-half second.
 
 This feature is useful when synchronizing dumps
 collected on different machines where the time difference between the
 two machines is known or can be estimated.
+--
 
-=item -T  E<lt>encapsulation typeE<gt>
-
+-T  <encapsulation type>::
++
+--
 Sets the packet encapsulation type of the output capture file.
-If the B<-T> flag is used to specify an encapsulation type, the
+If the *-T* flag is used to specify an encapsulation type, the
 encapsulation type of the output capture file will be forced to the
 specified type.
-B<editcap -T> provides a list of the available types. The default
+*editcap -T* provides a list of the available types. The default
 type is the one appropriate to the encapsulation type of the input
 capture file.
 
@@ -329,82 +372,95 @@ forces the encapsulation type of the output file to be the specified
 type; the packet headers of the packets will not be translated from the
 encapsulation type of the input capture file to the specified
 encapsulation type (for example, it will not translate an Ethernet
-capture to an FDDI capture if an Ethernet capture is read and 'B<-T
-fddi>' is specified). If you need to remove/add headers from/to a
-packet, you will need od(1)/text2pcap(1).
-
-=item -v
+capture to an FDDI capture if an Ethernet capture is read and '*-T
+ fddi*' is specified). If you need to remove/add headers from/to a
+packet, you will need od(1)/xref:text2pcap.html[text2pcap](1).
+--
 
-Causes B<editcap> to print verbose messages while it's working.
+-v::
++
+--
+Causes *editcap* to print verbose messages while it's working.
 
-Use of B<-v> with the de-duplication switches of B<-d>, B<-D> or B<-w>
+Use of *-v* with the de-duplication switches of *-d*, *-D* or *-w*
 will cause all MD5 hashes to be printed whether the packet is skipped
 or not.
+--
 
-=item -V
-
+-V::
++
+--
 Print the version and exit.
+--
 
-=item -w  E<lt>dup time windowE<gt>
-
+-w  <dup time window>::
++
+--
 Attempts to remove duplicate packets.  The current packet's arrival time
 is compared with up to 1000000 previous packets.  If the packet's relative
-arrival time is I<less than or equal to> the <dup time window> of a previous packet
+arrival time is __less than or equal to__ the <dup time window> of a previous packet
 and the packet length and MD5 hash of the current packet are the same then
 the packet to skipped.  The duplicate comparison test stops when
 the current packet's relative arrival time is greater than <dup time window>.
 
-The <dup time window> is specified as I<seconds>[I<.fractional seconds>].
+The <dup time window> is specified as __seconds__[__.fractional seconds__].
 
 The [.fractional seconds] component can be specified to nine (9) decimal
 places (billionths of a second) but most typical trace files have resolution
 to six (6) decimal places (millionths of a second).
 
 NOTE: Specifying large <dup time window> values with large tracefiles can
-result in very long processing times for B<editcap>.
+result in very long processing times for *editcap*.
 
-NOTE: The B<-w> option assumes that the packets are in chronological order.
-If the packets are NOT in chronological order then the B<-w> duplication
+NOTE: The *-w* option assumes that the packets are in chronological order.
+If the packets are NOT in chronological order then the *-w* duplication
 removal option may not identify some duplicates.
+--
 
-=item --inject-secrets E<lt>secrets typeE<gt>,E<lt>fileE<gt>
-
-Inserts the contents of E<lt>fileE<gt> into a Decryption Secrets Block (DSB)
+--inject-secrets <secrets type>,<file>::
++
+--
+Inserts the contents of <file> into a Decryption Secrets Block (DSB)
 within the pcapng output file. This enables decryption without requiring
 additional configuration in protocol preferences.
 
-The file format is described by E<lt>secrets typeE<gt> which can be one of:
+The file format is described by <secrets type> which can be one of:
 
-I<tls>  TLS Key Log as described at L<https://developer.mozilla.org/NSS_Key_Log_Format>
-I<wg>   WireGuard Key Log, see L<https://gitlab.com/wireshark/wireshark/-/wikis/WireGuard#key-log-format>
+__tls__  TLS Key Log as described at https://developer.mozilla.org/NSS_Key_Log_Format
+__wg__   WireGuard Key Log, see https://gitlab.com/wireshark/wireshark/-/wikis/WireGuard#key-log-format
 
 This option may be specified multiple times. The available options for
-E<lt>secrets typeE<gt> can be listed with B<--inject-secrets help>.
-
-=item --discard-all-secrets
+<secrets type> can be listed with *--inject-secrets help*.
+--
 
+--discard-all-secrets::
++
+--
 Discard all decryption secrets from the input file when writing the
-output file.  Does not discard secrets added by B<--inject-secrets> in
+output file.  Does not discard secrets added by *--inject-secrets* in
 the same command line.
+--
 
-=item --capture-comment E<lt>commentE<gt>
-
+--capture-comment <comment>::
++
+--
 Adds the given comment to the output file, if supported by the output
-file format.  New comments will be added I<after> any comments present
-in the input file unless B<--discard-capture-comment> is also specified.
+file format.  New comments will be added __after__ any comments present
+in the input file unless *--discard-capture-comment* is also specified.
 
 This option may be specified multiple times.  Note that Wireshark
 currently only displays the first comment of a capture file.
+--
 
-=item --discard-capture-comment
-
+--discard-capture-comment::
++
+--
 Discard all capture file comments from the input file when writing the output
-file. Does not discard comments added by B<--capture-comment> in the same
+file. Does not discard comments added by *--capture-comment* in the same
 command line.
+--
 
-=back
-
-=head1 EXAMPLES
+== EXAMPLES
 
 To see more detailed description of the options use:
 
@@ -450,7 +506,7 @@ To remove duplicate packets seen within the prior 100 frames use:
 
     editcap -D 101 capture.pcapng dedup.pcapng
 
-To remove duplicate packets seen I<equal to or less than> 1/10th of a second:
+To remove duplicate packets seen __equal to or less than__ 1/10th of a second:
 
     editcap -w 0.1 capture.pcapng dedup.pcapng
 
@@ -502,27 +558,26 @@ To add comment strings to the first 2 input frames, use:
 
     editcap -a "1:1st frame" -a 2:Second capture.pcapng capture-comments.pcapng
 
-=head1 SEE ALSO
+== SEE ALSO
 
-pcap(3), wireshark(1), tshark(1), mergecap(1), dumpcap(1), capinfos(1),
-text2pcap(1), reordercap(1), od(1), pcap-filter(7) or tcpdump(8)
+xref:https://www.tcpdump.org/manpages/pcap.3pcap.html[pcap](3), xref:wireshark.html[wireshark](1), xref:tshark.html[tshark](1), xref:mergecap.html[mergecap](1), xref:dumpcap.html[dumpcap](1), xref:capinfos.html[capinfos](1),
+xref:text2pcap.html[text2pcap](1), xref:reordercap.html[reordercap](1), od(1), xref:https://www.tcpdump.org/manpages/pcap-filter.7.html[pcap-filter](7) or xref:https://www.tcpdump.org/manpages/tcpdump.1.html[tcpdump](8)
 
-=head1 NOTES
+== NOTES
 
-B<Editcap> is part of the B<Wireshark> distribution.  The latest version
-of B<Wireshark> can be found at L<https://www.wireshark.org>.
+*Editcap* is part of the *Wireshark* distribution.  The latest version
+of *Wireshark* can be found at https://www.wireshark.org.
 
 HTML versions of the Wireshark project man pages are available at:
-L<https://www.wireshark.org/docs/man-pages>.
-
-=head1 AUTHORS
+https://www.wireshark.org/docs/man-pages.
 
-  Original Author
-  -------- ------
-  Richard Sharpe           <sharpe[AT]ns.aus.com>
+== AUTHORS
 
+.Original Author
+[%hardbreaks]
+Richard Sharpe <sharpe[AT]ns.aus.com>
 
-  Contributors
-  ------------
-  Guy Harris               <guy[AT]alum.mit.edu>
-  Ulf Lamping              <ulf.lamping[AT]web.de>
+.Contributors
+[%hardbreaks]
+Guy Harris <guy[AT]alum.mit.edu>
+Ulf Lamping <ulf.lamping[AT]web.de>