From Martin Warnes: support for VMS UCX$TRACE output in wiretap.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@7692 f5534014-38df-0310-8fa8-9805f1628bb7

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/editcap.pod b/doc/editcap.pod
index f8cf7ec97f..a3cbf5ffa9 100644
--- a/doc/editcap.pod
+++ b/doc/editcap.pod
@@ -33,14 +33,14 @@ WAN/LAN analyzer, B<Lucent/Ascend> router debug output, HP-UX's
 B<nettl>, the dump output from B<Toshiba's> ISDN routers, the output
 from B<i4btrace> from the ISDN4BSD project, the output in B<IPLog>
 format from the Cisco Secure Intrusion Detection System, B<pppd logs>
-(pppdump format), the output from VMS's B<TCPIPtrace> utility, the text
-output from the B<DBS Etherwatch> VMS utility, traffic capture files
-from Visual Networks' Visual UpTime and the output from B<CoSine> L2 
-debug. There is no need to tell B<Editcap> what type of file you are 
-reading; it will determine the file type by itself.  B<Editcap> is also 
-capable of reading any of these file formats if they are compressed 
-using gzip.  B<Editcap> recognizes this directly from the file; the 
-'.gz' extension is not required for this purpose.
+(pppdump format), the output from VMS's B<TCPIPtrace> and B<UCX$TRACE>
+utilities, the text output from the B<DBS Etherwatch> VMS utility,
+traffic capture files from Visual Networks' Visual UpTime and the output
+from B<CoSine> L2 debug.  There is no need to tell B<Editcap> what type
+of file you are reading; it will determine the file type by itself. 
+B<Editcap> is also capable of reading any of these file formats if they
+are compressed using gzip.  B<Editcap> recognizes this directly from the
+file; the '.gz' extension is not required for this purpose.
 
 By default, it writes the capture file in B<libpcap> format, and writes
 all of the packets in the capture file to the output file.  The B<-F>