add some information to the "Output File Formats" section
authorulfl <ulfl@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 15 Jun 2006 19:13:47 +0000 (19:13 +0000)
committerulfl <ulfl@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 15 Jun 2006 19:13:47 +0000 (19:13 +0000)
git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@18474 f5534014-38df-0310-8fa8-9805f1628bb7

docbook/wsug_src/WSUG_chapter_io.xml

index e7475cd0045c9a9ccb149637a5678da6d2857f94..61658be01e3c7ee8dee1a9ba86d1c25a0c38bf81 100644 (file)
   <section id="ChIOOutputFormatsSection">
     <title>Output File Formats</title>
     <para>
   <section id="ChIOOutputFormatsSection">
     <title>Output File Formats</title>
     <para>
-       The following file formats can be saved by <application>Wireshark</application>,
-       so other capture tools can read the capture data from:
+       Wireshark can save the packet data in it's "native" file format (libpcap) and 
+       in the file formats of some other protocol analyzers, so other tools can read 
+       the capture data.
+    </para>
+       <warning><title>Warning!</title>
+       <para>
+       The conversion to a different file format may reduce the time stamp accuracy, 
+       see the <xref linkend="ChAdvTimestamps"/> for details.
+       </para>
+       </warning>
+    <para>
+       The following file formats can be saved by <application>Wireshark</application>:
        <itemizedlist>
        <itemizedlist>
-             <listitem><para>libpcap (tcpdump)</para></listitem>
+             <listitem><para>libpcap, tcpdump and various other tools using tcpdump's capture format</para></listitem>
              <listitem><para>Novell LANalyzer</para></listitem>
              <listitem><para>Network Associates Sniffer</para></listitem>
              <listitem><para>Sun snoop</para></listitem>
              <listitem><para>Novell LANalyzer</para></listitem>
              <listitem><para>Network Associates Sniffer</para></listitem>
              <listitem><para>Sun snoop</para></listitem>
              <listitem><para>HP-UX's nettl</para></listitem>
        </itemizedlist>
     </para>
              <listitem><para>HP-UX's nettl</para></listitem>
        </itemizedlist>
     </para>
-       <note><title></title>
+    <para>
+       If the above tools will be more helpful than Wireshark is a different question ;-)
+    </para>
+       <note><title>Note!</title>
        <para>
        <para>
-       Other protocol analyzers may require that the file has a certain suffix 
-       in order to read the files you generate with Wireshark, e.g.:
+       Other protocol analyzers than Wireshark may require that the file has a 
+       certain suffix in order to read the files you generate with Wireshark, e.g.:
        </para>
        <para>
        ".DMP" for Tcpdump/libpcap
        </para>
        <para>
        ".DMP" for Tcpdump/libpcap