Fix indent for Documentation (Tab => Spaces)

svn path=/trunk/; revision=47148

16 files changed, 9707 insertions, 9700 deletions

diff --git a/docbook/wsug_src/WSUG_app_files.xml b/docbook/wsug_src/WSUG_app_files.xml
index 11a213affa..6d254c028d 100644
--- a/docbook/wsug_src/WSUG_app_files.xml
+++ b/docbook/wsug_src/WSUG_app_files.xml
@@ -6,111 +6,111 @@
 
   <section id="ChAppFilesCaptureFilesSection"><title>Capture Files</title>
     <para>
-	To understand which information will remain available after
-	the captured packets are saved to a capture file,
-	it's helpful to know a bit about the capture file contents.
+    To understand which information will remain available after
+    the captured packets are saved to a capture file,
+    it's helpful to know a bit about the capture file contents.
     </para>
     <para>
-	Wireshark uses the libpcap file format as the default format to save
-	captured packets; this format has existed for a long time and it's pretty simple.
-	However, it has some drawbacks: it's not extensible and lacks some
-	information that would be really helpful (e.g. being able to add a comment
-	to a packet such as "the problems start here" would be really nice).
+    Wireshark uses the libpcap file format as the default format to save
+    captured packets; this format has existed for a long time and it's pretty simple.
+    However, it has some drawbacks: it's not extensible and lacks some
+    information that would be really helpful (e.g. being able to add a comment
+    to a packet such as "the problems start here" would be really nice).
     </para>
     <para>
-	In addition to the libpcap format, Wireshark supports several different
-	capture file formats. However, the problems described above also applies
-	for these formats.
+    In addition to the libpcap format, Wireshark supports several different
+    capture file formats. However, the problems described above also applies
+    for these formats.
     </para>
     <para>
-	A new capture file format "PCAP Next Generation Dump File Format"
-	is currently under development, which will fix these drawbacks.
-	However, it still might take a while until the new file format is ready
-	and Wireshark can use it.
+    A new capture file format "PCAP Next Generation Dump File Format"
+    is currently under development, which will fix these drawbacks.
+    However, it still might take a while until the new file format is ready
+    and Wireshark can use it.
     </para>
   <section id="ChIOFileContentSection"><title>Libpcap File Contents</title>
     <para>
-	At the start of each libpcap capture file some basic information is stored
-	like a magic number to identify the libpcap file format.
-	The most interesting information of this file start is the link layer type
-	(Ethernet, Token Ring, ...).
-    </para>
-    <para>
-	The following data is saved for each packet:
-	<itemizedlist>
-	<listitem>
-	  <para>
-	    the timestamp with millisecond resolution
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    the packet length as it was "on the wire"
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	  	the packet length as it's saved in the file
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    the packet's raw bytes
-	  </para>
-	</listitem>
+    At the start of each libpcap capture file some basic information is stored
+    like a magic number to identify the libpcap file format.
+    The most interesting information of this file start is the link layer type
+    (Ethernet, Token Ring, ...).
+    </para>
+    <para>
+    The following data is saved for each packet:
+    <itemizedlist>
+    <listitem>
+      <para>
+        the timestamp with millisecond resolution
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        the packet length as it was "on the wire"
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+          the packet length as it's saved in the file
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        the packet's raw bytes
+      </para>
+    </listitem>
       </itemizedlist>
-	A detailed description of the libpcap file format can be found at:
-	<ulink url="http://wiki.wireshark.org/Development/LibpcapFileFormat"/>
+    A detailed description of the libpcap file format can be found at:
+    <ulink url="http://wiki.wireshark.org/Development/LibpcapFileFormat"/>
     </para>
   </section>
   <section id="ChIOFileNotContentSection"><title>Not Saved in the Capture File</title>
     <para>
-	Probably even more interesting for everyday Wireshark usage is to know
-	the things that are <command>not saved</command> in the capture file:
-	<itemizedlist>
-	<listitem>
-	  <para>
-	    current selections (selected packet, ...)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    name resolution information, see <xref
-		linkend="ChAdvNameResolutionSection"/> for details
-		<warning><title>Warning!</title>
-		<para>
-		The name resolution information is rebuilt each time Wireshark is
-		restarted so this information might even change when the capture file
-		is reopened on the same machine later!
-		</para>
-		</warning>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    the number of packets dropped while capturing
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    packet marks set with "Edit/Mark Packet"
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    time references set with "Edit/Time Reference"
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    the current display filter
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    ...
-	  </para>
-	</listitem>
+    Probably even more interesting for everyday Wireshark usage is to know
+    the things that are <command>not saved</command> in the capture file:
+    <itemizedlist>
+    <listitem>
+      <para>
+        current selections (selected packet, ...)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        name resolution information, see <xref
+        linkend="ChAdvNameResolutionSection"/> for details
+        <warning><title>Warning!</title>
+        <para>
+        The name resolution information is rebuilt each time Wireshark is
+        restarted so this information might even change when the capture file
+        is reopened on the same machine later!
+        </para>
+        </warning>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        the number of packets dropped while capturing
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        packet marks set with "Edit/Mark Packet"
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        time references set with "Edit/Time Reference"
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        the current display filter
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        ...
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
   </section>
@@ -119,503 +119,503 @@
     <section id="ChAppFilesConfigurationSection"><title>Configuration Files and Folders</title>
     <para>
       Wireshark uses a number of files and folders while it is running. Some
-	  of these reside in the personal configuration folder and are used to
-	  maintain information between runs of Wireshark, while some of them are
-	  maintained in system areas.
+      of these reside in the personal configuration folder and are used to
+      maintain information between runs of Wireshark, while some of them are
+      maintained in system areas.
     </para>
-	<tip><title>Tip</title>
-	<para>A list of the folders Wireshark actually uses can be found under the
-	<command>Folders</command> tab in the dialog box shown when you select
-	<command>About Wireshark</command> from the <command>Help</command> menu.
-	</para>
-	</tip>
+    <tip><title>Tip</title>
+    <para>A list of the folders Wireshark actually uses can be found under the
+    <command>Folders</command> tab in the dialog box shown when you select
+    <command>About Wireshark</command> from the <command>Help</command> menu.
+    </para>
+    </tip>
     <para>
-	The content format of the configuration files is the same on all platforms.
-	However, to match the different policies for Unix and Windows platforms,
-	different folders are used for these files.
+    The content format of the configuration files is the same on all platforms.
+    However, to match the different policies for Unix and Windows platforms,
+    different folders are used for these files.
     </para>
     <table id="AppFilesTabFolders" frame="none">
-	<title>Configuration files and folders overview</title>
+    <title>Configuration files and folders overview</title>
       <tgroup cols="4">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	  <colspec colnum="3" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>File/Folder</entry>
-		<entry>Description</entry>
-		<entry>Unix/Linux folders</entry>
-		<entry>Windows folders</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>preferences</command></entry>
-		<entry>Settings from the Preferences dialog box.</entry>
-		<entry>/etc/wireshark.conf, $HOME/.wireshark/preferences</entry>
-		<entry>%WIRESHARK%\wireshark.conf, %APPDATA%\Wireshark\preferences</entry>
-	      </row>
-	      <row>
-		<entry><command>recent</command></entry>
-		<entry>Recent GUI settings (e.g. recent files lists).</entry>
-		<entry>$HOME/.wireshark/recent</entry>
-		<entry>%APPDATA%\Wireshark\recent</entry>
-	      </row>
-	      <row>
-		<entry><command>cfilters</command></entry>
-		<entry>Capture filters.</entry>
-		<entry>$HOME/.wireshark/cfilters</entry>
-		<entry>%WIRESHARK%\cfilters, %APPDATA%\Wireshark\cfilters</entry>
-	      </row>
-	      <row>
-		<entry><command>dfilters</command></entry>
-		<entry>Display filters.</entry>
-		<entry>$HOME/.wireshark/dfilters</entry>
-		<entry>%WIRESHARK%\dfilters, %APPDATA%\Wireshark\dfilters</entry>
-	      </row>
-	      <row>
-		<entry><command>colorfilters</command></entry>
-		<entry>Coloring rules.</entry>
-		<entry>$HOME/.wireshark/colorfilters</entry>
-		<entry>%WIRESHARK%\colorfilters, %APPDATA%\Wireshark\colorfilters</entry>
-	      </row>
-	      <row>
-		<entry><command>disabled_protos</command></entry>
-		<entry>Disabled protocols.</entry>
-		<entry>$HOME/.wireshark/disabled_protos</entry>
-		<entry>%WIRESHARK%\disabled_protos, %APPDATA%\Wireshark\disabled_protos</entry>
-	      </row>
-	      <row>
-		<entry><command>ethers</command></entry>
-		<entry>Ethernet name resolution.</entry>
-		<entry>/etc/ethers, $HOME/.wireshark/ethers</entry>
-		<entry>%WIRESHARK%\ethers, %APPDATA%\Wireshark\ethers</entry>
-	      </row>
-	      <row>
-		<entry><command>manuf</command></entry>
-		<entry>Ethernet name resolution.</entry>
-		<entry>/etc/manuf, $HOME/.wireshark/manuf</entry>
-		<entry>%WIRESHARK%\manuf, %APPDATA%\Wireshark\manuf</entry>
-	      </row>
-	      <row>
-		<entry><command>hosts</command></entry>
-		<entry>IPv4 and IPv6 name resolution.</entry>
-		<entry>/etc/hosts, $HOME/.wireshark/hosts</entry>
-		<entry>%WIRESHARK%\hosts, %APPDATA%\Wireshark\hosts</entry>
-	      </row>
-	      <row>
-		<entry><command>services</command></entry>
-		<entry>Network services.</entry>
-		<entry>/etc/services, $HOME/.wireshark/services</entry>
-		<entry>%WIRESHARK%\services, %APPDATA%\Wireshark\services</entry>
-	      </row>
-	      <row>
-		<entry><command>subnets</command></entry>
-		<entry>IPv4 subnet name resolution.</entry>
-		<entry>/etc/subnets, $HOME/.wireshark/subnets</entry>
-		<entry>%WIRESHARK%\subnets, %APPDATA%\Wireshark\subnets</entry>
-	      </row>
-	      <row>
-		<entry><command>ipxnets</command></entry>
-		<entry>IPX name resolution.</entry>
-		<entry>/etc/ipxnets, $HOME/.wireshark/ipxnets</entry>
-		<entry>%WIRESHARK%\ipxnets, %APPDATA%\Wireshark\ipxnets</entry>
-	      </row>
-	      <row>
-		<entry><command>plugins</command></entry>
-		<entry>Plugin directories.</entry>
-		<entry>/usr/share/wireshark/plugins,
-	      /usr/local/share/wireshark/plugins,
-	      $HOME/.wireshark/plugins
-		</entry>
-		<entry>%WIRESHARK%\plugins\&lt;version&gt;,
-		%APPDATA%\Wireshark\plugins</entry>
-	      </row>
-	      <row>
-		<entry><command>temp</command></entry>
-		<entry>Temporary files.</entry>
-		<entry>Environment: TMPDIR</entry>
-		<entry>Environment: TMPDIR or TEMP</entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+      <colspec colnum="3" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>File/Folder</entry>
+        <entry>Description</entry>
+        <entry>Unix/Linux folders</entry>
+        <entry>Windows folders</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>preferences</command></entry>
+        <entry>Settings from the Preferences dialog box.</entry>
+        <entry>/etc/wireshark.conf, $HOME/.wireshark/preferences</entry>
+        <entry>%WIRESHARK%\wireshark.conf, %APPDATA%\Wireshark\preferences</entry>
+          </row>
+          <row>
+        <entry><command>recent</command></entry>
+        <entry>Recent GUI settings (e.g. recent files lists).</entry>
+        <entry>$HOME/.wireshark/recent</entry>
+        <entry>%APPDATA%\Wireshark\recent</entry>
+          </row>
+          <row>
+        <entry><command>cfilters</command></entry>
+        <entry>Capture filters.</entry>
+        <entry>$HOME/.wireshark/cfilters</entry>
+        <entry>%WIRESHARK%\cfilters, %APPDATA%\Wireshark\cfilters</entry>
+          </row>
+          <row>
+        <entry><command>dfilters</command></entry>
+        <entry>Display filters.</entry>
+        <entry>$HOME/.wireshark/dfilters</entry>
+        <entry>%WIRESHARK%\dfilters, %APPDATA%\Wireshark\dfilters</entry>
+          </row>
+          <row>
+        <entry><command>colorfilters</command></entry>
+        <entry>Coloring rules.</entry>
+        <entry>$HOME/.wireshark/colorfilters</entry>
+        <entry>%WIRESHARK%\colorfilters, %APPDATA%\Wireshark\colorfilters</entry>
+          </row>
+          <row>
+        <entry><command>disabled_protos</command></entry>
+        <entry>Disabled protocols.</entry>
+        <entry>$HOME/.wireshark/disabled_protos</entry>
+        <entry>%WIRESHARK%\disabled_protos, %APPDATA%\Wireshark\disabled_protos</entry>
+          </row>
+          <row>
+        <entry><command>ethers</command></entry>
+        <entry>Ethernet name resolution.</entry>
+        <entry>/etc/ethers, $HOME/.wireshark/ethers</entry>
+        <entry>%WIRESHARK%\ethers, %APPDATA%\Wireshark\ethers</entry>
+          </row>
+          <row>
+        <entry><command>manuf</command></entry>
+        <entry>Ethernet name resolution.</entry>
+        <entry>/etc/manuf, $HOME/.wireshark/manuf</entry>
+        <entry>%WIRESHARK%\manuf, %APPDATA%\Wireshark\manuf</entry>
+          </row>
+          <row>
+        <entry><command>hosts</command></entry>
+        <entry>IPv4 and IPv6 name resolution.</entry>
+        <entry>/etc/hosts, $HOME/.wireshark/hosts</entry>
+        <entry>%WIRESHARK%\hosts, %APPDATA%\Wireshark\hosts</entry>
+          </row>
+          <row>
+        <entry><command>services</command></entry>
+        <entry>Network services.</entry>
+        <entry>/etc/services, $HOME/.wireshark/services</entry>
+        <entry>%WIRESHARK%\services, %APPDATA%\Wireshark\services</entry>
+          </row>
+          <row>
+        <entry><command>subnets</command></entry>
+        <entry>IPv4 subnet name resolution.</entry>
+        <entry>/etc/subnets, $HOME/.wireshark/subnets</entry>
+        <entry>%WIRESHARK%\subnets, %APPDATA%\Wireshark\subnets</entry>
+          </row>
+          <row>
+        <entry><command>ipxnets</command></entry>
+        <entry>IPX name resolution.</entry>
+        <entry>/etc/ipxnets, $HOME/.wireshark/ipxnets</entry>
+        <entry>%WIRESHARK%\ipxnets, %APPDATA%\Wireshark\ipxnets</entry>
+          </row>
+          <row>
+        <entry><command>plugins</command></entry>
+        <entry>Plugin directories.</entry>
+        <entry>/usr/share/wireshark/plugins,
+          /usr/local/share/wireshark/plugins,
+          $HOME/.wireshark/plugins
+        </entry>
+        <entry>%WIRESHARK%\plugins\&lt;version&gt;,
+        %APPDATA%\Wireshark\plugins</entry>
+          </row>
+          <row>
+        <entry><command>temp</command></entry>
+        <entry>Temporary files.</entry>
+        <entry>Environment: TMPDIR</entry>
+        <entry>Environment: TMPDIR or TEMP</entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
-	<note><title>Windows folders</title>
-	<para>
-	%APPDATA% points to the personal configuration folder, e.g.:
-	<filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>
-	(details can be found at: <xref linkend="ChWindowsProfiles"/>),
-	</para>
-	<para>
-	%WIRESHARK% points to the Wireshark program folder, e.g.:
-	<filename>C:\Program Files\Wireshark</filename>
-	</para>
-	</note>
-	<note><title>Unix/Linux folders</title>
-	<para>
-	The <filename>/etc</filename> folder is the global Wireshark configuration
-	folder. The folder actually used on your system
-	may vary, maybe something like: <filename>/usr/local/etc</filename>.
-	</para>
-	<para>
+    <note><title>Windows folders</title>
+    <para>
+    %APPDATA% points to the personal configuration folder, e.g.:
+    <filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>
+    (details can be found at: <xref linkend="ChWindowsProfiles"/>),
+    </para>
+    <para>
+    %WIRESHARK% points to the Wireshark program folder, e.g.:
+    <filename>C:\Program Files\Wireshark</filename>
+    </para>
+    </note>
+    <note><title>Unix/Linux folders</title>
+    <para>
+    The <filename>/etc</filename> folder is the global Wireshark configuration
+    folder. The folder actually used on your system
+    may vary, maybe something like: <filename>/usr/local/etc</filename>.
+    </para>
+    <para>
     $HOME is usually something like: <filename>/home/&lt;username&gt;</filename>
-	</para>
-	</note>
+    </para>
+    </note>
     <para>
       <variablelist>
-	<varlistentry>
-	  <term><command>preferences/wireshark.conf</command></term>
-	  <listitem>
-	    <para>
-	      This file contains your Wireshark preferences,
-	      including defaults for capturing and displaying packets.
-	      It is a simple text file containing statements of the form:
-	      <programlisting>
+    <varlistentry>
+      <term><command>preferences/wireshark.conf</command></term>
+      <listitem>
+        <para>
+          This file contains your Wireshark preferences,
+          including defaults for capturing and displaying packets.
+          It is a simple text file containing statements of the form:
+          <programlisting>
 variable: value
-		  </programlisting>
-	      The settings from this file are
-		  read in at program start and written to disk when you press the
-		  Save button in the "Preferences" dialog box.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>recent</command></term>
-	  <listitem>
-	    <para>
-	      This file contains various GUI related settings like the main window
-		  position and size, the recent files list and such.
-	      It is a simple text file containing statements of the form:
-	      <programlisting>
+          </programlisting>
+          The settings from this file are
+          read in at program start and written to disk when you press the
+          Save button in the "Preferences" dialog box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>recent</command></term>
+      <listitem>
+        <para>
+          This file contains various GUI related settings like the main window
+          position and size, the recent files list and such.
+          It is a simple text file containing statements of the form:
+          <programlisting>
 variable: value
-		  </programlisting>
-		  It is read at program start and written at program exit.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>cfilters</command></term>
-	  <listitem>
-	    <para>
-	      This file contains all the capture filters that you have defined
-	      and saved. It consists of one or more lines, where each
-	      line has the following format:
-	      <programlisting>
+          </programlisting>
+          It is read at program start and written at program exit.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>cfilters</command></term>
+      <listitem>
+        <para>
+          This file contains all the capture filters that you have defined
+          and saved. It consists of one or more lines, where each
+          line has the following format:
+          <programlisting>
 "&lt;filter name>" &lt;filter string>
-	      </programlisting>
- 		The settings from this file are read in at program start and written
-		to disk when you press the Save button in the "Capture Filters" dialog
-		box.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>dfilters</command></term>
-	  <listitem>
-	    <para>
-	      This file contains all the display filters that you have defined
-	      and saved. It consists of one or more lines, where each
-	      line has the following format:
-	      <programlisting>
+          </programlisting>
+         The settings from this file are read in at program start and written
+        to disk when you press the Save button in the "Capture Filters" dialog
+        box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>dfilters</command></term>
+      <listitem>
+        <para>
+          This file contains all the display filters that you have defined
+          and saved. It consists of one or more lines, where each
+          line has the following format:
+          <programlisting>
 "&lt;filter name>" &lt;filter string>
-	      </programlisting>
- 		The settings from this file are read in at program start and written
-		to disk when you press the Save button in the "Display Filters" dialog
-		box.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>colorfilters</command></term>
-	  <listitem>
-	    <para>
-	      This file contains all the color filters that you have
-	      defined and saved. It consists of one or more lines,
-	      where each line has the following format:
-	      <programlisting>
+          </programlisting>
+         The settings from this file are read in at program start and written
+        to disk when you press the Save button in the "Display Filters" dialog
+        box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>colorfilters</command></term>
+      <listitem>
+        <para>
+          This file contains all the color filters that you have
+          defined and saved. It consists of one or more lines,
+          where each line has the following format:
+          <programlisting>
 @&lt;filter name>@&lt;filter string>@[&lt;bg RGB(16-bit)>][&lt;fg RGB(16-bit)>]
-	      </programlisting>
-	    </para>
-		<para>
- 		The settings from this file are read in at program start and written
-		to disk when you press the Save button in the "Coloring Rules" dialog
-		box.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>disabled_protos</command></term>
-	  <listitem>
-	    <para>
-	      Each line in this file specifies a disabled protocol name. The
-		  following are some examples:
-	      <programlisting>
+          </programlisting>
+        </para>
+        <para>
+         The settings from this file are read in at program start and written
+        to disk when you press the Save button in the "Coloring Rules" dialog
+        box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>disabled_protos</command></term>
+      <listitem>
+        <para>
+          Each line in this file specifies a disabled protocol name. The
+          following are some examples:
+          <programlisting>
 tcp
 udp
-	      </programlisting>
-	    </para>
-		<para>
- 		The settings from this file are read in at program start and written
-		to disk when you press the Save button in the "Enabled Protocols"
-		dialog box.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>
-	    <command>ethers</command>
-	  </term>
-	  <listitem>
-	    <para>
-	      When Wireshark is trying to translate Ethernet hardware
-	      addresses to names, it consults the files listed in
-		  <xref linkend="AppFilesTabFolders"/>.
-	      If an address is not found in /etc/ethers,
-	      Wireshark looks in $HOME/.wireshark/ethers
-	    </para>
-	    <para>
-	      Each line in these files consists of one hardware address and
-	      name separated by whitespace. The digits of hardware
-	      addresses are separated by colons (:), dashes (-) or
-	      periods(.). The following are some examples:
-	      <programlisting>
+          </programlisting>
+        </para>
+        <para>
+         The settings from this file are read in at program start and written
+        to disk when you press the Save button in the "Enabled Protocols"
+        dialog box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        <command>ethers</command>
+      </term>
+      <listitem>
+        <para>
+          When Wireshark is trying to translate Ethernet hardware
+          addresses to names, it consults the files listed in
+          <xref linkend="AppFilesTabFolders"/>.
+          If an address is not found in /etc/ethers,
+          Wireshark looks in $HOME/.wireshark/ethers
+        </para>
+        <para>
+          Each line in these files consists of one hardware address and
+          name separated by whitespace. The digits of hardware
+          addresses are separated by colons (:), dashes (-) or
+          periods(.). The following are some examples:
+          <programlisting>
 ff-ff-ff-ff-ff-ff    Broadcast
 c0-00-ff-ff-ff-ff    TR_broadcast
 00.2b.08.93.4b.a1    Freds_machine
-	      </programlisting>
- 		The settings from this file are read in at program start and never
-		written by Wireshark.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>manuf</command></term>
-	  <listitem>
-	    <para>
-	      Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
-		  to translate the first three bytes of an Ethernet address into a
-		  manufacturers name.  This file has the same format as the ethers
-		  file, except addresses are three bytes long.
-	    </para>
-	    <para>
-	      An example is:
-	      <programlisting>
-00:00:01	Xerox                  # XEROX CORPORATION
-	      </programlisting>
-	    </para>
-		<para>
- 		The settings from this file are read in at program start and never
-		written by Wireshark.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>hosts</command></term>
-	  <listitem>
-	    <para>
-	      Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
-		  to translate IPv4 and IPv6 addresses into names.
-	    </para>
-	    <para>
-		  This file has the same format as the usual /etc/hosts file on Unix systems.
-	    </para>
-	    <para>
-	      An example is:
-	      <programlisting>
+          </programlisting>
+         The settings from this file are read in at program start and never
+        written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>manuf</command></term>
+      <listitem>
+        <para>
+          Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
+          to translate the first three bytes of an Ethernet address into a
+          manufacturers name.  This file has the same format as the ethers
+          file, except addresses are three bytes long.
+        </para>
+        <para>
+          An example is:
+          <programlisting>
+00:00:01    Xerox                  # XEROX CORPORATION
+          </programlisting>
+        </para>
+        <para>
+         The settings from this file are read in at program start and never
+        written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>hosts</command></term>
+      <listitem>
+        <para>
+          Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
+          to translate IPv4 and IPv6 addresses into names.
+        </para>
+        <para>
+          This file has the same format as the usual /etc/hosts file on Unix systems.
+        </para>
+        <para>
+          An example is:
+          <programlisting>
 # Comments must be prepended by the # sign!
 192.168.0.1 homeserver
-	      </programlisting>
-	    </para>
-		<para>
- 		The settings from this file are read in at program start and never
-		written by Wireshark.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>services</command></term>
-	  <listitem>
-	    <para>
-	      Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
-	      to translate port numbers into names.
-	    </para>
-	    <para>
-	      An example is:
-	      <programlisting>
+          </programlisting>
+        </para>
+        <para>
+         The settings from this file are read in at program start and never
+        written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>services</command></term>
+      <listitem>
+        <para>
+          Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
+          to translate port numbers into names.
+        </para>
+        <para>
+          An example is:
+          <programlisting>
 mydns       5045/udp     # My own Domain Name Server
 mydns       5045/tcp     # My own Domain Name Server
-	      </programlisting>
-	    </para>
-	    <para>
-	      The settings from this file are read in at program start and never
-	      written by Wireshark.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>subnets</command></term>
-	  <listitem>
-	    <para>
-	      Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
-		  to translate an IPv4 address into a subnet name. If no exact match from the
-		  hosts file or from DNS is found, Wireshark will attempt a partial match for the subnet
-		  of the address.
-	    </para>
-	    <para>
-		  Each line of this file consists of an IPv4 address, a subnet mask length separated
-		  only by a '/' and a name separated by whitespace. While the address must be a full IPv4
-		  address, any values beyond the mask length are subsequently ignored.
-	    </para>
+          </programlisting>
+        </para>
+        <para>
+          The settings from this file are read in at program start and never
+          written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>subnets</command></term>
+      <listitem>
+        <para>
+          Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
+          to translate an IPv4 address into a subnet name. If no exact match from the
+          hosts file or from DNS is found, Wireshark will attempt a partial match for the subnet
+          of the address.
+        </para>
+        <para>
+          Each line of this file consists of an IPv4 address, a subnet mask length separated
+          only by a '/' and a name separated by whitespace. While the address must be a full IPv4
+          address, any values beyond the mask length are subsequently ignored.
+        </para>
 
-	    <para>
-	      An example is:
-	      <programlisting>
+        <para>
+          An example is:
+          <programlisting>
 # Comments must be prepended by the # sign!
 192.168.0.0/24 ws_test_network
-	      </programlisting>
-	    </para>
-		<para>
-		A partially matched name will be printed as "subnet-name.remaining-address". For example,
-		"192.168.0.1" under the subnet above would be printed as "ws_test_network.1"; if the mask length
-		above had been 16 rather than 24, the printed address would be "ws_test_network.0.1".
-		</para>
-		<para>
- 		The settings from this file are read in at program start and never
-		written by Wireshark.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>ipxnets</command></term>
-	  <listitem>
-	    <para>
-	      Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
-		  to translate IPX network numbers into names.
-	    </para>
-	    <para>
-	      An example is:
-	      <programlisting>
+          </programlisting>
+        </para>
+        <para>
+        A partially matched name will be printed as "subnet-name.remaining-address". For example,
+        "192.168.0.1" under the subnet above would be printed as "ws_test_network.1"; if the mask length
+        above had been 16 rather than 24, the printed address would be "ws_test_network.0.1".
+        </para>
+        <para>
+         The settings from this file are read in at program start and never
+        written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>ipxnets</command></term>
+      <listitem>
+        <para>
+          Wireshark uses the files listed in <xref linkend="AppFilesTabFolders"/>
+          to translate IPX network numbers into names.
+        </para>
+        <para>
+          An example is:
+          <programlisting>
 C0.A8.2C.00      HR
 c0-a8-1c-00      CEO
 00:00:BE:EF      IT_Server1
 110f             FileServer3
-	      </programlisting>
-	    </para>
-		<para>
- 		The settings from this file are read in at program start and never
-		written by Wireshark.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>plugins</command> folder</term>
-	  <listitem>
-	    <para>
-	      Wireshark searches for plugins in the directories listed in
-		  <xref linkend="AppFilesTabFolders"/>.
-	      They are searched in the order listed.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>temp</command> folder</term>
-	  <listitem>
-	    <para>
-	      If you start a new capture and don't specify a filename for it,
-		  Wireshark uses this directory to store that file; see
-		  <xref linkend="ChCapCaptureFiles"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
+          </programlisting>
+        </para>
+        <para>
+         The settings from this file are read in at program start and never
+        written by Wireshark.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>plugins</command> folder</term>
+      <listitem>
+        <para>
+          Wireshark searches for plugins in the directories listed in
+          <xref linkend="AppFilesTabFolders"/>.
+          They are searched in the order listed.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>temp</command> folder</term>
+      <listitem>
+        <para>
+          If you start a new capture and don't specify a filename for it,
+          Wireshark uses this directory to store that file; see
+          <xref linkend="ChCapCaptureFiles"/>.
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </para>
 
-	<section id="ChProtocolHelp"><title>Protocol help configuration</title>
-	<para>
-	  Wireshark can use configuration files to create context-sensitive menu
-	  items for protocol detail items which will load help URLs in your web
-	  browser.
-	</para>
-	<para>
-	  To create a protocol help file, create a folder named "protocol_help"
-	  in either the personal or global configuration folders. Then create a
-	  text file with the extension ".ini" in the "protocol_help" folder. The
-	  file must contain key-value pairs with the following sections:
-	  <variablelist>
-	    <varlistentry>
-	      <term>[database]</term>
-	      <listitem>
-		<para>
-		  Mandatory. This contains initialization information for the
-		  help file. The following keys must be defined:
-		  <variablelist>
-		    <varlistentry>
-		      <term>source</term>
-		      <listitem><para>Source name, e.g. "HyperGlobalMegaMart".</para></listitem>
-		    </varlistentry>
-		    <varlistentry>
-		      <term>version</term>
-		      <listitem><para>Must be "1".</para></listitem>
-		    </varlistentry>
-		    <varlistentry>
-		      <term>location</term>
-		      <listitem>
-			<para>
-			General URL for help items. Variables can be substituted using
-			the [location data] section below.
-			</para>
-		      </listitem>
-		    </varlistentry>
-		  </variablelist>
-		</para>
-	      </listitem>
-	    </varlistentry>
+    <section id="ChProtocolHelp"><title>Protocol help configuration</title>
+    <para>
+      Wireshark can use configuration files to create context-sensitive menu
+      items for protocol detail items which will load help URLs in your web
+      browser.
+    </para>
+    <para>
+      To create a protocol help file, create a folder named "protocol_help"
+      in either the personal or global configuration folders. Then create a
+      text file with the extension ".ini" in the "protocol_help" folder. The
+      file must contain key-value pairs with the following sections:
+      <variablelist>
+        <varlistentry>
+          <term>[database]</term>
+          <listitem>
+        <para>
+          Mandatory. This contains initialization information for the
+          help file. The following keys must be defined:
+          <variablelist>
+            <varlistentry>
+              <term>source</term>
+              <listitem><para>Source name, e.g. "HyperGlobalMegaMart".</para></listitem>
+            </varlistentry>
+            <varlistentry>
+              <term>version</term>
+              <listitem><para>Must be "1".</para></listitem>
+            </varlistentry>
+            <varlistentry>
+              <term>location</term>
+              <listitem>
+            <para>
+            General URL for help items. Variables can be substituted using
+            the [location data] section below.
+            </para>
+              </listitem>
+            </varlistentry>
+          </variablelist>
+        </para>
+          </listitem>
+        </varlistentry>
 
-	    <varlistentry>
-	      <term>[location data]</term>
-	      <listitem>
-		<para>
-		  Optional. Contains keys that will be used for variable
-		  substitution in the "location" value. For example, if
-		  the database section contains
-		  <programlisting>
+        <varlistentry>
+          <term>[location data]</term>
+          <listitem>
+        <para>
+          Optional. Contains keys that will be used for variable
+          substitution in the "location" value. For example, if
+          the database section contains
+          <programlisting>
 location = http://www.example.com/proto?cookie=${cookie}&amp;path=${PATH}
-		  </programlisting>
-		  then setting
-		  <programlisting>
+          </programlisting>
+          then setting
+          <programlisting>
 cookie = anonymous-user-1138
-		  </programlisting>
-		  will result in the URL
-		  "http://www.example.com/proto?cookie=anonymous-user-1138&amp;path=${PATH}".
-		  PATH is used for help path substitution, and shouldn't be defined in this section.
-		</para>
-	      </listitem>
-	    </varlistentry>
+          </programlisting>
+          will result in the URL
+          "http://www.example.com/proto?cookie=anonymous-user-1138&amp;path=${PATH}".
+          PATH is used for help path substitution, and shouldn't be defined in this section.
+        </para>
+          </listitem>
+        </varlistentry>
 
-	    <varlistentry>
-	      <term>[map]</term>
-	      <listitem>
-		<para>
-		  Maps Wireshark protocol names to section names below. Each key
-		  MUST match a valid protocol name such as "ip". Each value MUST
-		  have a matching section defined in the configuration file.
-		</para>
-	      </listitem>
-	    </varlistentry>
+        <varlistentry>
+          <term>[map]</term>
+          <listitem>
+        <para>
+          Maps Wireshark protocol names to section names below. Each key
+          MUST match a valid protocol name such as "ip". Each value MUST
+          have a matching section defined in the configuration file.
+        </para>
+          </listitem>
+        </varlistentry>
 
-	  </variablelist>
+      </variablelist>
 
-	  Each protocol section must contain an "_OVERVIEW" key which will be used
-	  as the first menu item for the help source. Subsequent keys must match
-	  descriptions in the protocol detail. Values will be used as the ${PATH}
-	  variable in the location template. If ${PATH} isn't present in the location
-	  template the value will be appended to the location.
-	</para>
+      Each protocol section must contain an "_OVERVIEW" key which will be used
+      as the first menu item for the help source. Subsequent keys must match
+      descriptions in the protocol detail. Values will be used as the ${PATH}
+      variable in the location template. If ${PATH} isn't present in the location
+      template the value will be appended to the location.
+    </para>
 
-	<para>
-	  Suppose the file
-	  <filename>C:\Users\sam.clemens\AppData\Roaming\Wireshark\protocol_help\wikipedia.ini</filename>
-	  contains the following:
+    <para>
+      Suppose the file
+      <filename>C:\Users\sam.clemens\AppData\Roaming\Wireshark\protocol_help\wikipedia.ini</filename>
+      contains the following:
 
-	  <programlisting>
+      <programlisting>
 # Wikipedia (en) protocol help file.
 
 # Help file initialization
@@ -648,18 +648,18 @@ tcp=TCP
 _OVERVIEW=Transmission_Control_Protocol
 Destination port=Transmission_Control_Protocol#TCP_ports
 Source port=Transmission_Control_Protocol#TCP_ports
-	  </programlisting>
-	  Right-clicking on a TCP protocol detail item will display a help menu
-	  item that displays the Wikipedia page for TCP. Right-clicking on the
-	  TCP destination or source ports will display additional help menu items that
-	  take you to the "TCP ports" section of the page.
-	</para>
+      </programlisting>
+      Right-clicking on a TCP protocol detail item will display a help menu
+      item that displays the Wikipedia page for TCP. Right-clicking on the
+      TCP destination or source ports will display additional help menu items that
+      take you to the "TCP ports" section of the page.
+    </para>
 
-	<para>
-	  The [location data] and ${PATH} can be omitted if they are not needed.
-	  For example, the following configuration is functionally equivalent to
-	  the previous configuration:
-	  <programlisting>
+    <para>
+      The [location data] and ${PATH} can be omitted if they are not needed.
+      For example, the following configuration is functionally equivalent to
+      the previous configuration:
+      <programlisting>
 [database]
 source=Wikipedia
 version=1
@@ -672,163 +672,163 @@ tcp=TCP
 _OVERVIEW=Transmission_Control_Protocol
 Destination port=Transmission_Control_Protocol#TCP_ports
 Source port=Transmission_Control_Protocol#TCP_ports
-	  </programlisting>
-	</para>
-	</section>
+      </programlisting>
+    </para>
+    </section>
 
-	</section>
+    </section>
 
-	<section id="ChWindowsFolder"><title>Windows folders</title>
-	<para>
-	Here you will find some details about the folders used in Wireshark
-	on different Windows versions.
-	</para>
-	<para>
-	As already mentioned, you can find the currently used folders in the
-	<command>About Wireshark</command> dialog.
-	</para>
+    <section id="ChWindowsFolder"><title>Windows folders</title>
+    <para>
+    Here you will find some details about the folders used in Wireshark
+    on different Windows versions.
+    </para>
+    <para>
+    As already mentioned, you can find the currently used folders in the
+    <command>About Wireshark</command> dialog.
+    </para>
 
-	<section id="ChWindowsProfiles"><title>Windows profiles</title>
-	<para>
-	Windows uses some special directories to store user configuration files
+    <section id="ChWindowsProfiles"><title>Windows profiles</title>
+    <para>
+    Windows uses some special directories to store user configuration files
         which define the "user profile". This can be confusing, as the default directory location
-	changed from Windows version to version and might also be different for English
-	and internationalized versions of Windows.
-	</para>
-	<note><title>Note!</title>
-	<para>
-	If you've upgraded to a new Windows version, your profile might
-	be kept in the former location, so the defaults mentioned here might not
-	apply.
-	</para>
-	</note>
-	<para>
-	The following guides
-	you to the right place where to look for Wireshark's profile data.
-	</para>
-	<para>
+    changed from Windows version to version and might also be different for English
+    and internationalized versions of Windows.
+    </para>
+    <note><title>Note!</title>
+    <para>
+    If you've upgraded to a new Windows version, your profile might
+    be kept in the former location, so the defaults mentioned here might not
+    apply.
+    </para>
+    </note>
+    <para>
+    The following guides
+    you to the right place where to look for Wireshark's profile data.
+    </para>
+    <para>
       <variablelist>
-	<varlistentry>
-	  <term><application>Windows 7</application>, <application>Windows Vista</application></term>
-	  <listitem>
-	<para>
-	<filename>C:\Users\&lt;username&gt;\AppData\Roaming\Wireshark</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><application>Windows 7</application>, <application>Windows Vista</application></term>
+      <listitem>
+    <para>
+    <filename>C:\Users\&lt;username&gt;\AppData\Roaming\Wireshark</filename>
+    </para>
+      </listitem>
+    </varlistentry>
 
-	<varlistentry>
-	  <term><application>Windows XP</application></term>
-	  <listitem>
-	<para>
-	<filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>,
-	"Documents and Settings" and "Application Data" might be internationalized.
-	</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><application>Windows XP</application></term>
+      <listitem>
+    <para>
+    <filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>,
+    "Documents and Settings" and "Application Data" might be internationalized.
+    </para>
+      </listitem>
+    </varlistentry>
 
-	<varlistentry>
-	  <term><application>Windows 2000</application> (no longer supported by Wireshark, for historical reference only)</term>
-	  <listitem>
-	<para>
-	<filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>,
-	"Documents and Settings" and "Application Data" might be internationalized.
-	</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><application>Windows 2000</application> (no longer supported by Wireshark, for historical reference only)</term>
+      <listitem>
+    <para>
+    <filename>C:\Documents and Settings\&lt;username&gt;\Application Data</filename>,
+    "Documents and Settings" and "Application Data" might be internationalized.
+    </para>
+      </listitem>
+    </varlistentry>
 
-	<varlistentry>
-	  <term><application>Windows NT 4</application> (no longer supported, for historical reference only)</term>
-	  <listitem>
-	<para>
-	<filename>C:\WINNT\Profiles\&lt;username&gt;\Application Data\Wireshark</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><application>Windows ME</application>, <application>Windows 98</application> with user profiles (no longer supported, for historical reference only)</term>
-	  <listitem>
-	<para>
-	In Windows ME and 98 you can enable separate user profiles. In that case,
-	something like
-	<filename>C:\windows\Profiles\&lt;username&gt;\Application Data\Wireshark</filename>
-	is used.
-	</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><application>Windows ME</application>, <application>Windows 98</application> without user profiles (no longer supported, for historical reference only)</term>
-	  <listitem>
-	<para>
-	Without user profiles enabled the default location for all users is
-	<filename>C:\windows\Application Data\Wireshark</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><application>Windows NT 4</application> (no longer supported, for historical reference only)</term>
+      <listitem>
+    <para>
+    <filename>C:\WINNT\Profiles\&lt;username&gt;\Application Data\Wireshark</filename>
+    </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><application>Windows ME</application>, <application>Windows 98</application> with user profiles (no longer supported, for historical reference only)</term>
+      <listitem>
+    <para>
+    In Windows ME and 98 you can enable separate user profiles. In that case,
+    something like
+    <filename>C:\windows\Profiles\&lt;username&gt;\Application Data\Wireshark</filename>
+    is used.
+    </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><application>Windows ME</application>, <application>Windows 98</application> without user profiles (no longer supported, for historical reference only)</term>
+      <listitem>
+    <para>
+    Without user profiles enabled the default location for all users is
+    <filename>C:\windows\Application Data\Wireshark</filename>
+    </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
-	</para>
-	</section>
+    </para>
+    </section>
 
-	<section id="ChWindowsRoamingProfiles">
-	<title>Windows 7, Vista, XP, 2000, and NT roaming profiles</title>
-	<para>
-	The following will only be applicable if you are using roaming profiles.
-	This might be the case, if you work in a Windows domain environment
-	(used in company networks). The configurations of all
-	programs you use won't be saved on the local hard drive of the computer
-	you are currently working on, but on the domain server.
-	</para>
-	<para>
-	As Wireshark is using the correct places to store its profile data,
-	your settings will travel with you, if you logon to a different computer
-	the next time.
-	</para>
-	<para>
-	There is an exception to this: The "Local Settings" folder in your profile
-	data (typically something like:
-	<filename>C:\Documents and Settings\&lt;username&gt;\Local Settings</filename>)
-	will not be transferred to the domain server. This is the default for
-	temporary capture files.
-	</para>
-	</section>
+    <section id="ChWindowsRoamingProfiles">
+    <title>Windows 7, Vista, XP, 2000, and NT roaming profiles</title>
+    <para>
+    The following will only be applicable if you are using roaming profiles.
+    This might be the case, if you work in a Windows domain environment
+    (used in company networks). The configurations of all
+    programs you use won't be saved on the local hard drive of the computer
+    you are currently working on, but on the domain server.
+    </para>
+    <para>
+    As Wireshark is using the correct places to store its profile data,
+    your settings will travel with you, if you logon to a different computer
+    the next time.
+    </para>
+    <para>
+    There is an exception to this: The "Local Settings" folder in your profile
+    data (typically something like:
+    <filename>C:\Documents and Settings\&lt;username&gt;\Local Settings</filename>)
+    will not be transferred to the domain server. This is the default for
+    temporary capture files.
+    </para>
+    </section>
 
-	<section id="ChWindowsTempFolder">
-	<title>Windows temporary folder</title>
-	<para>
-	Wireshark uses the folder which is set by the TMPDIR or TEMP environment
-	variable. This variable will be set by the Windows installer.
-	</para>
-	<para>
+    <section id="ChWindowsTempFolder">
+    <title>Windows temporary folder</title>
+    <para>
+    Wireshark uses the folder which is set by the TMPDIR or TEMP environment
+    variable. This variable will be set by the Windows installer.
+    </para>
+    <para>
       <variablelist>
-	<varlistentry>
-	  <term><application>Windows 7</application>, <application>Windows Vista</application></term>
-	  <listitem>
-	<para>
-	<filename>C:\Users\&lt;username&gt;\AppData\Local\Temp</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><application>Windows XP</application>, <application>Windows 2000</application></term>
-	  <listitem>
-	<para>
-	<filename>C:\Documents and Settings\&lt;username&gt;\Local Settings\Temp</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><application>Windows NT</application></term>
-	  <listitem>
-	<para>
-	<filename>C:\TEMP</filename>
-	</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><application>Windows 7</application>, <application>Windows Vista</application></term>
+      <listitem>
+    <para>
+    <filename>C:\Users\&lt;username&gt;\AppData\Local\Temp</filename>
+    </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><application>Windows XP</application>, <application>Windows 2000</application></term>
+      <listitem>
+    <para>
+    <filename>C:\Documents and Settings\&lt;username&gt;\Local Settings\Temp</filename>
+    </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><application>Windows NT</application></term>
+      <listitem>
+    <para>
+    <filename>C:\TEMP</filename>
+    </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
-	</para>
-	</section>
+    </para>
+    </section>
 
-	</section>
+    </section>
 
 </appendix>
 <!-- End of WSUG Appendix Files -->
diff --git a/docbook/wsug_src/WSUG_app_messages.xml b/docbook/wsug_src/WSUG_app_messages.xml
index af0c99dfec..eb47a1431f 100644
--- a/docbook/wsug_src/WSUG_app_messages.xml
+++ b/docbook/wsug_src/WSUG_app_messages.xml
@@ -10,96 +10,96 @@
   </para>
   <section id="AppMessagesList"><title>Packet List Messages</title>
     <para>
-	These messages might appear in the packet list.
+    These messages might appear in the packet list.
     </para>
   <section><title>[Malformed Packet]</title>
     <para>
-	Malformed packet means that the protocol dissector can't dissect the 
-	contents of the packet any further. There can be various reasons:
+    Malformed packet means that the protocol dissector can't dissect the 
+    contents of the packet any further. There can be various reasons:
       <itemizedlist>
-	<listitem>
-	  <para>
-		<command>Wrong dissector</command>:
-	    Wireshark erroneously has chosen the wrong protocol dissector for 
-		this packet. This will happen e.g. if you are using a protocol  
-		not on its well known TCP or UDP port. You may try Analyze|Decode As 
-		to circumvent this problem.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		<command>Packet not reassembled</command>:
-		The packet is longer than a single frame and it is not reassembled,
-		see	<xref linkend="ChAdvReassemblySection"/> for further details.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		<command>Packet is malformed</command>:
-	    The packet is actually wrong (malformed), meaning that a part of the 
-		packet is just not as expected (not following the protocol 
-		specifications).
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		<command>Dissector is buggy</command>:
-	    The corresponding protocol dissector is simply buggy or still
-		incomplete.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        <command>Wrong dissector</command>:
+        Wireshark erroneously has chosen the wrong protocol dissector for 
+        this packet. This will happen e.g. if you are using a protocol  
+        not on its well known TCP or UDP port. You may try Analyze|Decode As 
+        to circumvent this problem.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Packet not reassembled</command>:
+        The packet is longer than a single frame and it is not reassembled,
+        see    <xref linkend="ChAdvReassemblySection"/> for further details.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Packet is malformed</command>:
+        The packet is actually wrong (malformed), meaning that a part of the 
+        packet is just not as expected (not following the protocol 
+        specifications).
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Dissector is buggy</command>:
+        The corresponding protocol dissector is simply buggy or still
+        incomplete.
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
     <para>
-	Any of the above is possible. You'll have to look into the specific 
-	situation to determine the reason. 
-	You could disable the dissector by disabling the
-	protocol on the Analyze menu and check how Wireshark displays the packet
-	then. You could (if it's TCP) enable reassembly for TCP and the specific
-	dissector (if possible) in the Edit|Preferences menu. You could check the
-	packet contents yourself by reading the packet bytes and comparing it to
-	the protocol specification. This could reveal a dissector bug. Or you
-	could find out that the packet is indeed wrong.
+    Any of the above is possible. You'll have to look into the specific 
+    situation to determine the reason. 
+    You could disable the dissector by disabling the
+    protocol on the Analyze menu and check how Wireshark displays the packet
+    then. You could (if it's TCP) enable reassembly for TCP and the specific
+    dissector (if possible) in the Edit|Preferences menu. You could check the
+    packet contents yourself by reading the packet bytes and comparing it to
+    the protocol specification. This could reveal a dissector bug. Or you
+    could find out that the packet is indeed wrong.
     </para>
   </section>
   <section><title>[Packet size limited during capture]</title>
     <para>
-	The packet size was limited during capture, see "Limit each packet to n 
-	bytes" at the <xref linkend="ChCapCaptureOptions"/>. 
-	While dissecting, the current protocol 
-	dissector was simply running out of packet bytes and had to give up.
-	There's nothing else you can do now, except to repeat the whole capture 
-	process again with a higher (or no) packet size limitation.
+    The packet size was limited during capture, see "Limit each packet to n 
+    bytes" at the <xref linkend="ChCapCaptureOptions"/>. 
+    While dissecting, the current protocol 
+    dissector was simply running out of packet bytes and had to give up.
+    There's nothing else you can do now, except to repeat the whole capture 
+    process again with a higher (or no) packet size limitation.
     </para>
   </section>
   </section>
 
   <section id="AppMessagesDetails"><title>Packet Details Messages</title>
     <para>
-	These messages might appear in the packet details.
+    These messages might appear in the packet details.
     </para>
   <section><title>[Response in frame: 123]</title>
     <para>
-	The current packet is the request of a detected request/response pair. 
-	You can directly jump to the corresponding response packet just 
-	by double clicking on this message.
+    The current packet is the request of a detected request/response pair. 
+    You can directly jump to the corresponding response packet just 
+    by double clicking on this message.
     </para>
   </section>
   <section><title>[Request in frame: 123]</title>
     <para>
-	Same as "Response in frame: 123" above, but the other way round.
+    Same as "Response in frame: 123" above, but the other way round.
     </para>
   </section>
   <section><title>[Time from request: 0.123 seconds]</title>
     <para>
-	The time between the request and the response packets.
+    The time between the request and the response packets.
     </para>
   </section>
   <section><title>[Stream setup by PROTOCOL (frame 123)]</title>
     <para>
-	The session control protocol (SDP, H225, etc) message which signaled 
-	the creation of this session. You can directly jump to the 
-	corresponding packet just by double clicking on this message.
+    The session control protocol (SDP, H225, etc) message which signaled 
+    the creation of this session. You can directly jump to the 
+    corresponding packet just by double clicking on this message.
     </para>
   </section>
   </section>
diff --git a/docbook/wsug_src/WSUG_app_protocols.xml b/docbook/wsug_src/WSUG_app_protocols.xml
index ce43738bd4..0d04883261 100644
--- a/docbook/wsug_src/WSUG_app_protocols.xml
+++ b/docbook/wsug_src/WSUG_app_protocols.xml
@@ -4,12 +4,12 @@
 <appendix id="AppProtocols">
   <title>Protocols and Protocol Fields</title>
   <para>
-  	Wireshark distinguishes between protocols (e.g. tcp) and protocol fields 
-	(e.g. tcp.port).
+      Wireshark distinguishes between protocols (e.g. tcp) and protocol fields 
+    (e.g. tcp.port).
   </para>
     <para>
-	 A comprehensive list of all protocols and protocol fields can be found 
-	at: <ulink url="&WiresharkProtocolsPage;">&WiresharkProtocolsPage;</ulink>	
+     A comprehensive list of all protocols and protocol fields can be found 
+    at: <ulink url="&WiresharkProtocolsPage;">&WiresharkProtocolsPage;</ulink>    
     </para>
 </appendix>
 <!-- End of WSUG Appendix Protocols -->
diff --git a/docbook/wsug_src/WSUG_app_tools.xml b/docbook/wsug_src/WSUG_app_tools.xml
index de3ab157b5..2b066a8a08 100644
--- a/docbook/wsug_src/WSUG_app_tools.xml
+++ b/docbook/wsug_src/WSUG_app_tools.xml
@@ -7,10 +7,10 @@
   <section id="AppToolsIntroduction">
     <title>Introduction</title>
     <para>
-	Besides the Wireshark GUI application, there are some command line tools
-	which can be helpful for doing some more specialized things. These tools
-	will be described in this chapter.
-	</para>
+    Besides the Wireshark GUI application, there are some command line tools
+    which can be helpful for doing some more specialized things. These tools
+    will be described in this chapter.
+    </para>
   </section>
 
   <section id="AppToolstshark">
@@ -121,7 +121,7 @@ Miscellaneous:
 
   <section id="AppToolstcpdump">
     <title><command>tcpdump</command>: Capturing with tcpdump for viewing
-	with Wireshark</title>
+    with Wireshark</title>
     <para>
       There are occasions when you want to capture packets using
       <command>tcpdump</command> rather than <command>wireshark</command>,
@@ -145,33 +145,33 @@ tcpdump -i &lt;interface> -s 65535 -w &lt;some-file>
       you will have to terminate the capture with ^C when you believe you
       have captured enough packets.
     </para>
-	<note><title>Note!</title>
-	<para>
-	tcpdump is not part of the Wireshark distribution. You can get it from:
-	<ulink url="&TcpdumpWebsite;">&TcpdumpWebsite;</ulink> for various
-	platforms.
-	</para>
-	</note>
+    <note><title>Note!</title>
+    <para>
+    tcpdump is not part of the Wireshark distribution. You can get it from:
+    <ulink url="&TcpdumpWebsite;">&TcpdumpWebsite;</ulink> for various
+    platforms.
+    </para>
+    </note>
   </section>
 
   <section id="AppToolsdumpcap">
     <title><command>dumpcap</command>: Capturing with dumpcap for viewing
-	with Wireshark</title>
+    with Wireshark</title>
     <para>
-	<application>Dumpcap</application> is a network traffic dump tool.
-	It captures packet data from a live network and writes the
-	packets to a file.
-	Dumpcap's native capture file format is libpcap format, which is also
-	the format used by Wireshark, tcpdump and various other tools.
+    <application>Dumpcap</application> is a network traffic dump tool.
+    It captures packet data from a live network and writes the
+    packets to a file.
+    Dumpcap's native capture file format is libpcap format, which is also
+    the format used by Wireshark, tcpdump and various other tools.
     </para>
     <para>
-	Without any options set it will use the pcap library to capture traffic
-	from the first available network interface and write the received raw
-	packet data, along with the packets' time stamps into a libpcap file.
+    Without any options set it will use the pcap library to capture traffic
+    from the first available network interface and write the received raw
+    packet data, along with the packets' time stamps into a libpcap file.
     </para>
     <para>
-	Packet capturing is performed with the pcap library.
-	The capture filter syntax follows the rules of the pcap library.
+    Packet capturing is performed with the pcap library.
+    The capture filter syntax follows the rules of the pcap library.
     </para>
     <para>
     <example id="AppToolsdumpcapEx">
@@ -233,17 +233,17 @@ Example: dumpcap -i eth0 -a duration:60 -w output.pcapng
 
 Use Ctrl-C to stop capturing at any time.
       </programlisting>
-	</example>
+    </example>
     </para>
   </section>
 
   <section id="AppToolscapinfos">
     <title><command>capinfos</command>: Print information about capture files
-	</title>
+    </title>
     <para>
       Included with Wireshark is a small utility called
       <command>capinfos</command>, which is a command-line utility to
-	  print information about binary capture files.
+      print information about binary capture files.
     </para>
     <para>
     <example id="AppToolscapinfosEx">
@@ -306,7 +306,7 @@ or adding to earlier options.
 If no options are given the default is to display all infos in long report
 output format.
       </programlisting>
-	</example>
+    </example>
     </para>
   </section>
 
@@ -753,7 +753,7 @@ Miscellaneous:
 
   <section id="AppToolstext2pcap" >
     <title><command>text2pcap</command>: Converting ASCII hexdumps to network
-	captures
+    captures
     </title>
     <para>
       There may be some occasions when you wish to convert a hex dump of some
@@ -911,221 +911,221 @@ Miscellaneous:
     <section>
       <title>What is it?</title>
       <para>
-	As you have probably guessed from the name,
-	<command>idl2wrs</command> takes a
-	user specified IDL file and attempts to build a dissector that
-	can decode the IDL traffic over GIOP. The resulting file is
-	"C" code, that should compile okay as a Wireshark dissector.
+    As you have probably guessed from the name,
+    <command>idl2wrs</command> takes a
+    user specified IDL file and attempts to build a dissector that
+    can decode the IDL traffic over GIOP. The resulting file is
+    "C" code, that should compile okay as a Wireshark dissector.
       </para>
       <para>
-	<command>idl2wrs</command> basically parses the data struct given to
-	it by the omniidl compiler, and using the GIOP API available in
-	packet-giop.[ch], generates  get_CDR_xxx calls to decode the
-	CORBA traffic on the wire.
+    <command>idl2wrs</command> basically parses the data struct given to
+    it by the omniidl compiler, and using the GIOP API available in
+    packet-giop.[ch], generates  get_CDR_xxx calls to decode the
+    CORBA traffic on the wire.
       </para>
       <para>It consists of 4 main files.</para>
       <variablelist>
-	<varlistentry><term><filename>README.idl2wrs</filename></term>
-	  <listitem>
-	    <para>This document</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><filename>wireshark_be.py</filename></term>
-	  <listitem>
-	    <para>The main compiler backend</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><filename>wireshark_gen.py</filename></term>
-	  <listitem>
-	    <para>A helper class, that generates the C code.</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><filename>idl2wrs</filename></term>
-	  <listitem>
-	    <para> A simple shell script wrapper that the end user should
-	      use to generate the dissector from the IDL file(s).</para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry><term><filename>README.idl2wrs</filename></term>
+      <listitem>
+        <para>This document</para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><filename>wireshark_be.py</filename></term>
+      <listitem>
+        <para>The main compiler backend</para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><filename>wireshark_gen.py</filename></term>
+      <listitem>
+        <para>A helper class, that generates the C code.</para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><filename>idl2wrs</filename></term>
+      <listitem>
+        <para> A simple shell script wrapper that the end user should
+          use to generate the dissector from the IDL file(s).</para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </section>
     <section>
       <title>Why do this?</title>
       <para>
-	It is important to understand what CORBA traffic looks
-	like over GIOP/IIOP, and to help build a tool that can assist
-	in troubleshooting CORBA interworking. This was especially the
-	case after seeing a lot of discussions about how particular
-	IDL types are represented inside an octet stream.
+    It is important to understand what CORBA traffic looks
+    like over GIOP/IIOP, and to help build a tool that can assist
+    in troubleshooting CORBA interworking. This was especially the
+    case after seeing a lot of discussions about how particular
+    IDL types are represented inside an octet stream.
       </para>
       <para>
-	I have also had comments/feedback that this tool would be good for say
-	a CORBA class when teaching students what CORBA traffic looks like
-	"on the wire".
+    I have also had comments/feedback that this tool would be good for say
+    a CORBA class when teaching students what CORBA traffic looks like
+    "on the wire".
       </para>
       <para>
-	It is also COOL to work on a great Open Source project such as
-	the case with "Wireshark" (
-	<ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>
-	)
+    It is also COOL to work on a great Open Source project such as
+    the case with "Wireshark" (
+    <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>
+    )
       </para>
     </section>
     <section><title>How to use idl2wrs</title>
       <para>
-	To use the idl2wrs to generate Wireshark dissectors, you
-	need the following:
+    To use the idl2wrs to generate Wireshark dissectors, you
+    need the following:
       </para>
       <orderedlist>
-	<title>Prerequisites to using idl2wrs</title>
-	<listitem>
-	  <para>
-	    Python must be installed.  See
-	    <ulink url="http://python.org/"/>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    omniidl from the omniORB package must be available. See
-	    <ulink url="http://omniorb.sourceforge.net/"/>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Of course you need Wireshark installed to compile the
-	    code and tweak it if required. idl2wrs is part of the
-	    standard Wireshark distribution
-	  </para>
-	</listitem>
+    <title>Prerequisites to using idl2wrs</title>
+    <listitem>
+      <para>
+        Python must be installed.  See
+        <ulink url="http://python.org/"/>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        omniidl from the omniORB package must be available. See
+        <ulink url="http://omniorb.sourceforge.net/"/>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Of course you need Wireshark installed to compile the
+        code and tweak it if required. idl2wrs is part of the
+        standard Wireshark distribution
+      </para>
+    </listitem>
       </orderedlist>
       <para>
-	To use idl2wrs to generate an Wireshark dissector from an idl file
-	use the following procedure:
+    To use idl2wrs to generate an Wireshark dissector from an idl file
+    use the following procedure:
       </para>
       <orderedlist>
-	<title>
-	  Procedure for converting a CORBA idl file into a Wireshark
-	  dissector
-	</title>
-	<listitem>
-	  <para>
-	    To write the C code to stdout.
-	    <programlisting>idl2wrs  &lt;your_file.idl&gt;</programlisting>
-	    e.g.: <programlisting>idl2wrs echo.idl</programlisting>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    To write to a file, just redirect the output.
-	    <programlisting>idl2wrs echo.idl > packet-test-idl.c</programlisting>
-	    You may wish to comment out the register_giop_user_module() code
-	    and that will leave you with heuristic dissection.
-	  </para>
-	</listitem>
+    <title>
+      Procedure for converting a CORBA idl file into a Wireshark
+      dissector
+    </title>
+    <listitem>
+      <para>
+        To write the C code to stdout.
+        <programlisting>idl2wrs  &lt;your_file.idl&gt;</programlisting>
+        e.g.: <programlisting>idl2wrs echo.idl</programlisting>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        To write to a file, just redirect the output.
+        <programlisting>idl2wrs echo.idl > packet-test-idl.c</programlisting>
+        You may wish to comment out the register_giop_user_module() code
+        and that will leave you with heuristic dissection.
+      </para>
+    </listitem>
       </orderedlist>
       <para>
-	If you don't want to use the shell script wrapper, then try
-	steps 3 or 4 instead.</para>
+    If you don't want to use the shell script wrapper, then try
+    steps 3 or 4 instead.</para>
       <orderedlist continuation="continues">
-	<listitem>
-	  <para>To write the C code to stdout.
-	    <programlisting>Usage: omniidl  -p ./ -b wireshark_be &lt;your file.idl&gt;</programlisting>
-	    e.g.:
-	    <programlisting>omniidl  -p ./ -b wireshark_be echo.idl</programlisting>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    To write to a file, just redirect the output.
-	    <programlisting>omniidl  -p ./ -b wireshark_be echo.idl > packet-test-idl.c</programlisting>
-	    You may wish to comment out the register_giop_user_module() code
-	    and that will leave you with heuristic dissection.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Copy the resulting C code to subdirectory epan/dissectors/ inside your
-	    Wireshark source directory.
-	    <programlisting>cp packet-test-idl.c /dir/where/wireshark/lives/epan/dissectors/</programlisting>
-	    The new dissector has to be added to Makefile.common in the same
-	    directory. Look for the declaration CLEAN_DISSECTOR_SRC and add
-	    the new dissector there. For example,
-	    <programlisting>
+    <listitem>
+      <para>To write the C code to stdout.
+        <programlisting>Usage: omniidl  -p ./ -b wireshark_be &lt;your file.idl&gt;</programlisting>
+        e.g.:
+        <programlisting>omniidl  -p ./ -b wireshark_be echo.idl</programlisting>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        To write to a file, just redirect the output.
+        <programlisting>omniidl  -p ./ -b wireshark_be echo.idl > packet-test-idl.c</programlisting>
+        You may wish to comment out the register_giop_user_module() code
+        and that will leave you with heuristic dissection.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Copy the resulting C code to subdirectory epan/dissectors/ inside your
+        Wireshark source directory.
+        <programlisting>cp packet-test-idl.c /dir/where/wireshark/lives/epan/dissectors/</programlisting>
+        The new dissector has to be added to Makefile.common in the same
+        directory. Look for the declaration CLEAN_DISSECTOR_SRC and add
+        the new dissector there. For example,
+        <programlisting>
 CLEAN_DISSECTOR_SRC = \
         packet-2dparityfec.c    \
         packet-3com-njack.c     \
         ...
             </programlisting>
             becomes
-	    <programlisting>
+        <programlisting>
 CLEAN_DISSECTOR_SRC = \
         packet-test-idl.c       \
         packet-2dparityfec.c    \
         packet-3com-njack.c     \
         ...
             </programlisting>
-	  </para>
+      </para>
           <para>
           For the next steps, go up to the top of your Wireshark source directory.
           </para>
-	</listitem>
-	<listitem>
-	  <para>Run configure
-	    <programlisting>./configure (or ./autogen.sh)</programlisting>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para> Compile the code
-	    <programlisting>make</programlisting>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>Good Luck !!</para>
-	</listitem>
+    </listitem>
+    <listitem>
+      <para>Run configure
+        <programlisting>./configure (or ./autogen.sh)</programlisting>
+      </para>
+    </listitem>
+    <listitem>
+      <para> Compile the code
+        <programlisting>make</programlisting>
+      </para>
+    </listitem>
+    <listitem>
+      <para>Good Luck !!</para>
+    </listitem>
       </orderedlist>
     </section>
     <section><title>TODO</title>
       <orderedlist>
-	<listitem>
-	  <para>
-	    Exception code not generated  (yet), but can be added manually.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Enums not converted to symbolic values (yet), but can be added
-	    manually.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>Add command line options etc</para>
-	</listitem>
-	<listitem>
-	  <para>More I am sure :-)</para>
-	</listitem>
+    <listitem>
+      <para>
+        Exception code not generated  (yet), but can be added manually.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Enums not converted to symbolic values (yet), but can be added
+        manually.
+      </para>
+    </listitem>
+    <listitem>
+      <para>Add command line options etc</para>
+    </listitem>
+    <listitem>
+      <para>More I am sure :-)</para>
+    </listitem>
       </orderedlist>
     </section>
     <section><title>Limitations</title>
       <para>
-	See the TODO list inside <filename>packet-giop.c</filename>
+    See the TODO list inside <filename>packet-giop.c</filename>
       </para>
     </section>
     <section><title>Notes</title>
       <orderedlist>
-	<listitem>
-	  <para>
-	    The "-p ./" option passed to omniidl indicates that the
-	    wireshark_be.py and wireshark_gen.py are residing in the
-	    current directory. This may need
-	    tweaking if you place these files somewhere else.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    If it complains about being unable to find some modules
-	    (e.g. tempfile.py),
-	    you may want to check if PYTHONPATH is set correctly.
-	    On my Linux box, it is  PYTHONPATH=/usr/lib/python2.4/
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        The "-p ./" option passed to omniidl indicates that the
+        wireshark_be.py and wireshark_gen.py are residing in the
+        current directory. This may need
+        tweaking if you place these files somewhere else.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If it complains about being unable to find some modules
+        (e.g. tempfile.py),
+        you may want to check if PYTHONPATH is set correctly.
+        On my Linux box, it is  PYTHONPATH=/usr/lib/python2.4/
+      </para>
+    </listitem>
       </orderedlist>
     </section>
   </section>
diff --git a/docbook/wsug_src/WSUG_chapter_advanced.xml b/docbook/wsug_src/WSUG_chapter_advanced.xml
index fdc55aaff1..8cd1f32d83 100644
--- a/docbook/wsug_src/WSUG_chapter_advanced.xml
+++ b/docbook/wsug_src/WSUG_chapter_advanced.xml
@@ -543,7 +543,7 @@
       Windows Sniffer, EtherPeek, AiroPeek, and Sun snoop formats,
       save the arrival time of packets as UTC values. UN*X systems,
       and "Windows NT based" systems (Windows NT 4.0, 2000, XP,
-	  Server 2003, Vista, Server 2008, 7) represent
+      Server 2003, Vista, Server 2008, 7) represent
       time internally as UTC. When Wireshark is capturing, no
       conversion is necessary. However, if the system time zone is
       not set correctly, the system's UTC time might not be
diff --git a/docbook/wsug_src/WSUG_chapter_build_install.xml b/docbook/wsug_src/WSUG_chapter_build_install.xml
index ac0250f6e6..0f17704830 100644
--- a/docbook/wsug_src/WSUG_chapter_build_install.xml
+++ b/docbook/wsug_src/WSUG_chapter_build_install.xml
@@ -9,16 +9,16 @@
       As with all things, there must be a beginning, and so it is with 
       Wireshark. To use Wireshark, you must:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    Obtain a binary package for your operating system, or
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Obtain the source and build Wireshark for your operating system.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Obtain a binary package for your operating system, or
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Obtain the source and build Wireshark for your operating system.
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
     <para>
@@ -35,26 +35,26 @@
     <para>
       The following are the general steps you would use:
       <orderedlist>
-	<listitem>
-	  <para>
-	    Download the relevant package for your needs, e.g. source or 
-	    binary distribution.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Build the source into a binary, if you have downloaded the 
-	    source.
-	  </para>
-	  <para>
-	    This may involve building and/or installing other necessary packages.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Install the binaries into their final destinations.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Download the relevant package for your needs, e.g. source or 
+        binary distribution.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Build the source into a binary, if you have downloaded the 
+        source.
+      </para>
+      <para>
+        This may involve building and/or installing other necessary packages.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Install the binaries into their final destinations.
+      </para>
+    </listitem>
       </orderedlist>
     </para>
   </section>
@@ -71,10 +71,10 @@
     <note>
       <title>Download all required files!</title>
       <para>
-	In general, unless you have already downloaded Wireshark 
-	before, you will most likely need to download several source 
-	packages if you are building Wireshark from source.  This is 
-	covered in more detail below. <!-- Make a ref -->
+    In general, unless you have already downloaded Wireshark 
+    before, you will most likely need to download several source 
+    packages if you are building Wireshark from source.  This is 
+    covered in more detail below. <!-- Make a ref -->
       </para>
     </note>
     <para>
@@ -84,15 +84,15 @@
     <note>
       <title>Note!</title>
       <para>
-	While you will find a number of binary packages available on the 
-	Wireshark web site, you might not find one for your platform, and 
-	they often tend to be several versions behind the current released 
-	version, as they are contributed by people who have the platforms 
-	they are built for.
+    While you will find a number of binary packages available on the 
+    Wireshark web site, you might not find one for your platform, and 
+    they often tend to be several versions behind the current released 
+    version, as they are contributed by people who have the platforms 
+    they are built for.
       </para>
       <para>
-	For this reason, you might want to pull down the source distribution 
-	and build it, as the process is relatively simple.
+    For this reason, you might want to pull down the source distribution 
+    and build it, as the process is relatively simple.
       </para>
     </note>
   </section>
@@ -103,22 +103,22 @@
       Before you build Wireshark from sources, or install a binary package, 
       you must ensure that you have the following other packages installed:
       <itemizedlist>
-	<listitem>
-	  <para>GTK+, The GIMP Tool Kit.</para>
-	  <para>
-	    You will also need Glib.  Both can be obtained from 
-	    <ulink url="http://www.gtk.org">www.gtk.org</ulink>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    libpcap, the packet capture software that Wireshark uses.
-	  </para>
-	  <para>
-	    You can obtain libpcap from 
-	    <ulink url="&TcpdumpWebsite;">www.tcpdump.org</ulink>
-	  </para>
-	</listitem>
+    <listitem>
+      <para>GTK+, The GIMP Tool Kit.</para>
+      <para>
+        You will also need Glib.  Both can be obtained from 
+        <ulink url="http://www.gtk.org">www.gtk.org</ulink>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        libpcap, the packet capture software that Wireshark uses.
+      </para>
+      <para>
+        You can obtain libpcap from 
+        <ulink url="&TcpdumpWebsite;">www.tcpdump.org</ulink>
+      </para>
+    </listitem>
       </itemizedlist>
       Depending on your system, you may be able to install these from 
       binaries, e.g. RPMs, or you may need to obtain them in source code 
@@ -127,9 +127,9 @@
     <para>
       If you have downloaded the source for GTK+, the instructions shown 
       in <xref linkend="Ch02Ex1"/> may provide some help in building it:
-	<example id="Ch02Ex1">
-	  <title>Building GTK+ from source</title>
-	  <programlisting>
+    <example id="Ch02Ex1">
+      <title>Building GTK+ from source</title>
+      <programlisting>
 gzip -dc gtk+-2.21.1.tar.gz | tar xvf -
 &lt;much output removed>
 cd gtk+-2.21.1
@@ -139,36 +139,36 @@ make
 &lt;much output removed>
 make install
 &lt;much output removed>
-	  </programlisting>
-	</example>
-	<note>
-	  <title>Note!</title>
-	  <para>
-	    You may need to change the version number of GTK+ in
-	    <xref linkend="Ch02Ex1"/> to match the version of GTK+ you have 
-	      downloaded. The directory you change to will change if the 
-	      version of GTK+ changes, and in all cases, 
-	      <command>tar xvf -</command> will show you the name of the 
-	      directory you should change to.
-	  </para>
-	</note>
-	<note>
-	  <title>Note!</title>
-	  <para>
-	    If you use Linux, or have GNU <command>tar</command> installed, 
-	    you can use <command>tar zxvf gtk+-2.21.1.tar.gz</command>. It
-	    is also possible to use <command>gunzip -c</command> or 
-	    <command>gzcat</command> rather than <command>gzip -dc</command> 
-	    on many UNIX systems.
-	  </para>
-	</note>
-	<note>
-	  <title>Note!</title>
-	  <para>
-	    If you downloaded GTK+ or any other tar file using Windows,
-	    you may find your file called gtk+-2_21_1_tar.gz.
-	  </para>
-	</note>
+      </programlisting>
+    </example>
+    <note>
+      <title>Note!</title>
+      <para>
+        You may need to change the version number of GTK+ in
+        <xref linkend="Ch02Ex1"/> to match the version of GTK+ you have 
+          downloaded. The directory you change to will change if the 
+          version of GTK+ changes, and in all cases, 
+          <command>tar xvf -</command> will show you the name of the 
+          directory you should change to.
+      </para>
+    </note>
+    <note>
+      <title>Note!</title>
+      <para>
+        If you use Linux, or have GNU <command>tar</command> installed, 
+        you can use <command>tar zxvf gtk+-2.21.1.tar.gz</command>. It
+        is also possible to use <command>gunzip -c</command> or 
+        <command>gzcat</command> rather than <command>gzip -dc</command> 
+        on many UNIX systems.
+      </para>
+    </note>
+    <note>
+      <title>Note!</title>
+      <para>
+        If you downloaded GTK+ or any other tar file using Windows,
+        you may find your file called gtk+-2_21_1_tar.gz.
+      </para>
+    </note>
     </para>
     <para>
       You should consult the GTK+ web site if any errors occur in carrying 
@@ -177,13 +177,13 @@ make install
     <para>
       If you have downloaded the source to libpcap, the general instructions 
       shown in <xref linkend="Ch2Ex2"/>  will assist in building it. Also, 
-	if your operating system does not support <command>tcpdump</command>, 
-	you might also want to download it from the 
-	<ulink url="&TcpdumpWebsite;">tcpdump</ulink> web site and 
-	install it.
-	<example id="Ch2Ex2">
-	  <title>Building and installing libpcap</title>
-	  <programlisting>
+    if your operating system does not support <command>tcpdump</command>, 
+    you might also want to download it from the 
+    <ulink url="&TcpdumpWebsite;">tcpdump</ulink> web site and 
+    install it.
+    <example id="Ch2Ex2">
+      <title>Building and installing libpcap</title>
+      <programlisting>
 gzip -dc libpcap-1.0.0.tar.Z | tar xvf -
 &lt;much output removed>
 cd libpcap-1.0.0
@@ -193,16 +193,16 @@ make
 &lt;much output removed>
 make install
 &lt;much output removed>
-	    </programlisting>
-	</example>
+        </programlisting>
+    </example>
     </para>
     <note>
       <title>Note!</title>
       <para>
-	The directory you should change to will depend on the version of 
-	libpcap you have downloaded.  In all cases, 
-	<command>tar xvf -</command> will show you the name of the 
-	directory that has been unpacked.
+    The directory you should change to will depend on the version of 
+    libpcap you have downloaded.  In all cases, 
+    <command>tar xvf -</command> will show you the name of the 
+    directory that has been unpacked.
       </para>
     </note>
     <para>
@@ -211,38 +211,38 @@ make install
       RPMs. Most Linux systems will install GTK+ and GLib in any case, 
       however you will probably need to install the devel versions of 
       each of these packages. The commands shown in <xref linkend="Ch02Ex4"/> 
-	will install all the needed RPMs if they are not already installed.
-	<example id="Ch02Ex4">
-	  <title>
-	    Installing required RPMs under Red Hat Linux 6.2 and beyond
-	  </title>
-	  <programlisting>
+    will install all the needed RPMs if they are not already installed.
+    <example id="Ch02Ex4">
+      <title>
+        Installing required RPMs under Red Hat Linux 6.2 and beyond
+      </title>
+      <programlisting>
 cd /mnt/cdrom/RedHat/RPMS
 rpm -ivh glib-1.2.6-3.i386.rpm
 rpm -ivh glib-devel-1.2.6-3.i386.rpm
 rpm -ivh gtk+-1.2.6-7.i386.rpm
 rpm -ivh gtk+-devel-1.2.6-7.i386.rpm
 rpm -ivh libpcap-0.4-19.i386.rpm
-	  </programlisting>
-	</example>
+      </programlisting>
+    </example>
     </para>
     <note>
       <para>
-	If you are using a version of Red Hat later than 6.2, the required 
-	RPMs have most likely changed. Simply use the correct RPMs from your 
-	distribution.
+    If you are using a version of Red Hat later than 6.2, the required 
+    RPMs have most likely changed. Simply use the correct RPMs from your 
+    distribution.
       </para>
     </note>
     <para> 
       Under Debian you can install Wireshark using aptitude.  aptitude will
       handle any dependency issues for you. <xref linkend="Ch02Ex5"/> shows 
-	how to do this.
-	<example id="Ch02Ex5">
-	  <title>Installing debs under Debian, Ubuntu and other Debian derivatives</title>
-	  <programlisting>
+    how to do this.
+    <example id="Ch02Ex5">
+      <title>Installing debs under Debian, Ubuntu and other Debian derivatives</title>
+      <programlisting>
 aptitude install wireshark-dev
-	  </programlisting>
-	</example>
+      </programlisting>
+    </example>
     </para>
   </section>
   
@@ -252,78 +252,78 @@ aptitude install wireshark-dev
       Use the following general steps if you are building Wireshark from 
       source under a UNIX operating system:
       <orderedlist>
-	<listitem>
-	  <para>
-	    Unpack the source from its <command>gzip</command>'d 
-	    <command>tar</command> file. If you are using Linux, or your 
-	    version of UNIX uses GNU <command>tar</command>, you can use the 
-	    following command:
-	    <programlisting>
+    <listitem>
+      <para>
+        Unpack the source from its <command>gzip</command>'d 
+        <command>tar</command> file. If you are using Linux, or your 
+        version of UNIX uses GNU <command>tar</command>, you can use the 
+        following command:
+        <programlisting>
 tar zxvf wireshark-&WiresharkCurrentVersion;-tar.gz
-	    </programlisting>
-	  </para>
-	  <para>
-	    For other versions of UNIX, you will want to use the following 
-	    commands:
-	    <programlisting>
+        </programlisting>
+      </para>
+      <para>
+        For other versions of UNIX, you will want to use the following 
+        commands:
+        <programlisting>
 gzip -d wireshark-&WiresharkCurrentVersion;-tar.gz
 tar xvf wireshark-&WiresharkCurrentVersion;-tar
-	    </programlisting>
-	    <note>
-	      <title>Note!</title>
-	      <para>
-		The pipeline 
-		<command>
-		  gzip -dc wireshark-&WiresharkCurrentVersion;-tar.gz | tar xvf -
-		</command> will work here as well.
-	      </para>
-	    </note>
-	    <note>
-	      <title>Note!</title>
-	      <para>
-		If you have downloaded the Wireshark tarball under Windows, 
-		you may find that your browser has created a file with 
-		underscores rather than periods in its file name.
-	      </para>
-	    </note>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Change directory to the Wireshark source directory.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Configure your source so it will build correctly for your 
-	    version of UNIX.  You can do this with the following command:
-	    <programlisting>
+        </programlisting>
+        <note>
+          <title>Note!</title>
+          <para>
+        The pipeline 
+        <command>
+          gzip -dc wireshark-&WiresharkCurrentVersion;-tar.gz | tar xvf -
+        </command> will work here as well.
+          </para>
+        </note>
+        <note>
+          <title>Note!</title>
+          <para>
+        If you have downloaded the Wireshark tarball under Windows, 
+        you may find that your browser has created a file with 
+        underscores rather than periods in its file name.
+          </para>
+        </note>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Change directory to the Wireshark source directory.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Configure your source so it will build correctly for your 
+        version of UNIX.  You can do this with the following command:
+        <programlisting>
 ./configure
-	    </programlisting>
-	  </para>
-	  <para>
-	    If this step fails, you will have to rectify the problems and 
-	    rerun <command>configure</command>.  Troubleshooting hints are 
-	    provided in <xref linkend="ChBuildInstallUnixTrouble"/>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Build the sources into a binary, with the <command>make</command> 
-	    command.  For example:
-	    <programlisting>
+        </programlisting>
+      </para>
+      <para>
+        If this step fails, you will have to rectify the problems and 
+        rerun <command>configure</command>.  Troubleshooting hints are 
+        provided in <xref linkend="ChBuildInstallUnixTrouble"/>.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Build the sources into a binary, with the <command>make</command> 
+        command.  For example:
+        <programlisting>
 make
-	    </programlisting>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Install the software in its final destination, using the command:
-	    <programlisting>
+        </programlisting>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Install the software in its final destination, using the command:
+        <programlisting>
 make install
-	    </programlisting>
-	  </para>
-	</listitem>
+        </programlisting>
+      </para>
+    </listitem>
       </orderedlist>
     </para>
     <para>
@@ -354,7 +354,7 @@ rpm -ivh wireshark-&WiresharkCurrentVersion;.i386.rpm
       If the above step fails because of missing dependencies, install the 
       dependencies first, and then retry the step above.  See 
       <xref linkend="Ch02Ex4"/> for information on what RPMs you will need 
-	to have installed.
+    to have installed.
     </para>
   </section>
 
@@ -376,8 +376,8 @@ dpkg -i wireshark-common_&WiresharkCurrentVersion;.0-1_i386.deb wireshark_&Wires
       dpkg doesn't take care of all dependencies, but reports what's missing.
     </para>
     <note><title>Note!</title>
-	<para>
-	By installing Wireshark packages non-root users won't gain rights
+    <para>
+    By installing Wireshark packages non-root users won't gain rights
         automatically to capture packets. To allow non-root users to capture
         packets follow the procedure described in
         <ulink url="file:///usr/share/doc/wireshark-common/README.Debian">/usr/share/doc/wireshark-common/README.Debian</ulink>
@@ -448,18 +448,18 @@ pkg_add -r wireshark
   <section id="ChBuildInstallWinBuild">
     <title>Building from source under Windows</title>
     <para>
-	  It is recommended to use the binary installer for Windows, 
-	  until you want to start developing Wireshark on the Windows platform.
+      It is recommended to use the binary installer for Windows, 
+      until you want to start developing Wireshark on the Windows platform.
     </para>
     <para>
-	  For further information how to build Wireshark for Windows from the 
-	  sources, have a look at the Developer's Guide on the 
-	  <ulink url="&WiresharkWebSite;/docs/">Documentation Page</ulink>.
+      For further information how to build Wireshark for Windows from the 
+      sources, have a look at the Developer's Guide on the 
+      <ulink url="&WiresharkWebSite;/docs/">Documentation Page</ulink>.
     </para>
     <para>
-	  You may also want to have a look at the Development Wiki:
-	  <ulink url="&WiresharkWikiPage;/Development">&WiresharkWikiPage;/Development</ulink>
-	  for the latest available development documentation.
+      You may also want to have a look at the Development Wiki:
+      <ulink url="&WiresharkWikiPage;/Development">&WiresharkWikiPage;/Development</ulink>
+      for the latest available development documentation.
     </para>
   </section>
   
@@ -468,311 +468,311 @@ pkg_add -r wireshark
     <para>
       In this section we explore installing Wireshark under Windows from the 
       binary packages.  
-	</para>
+    </para>
   <section id="ChBuildInstallWireshark">
     <title>Install Wireshark</title>
-	<para>
-	You may acquire a binary installer of Wireshark named something like: 
-	<filename>wireshark-winxx-&WiresharkCurrentVersion;.x.exe</filename>.
-	The Wireshark installer includes WinPcap, so you don't need to download 
-	and install two separate packages.
-	</para>
-	<para>
+    <para>
+    You may acquire a binary installer of Wireshark named something like: 
+    <filename>wireshark-winxx-&WiresharkCurrentVersion;.x.exe</filename>.
+    The Wireshark installer includes WinPcap, so you don't need to download 
+    and install two separate packages.
+    </para>
+    <para>
     Simply download the Wireshark installer from:
     <ulink url="&WiresharkBinariesPage;">&WiresharkBinariesPage;</ulink> 
-	and execute it.
-	Beside the usual installer options like where to install the program, 
-	there are several optional components.
+    and execute it.
+    Beside the usual installer options like where to install the program, 
+    there are several optional components.
     </para>
     <tip><title>Tip: Just keep the defaults!</title>
-	<para>
-	If you are unsure which settings to select, just keep the defaults.
+    <para>
+    If you are unsure which settings to select, just keep the defaults.
     </para>
-	</tip>
+    </tip>
   <section id="ChBuildInstallComponents">
     <title>"Choose Components" page</title>
     <para>
-	<command>Wireshark</command>
-	<itemizedlist>
-	<listitem><para>
-	<command>Wireshark GTK</command> - Wireshark is a GUI network protocol 
-	analyzer.
-	</para></listitem>
-	</itemizedlist>
-	</para>
-	<para>
-	<command>TShark</command> - TShark is a command-line based network 
-	protocol analyzer.
-	</para>
-	<para>
-	<command>Plugins / Extensions</command> (for the Wireshark and TShark 
-	dissection engines):
-	<itemizedlist>
-	<listitem><para>
-	<command>Dissector Plugins</command> - Plugins with some extended dissections.
-	</para></listitem>
-	<listitem><para>
-	<command>Tree Statistics Plugins</command> - Plugins with some extended statistics.
-	</para></listitem>
-	<listitem><para>
-	<command>Mate - Meta Analysis and Tracing Engine (experimental)</command> 
-	- user configurable extension(s) of the display filter engine, see 
-	<ulink url="&WiresharkWikiPage;/Mate">&WiresharkWikiPage;/Mate</ulink>
-	for details.
-	</para></listitem>
-	<listitem><para>
-	<command>SNMP MIBs</command> - SNMP MIBs for a more detailed SNMP 
-	dissection.
-	</para></listitem>
-	</itemizedlist>
-	<command>Tools</command> (additional command line tools to work with 
-	capture files):
-	<itemizedlist>
-	<listitem><para>
-	<command>Editcap</command> - Editcap is a program that reads a capture 
-	file and writes some or all of the packets into another capture file.
-	</para></listitem>
-	<listitem><para>
-	<command>Text2Pcap</command> - Text2pcap is a program that reads in an 
-	ASCII hex dump and writes the data into a libpcap-style capture file.
-	</para></listitem>
-	<listitem><para>
-	<command>Mergecap</command> - Mergecap is a program that combines multiple 
-	saved capture files into a single output file.
-	</para></listitem>
-	<listitem><para>
-	<command>Capinfos</command> - Capinfos is a program that provides 
-	information on capture files.
-	</para></listitem>
-	<listitem><para>
-	<command>Rawshark</command> - Rawshark is a raw packet filter.
-	</para></listitem>
-	</itemizedlist>
-    </para>
-	<para>
-	<command>User's Guide</command> -
-	Local installation of the User's Guide. The Help buttons on most dialogs 
-	will require an internet connection to show help pages if the User's Guide 
-	is not installed locally.
-	</para>
+    <command>Wireshark</command>
+    <itemizedlist>
+    <listitem><para>
+    <command>Wireshark GTK</command> - Wireshark is a GUI network protocol 
+    analyzer.
+    </para></listitem>
+    </itemizedlist>
+    </para>
+    <para>
+    <command>TShark</command> - TShark is a command-line based network 
+    protocol analyzer.
+    </para>
+    <para>
+    <command>Plugins / Extensions</command> (for the Wireshark and TShark 
+    dissection engines):
+    <itemizedlist>
+    <listitem><para>
+    <command>Dissector Plugins</command> - Plugins with some extended dissections.
+    </para></listitem>
+    <listitem><para>
+    <command>Tree Statistics Plugins</command> - Plugins with some extended statistics.
+    </para></listitem>
+    <listitem><para>
+    <command>Mate - Meta Analysis and Tracing Engine (experimental)</command> 
+    - user configurable extension(s) of the display filter engine, see 
+    <ulink url="&WiresharkWikiPage;/Mate">&WiresharkWikiPage;/Mate</ulink>
+    for details.
+    </para></listitem>
+    <listitem><para>
+    <command>SNMP MIBs</command> - SNMP MIBs for a more detailed SNMP 
+    dissection.
+    </para></listitem>
+    </itemizedlist>
+    <command>Tools</command> (additional command line tools to work with 
+    capture files):
+    <itemizedlist>
+    <listitem><para>
+    <command>Editcap</command> - Editcap is a program that reads a capture 
+    file and writes some or all of the packets into another capture file.
+    </para></listitem>
+    <listitem><para>
+    <command>Text2Pcap</command> - Text2pcap is a program that reads in an 
+    ASCII hex dump and writes the data into a libpcap-style capture file.
+    </para></listitem>
+    <listitem><para>
+    <command>Mergecap</command> - Mergecap is a program that combines multiple 
+    saved capture files into a single output file.
+    </para></listitem>
+    <listitem><para>
+    <command>Capinfos</command> - Capinfos is a program that provides 
+    information on capture files.
+    </para></listitem>
+    <listitem><para>
+    <command>Rawshark</command> - Rawshark is a raw packet filter.
+    </para></listitem>
+    </itemizedlist>
+    </para>
+    <para>
+    <command>User's Guide</command> -
+    Local installation of the User's Guide. The Help buttons on most dialogs 
+    will require an internet connection to show help pages if the User's Guide 
+    is not installed locally.
+    </para>
   </section>
   <section id="ChBuildInstallAdditionalTasks">
     <title>"Additional Tasks" page</title>
     <para>
-	<itemizedlist>
-	<listitem><para>
-	<command>Start Menu Shortcuts</command> - add some start menu shortcuts.
-	</para></listitem>
-	<listitem><para>
-	<command>Desktop Icon</command> - add a Wireshark icon to the desktop.
-	</para></listitem>
-	<listitem><para>
-	<command>Quick Launch Icon</command> - add a Wireshark icon to the 
-	Explorer quick launch toolbar.
-	</para></listitem>
-	<listitem><para>
-	<command>Associate file extensions to Wireshark</command> - Associate 
-	standard network trace files to Wireshark.
-	</para></listitem>
-	</itemizedlist>
-    </para>
-	</section>
-	<section id="ChBuildInstallWinPcap">
+    <itemizedlist>
+    <listitem><para>
+    <command>Start Menu Shortcuts</command> - add some start menu shortcuts.
+    </para></listitem>
+    <listitem><para>
+    <command>Desktop Icon</command> - add a Wireshark icon to the desktop.
+    </para></listitem>
+    <listitem><para>
+    <command>Quick Launch Icon</command> - add a Wireshark icon to the 
+    Explorer quick launch toolbar.
+    </para></listitem>
+    <listitem><para>
+    <command>Associate file extensions to Wireshark</command> - Associate 
+    standard network trace files to Wireshark.
+    </para></listitem>
+    </itemizedlist>
+    </para>
+    </section>
+    <section id="ChBuildInstallWinPcap">
     <title>"Install WinPcap?" page</title>
     <para>
-	The Wireshark installer contains the latest released WinPcap installer.
-    </para>
-    <para>
-	If you don't have WinPcap installed, you won't be able to capture live 
-	network traffic, but you will still be able to open saved capture files.
-    </para>
-    <para>
-	<itemizedlist>
-	<listitem><para>
-	<command>Currently installed WinPcap version</command> - the Wireshark 
-	installer detects the currently installed WinPcap version. 
-	</para></listitem>
-	<listitem><para>
-	<command>Install WinPcap x.x</command> - if the currently installed 
-	version is older than the one which comes with the Wireshark installer 
-	(or WinPcap is not installed at all), this will be selected by default.
-	</para></listitem>
-	<listitem><para>
-	<command>Start WinPcap service "NPF" at startup</command> - so users 
-	without administrative privileges can capture.
-	</para></listitem>
-	</itemizedlist>
-	
-    </para>
-	<para>
-	More WinPcap info:
-	<itemizedlist>
-	<listitem><para>
-	Wireshark related:
-	<ulink url="&WiresharkWikiPage;/WinPcap">&WiresharkWikiPage;/WinPcap</ulink>
-	</para></listitem>
-	<listitem><para>
-	General WinPcap info: 
-	<ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink>
-	</para></listitem>
-	</itemizedlist>
-	</para>
-	</section>
-	<section id="ChBuildInstallWiresharkCommandLine">
+    The Wireshark installer contains the latest released WinPcap installer.
+    </para>
+    <para>
+    If you don't have WinPcap installed, you won't be able to capture live 
+    network traffic, but you will still be able to open saved capture files.
+    </para>
+    <para>
+    <itemizedlist>
+    <listitem><para>
+    <command>Currently installed WinPcap version</command> - the Wireshark 
+    installer detects the currently installed WinPcap version. 
+    </para></listitem>
+    <listitem><para>
+    <command>Install WinPcap x.x</command> - if the currently installed 
+    version is older than the one which comes with the Wireshark installer 
+    (or WinPcap is not installed at all), this will be selected by default.
+    </para></listitem>
+    <listitem><para>
+    <command>Start WinPcap service "NPF" at startup</command> - so users 
+    without administrative privileges can capture.
+    </para></listitem>
+    </itemizedlist>
+    
+    </para>
+    <para>
+    More WinPcap info:
+    <itemizedlist>
+    <listitem><para>
+    Wireshark related:
+    <ulink url="&WiresharkWikiPage;/WinPcap">&WiresharkWikiPage;/WinPcap</ulink>
+    </para></listitem>
+    <listitem><para>
+    General WinPcap info: 
+    <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink>
+    </para></listitem>
+    </itemizedlist>
+    </para>
+    </section>
+    <section id="ChBuildInstallWiresharkCommandLine">
     <title>Command line options</title>
     <para>
-	You can simply start the Wireshark installer without any command line 
-	parameters, it will show you the usual interactive installer.
-    </para>
-    <para>
-	For special cases, there are some command line parameters available:
-    </para>
-	<itemizedlist>
-	<listitem>
-		<para>
-		<command>/NCRC</command> disables the CRC check
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-		<command>/S</command> runs the installer or uninstaller silently with 
-		default values. Please note: The silent installer won't install WinPCap!
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-		<command>/desktopicon</command> installation of the desktop icon, 
-		<command>=yes</command> - force installation, <command>=no</command> - 
-		don't install, otherwise use defaults / user settings.
-		This option can be useful for a silent installer. 
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-		<command>/quicklaunchicon</command> installation of the quick launch icon, 
-		<command>=yes</command> - force installation, <command>=no</command> - 
-		don't install, otherwise use defaults / user settings.
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-		<command>/D</command> sets the default installation directory 
-		($INSTDIR), overriding 
-		InstallDir and InstallDirRegKey. It must be the last parameter used in 
-		the command line and must not contain any quotes, even if the path 
-		contains spaces.
-		</para>
-	</listitem>
-	</itemizedlist>
-	<para> Example:
+    You can simply start the Wireshark installer without any command line 
+    parameters, it will show you the usual interactive installer.
+    </para>
+    <para>
+    For special cases, there are some command line parameters available:
+    </para>
+    <itemizedlist>
+    <listitem>
+        <para>
+        <command>/NCRC</command> disables the CRC check
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+        <command>/S</command> runs the installer or uninstaller silently with 
+        default values. Please note: The silent installer won't install WinPCap!
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+        <command>/desktopicon</command> installation of the desktop icon, 
+        <command>=yes</command> - force installation, <command>=no</command> - 
+        don't install, otherwise use defaults / user settings.
+        This option can be useful for a silent installer. 
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+        <command>/quicklaunchicon</command> installation of the quick launch icon, 
+        <command>=yes</command> - force installation, <command>=no</command> - 
+        don't install, otherwise use defaults / user settings.
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+        <command>/D</command> sets the default installation directory 
+        ($INSTDIR), overriding 
+        InstallDir and InstallDirRegKey. It must be the last parameter used in 
+        the command line and must not contain any quotes, even if the path 
+        contains spaces.
+        </para>
+    </listitem>
+    </itemizedlist>
+    <para> Example:
     <programlisting>
 wireshark-win32-&WiresharkCurrentVersion;.0.exe /NCRC /S /desktopicon=yes
   /quicklaunchicon=no /D=C:\Program Files\Foo
-	</programlisting>
-	</para>
-	</section>  
+    </programlisting>
+    </para>
+    </section>  
   </section>
   
   <section id="ChBuildInstallWinPcapManually">
     <title>Manual WinPcap Installation</title>
     <note><title>Note!</title>
-	<para>
-	<command>As mentioned above, the Wireshark installer 
-	takes care of the installation of WinPcap, 
-	so usually you don't have to worry about WinPcap at all!</command> 
+    <para>
+    <command>As mentioned above, the Wireshark installer 
+    takes care of the installation of WinPcap, 
+    so usually you don't have to worry about WinPcap at all!</command> 
     </para>
-	</note>
+    </note>
     <para>
-	The following is only necessary if you want to 
-	try a different version than the one included in the Wireshark installer, 
-	e.g. because a new WinPcap (beta) version was released.
+    The following is only necessary if you want to 
+    try a different version than the one included in the Wireshark installer, 
+    e.g. because a new WinPcap (beta) version was released.
     </para>
     <para>
-	Additional WinPcap versions (including newer alpha or beta releases)
-	can be downloaded from the following locations:
-	<itemizedlist>
-	<listitem><para>
+    Additional WinPcap versions (including newer alpha or beta releases)
+    can be downloaded from the following locations:
+    <itemizedlist>
+    <listitem><para>
     The main WinPcap site: 
-	<ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink>
-	</para></listitem>
-	<listitem><para>
+    <ulink url="&WinPcapWebsite;">&WinPcapWebsite;</ulink>
+    </para></listitem>
+    <listitem><para>
     The Wiretapped.net mirror:
-	<ulink url="http://www.mirrors.wiretapped.net/security/packet-capture/winpcap">
-	http://www.mirrors.wiretapped.net/security/packet-capture/winpcap</ulink>
-	</para></listitem>
-	</itemizedlist>
+    <ulink url="http://www.mirrors.wiretapped.net/security/packet-capture/winpcap">
+    http://www.mirrors.wiretapped.net/security/packet-capture/winpcap</ulink>
+    </para></listitem>
+    </itemizedlist>
     </para>
     <para>
-	At the download page you will find a single installer exe called something 
-	like "auto-installer", which can be installed under various Windows 
-	systems, including NT4.0/2000/XP/2003/Vista/7/2008.
-	</para>
+    At the download page you will find a single installer exe called something 
+    like "auto-installer", which can be installed under various Windows 
+    systems, including NT4.0/2000/XP/2003/Vista/7/2008.
+    </para>
   </section>
   
   <section id="ChBuildInstallWinWiresharkUpdate">
     <title>Update Wireshark</title>
-	<para>
-	From time to time you may want to update your installed Wireshark to a more
-	recent version. If you join Wireshark's announce mailing list, you will be 
-	informed about new Wireshark versions, see <xref 
-	linkend="ChIntroMailingLists"/> for details how to subscribe to this list.
+    <para>
+    From time to time you may want to update your installed Wireshark to a more
+    recent version. If you join Wireshark's announce mailing list, you will be 
+    informed about new Wireshark versions, see <xref 
+    linkend="ChIntroMailingLists"/> for details how to subscribe to this list.
     </para>
     <para>
-	New versions of Wireshark usually become available every 4 to 8 months.
-	Updating Wireshark is done the same way as installing it, you simply 
-	download and start the installer exe. A reboot is usually not required and
-	all your personal settings remain unchanged.
+    New versions of Wireshark usually become available every 4 to 8 months.
+    Updating Wireshark is done the same way as installing it, you simply 
+    download and start the installer exe. A reboot is usually not required and
+    all your personal settings remain unchanged.
     </para>
   </section>
   
   <section id="ChBuildInstallWinPcapUpdate">
     <title>Update WinPcap</title>
     <para>
-	New versions of WinPcap are less frequently available, maybe only once in a 
-	year. You will find WinPcap update instructions where you can download new 
-	WinPcap versions. Usually you have to reboot the machine after installing 
-	a new WinPcap version.
-    </para>
-	<warning><title>Warning!</title>
-	<para>
-	If you have an older version of WinPcap installed, you must uninstall it 
-	before installing the current version. Recent versions of the WinPcap 
-	installer will take care of this.
-	</para>
-	</warning>
+    New versions of WinPcap are less frequently available, maybe only once in a 
+    year. You will find WinPcap update instructions where you can download new 
+    WinPcap versions. Usually you have to reboot the machine after installing 
+    a new WinPcap version.
+    </para>
+    <warning><title>Warning!</title>
+    <para>
+    If you have an older version of WinPcap installed, you must uninstall it 
+    before installing the current version. Recent versions of the WinPcap 
+    installer will take care of this.
+    </para>
+    </warning>
   </section>
   
   <section id="ChBuildInstallWinUninstall">
     <title>Uninstall Wireshark</title>
     <para>
-	You can uninstall Wireshark the usual way, using the "Add or Remove 
-	Programs" option inside the Control Panel. Select the "Wireshark" entry to 
-	start the uninstallation procedure.
+    You can uninstall Wireshark the usual way, using the "Add or Remove 
+    Programs" option inside the Control Panel. Select the "Wireshark" entry to 
+    start the uninstallation procedure.
     </para>
     <para>
-	The Wireshark uninstaller will provide several options as to which things are to be 
-	uninstalled; the default is to remove the core components but keep the personal 
-	settings, WinPcap and alike.
+    The Wireshark uninstaller will provide several options as to which things are to be 
+    uninstalled; the default is to remove the core components but keep the personal 
+    settings, WinPcap and alike.
     </para>
     <para>
-	WinPcap won't be uninstalled by default, as other programs than Wireshark 
-	may use it as well.
+    WinPcap won't be uninstalled by default, as other programs than Wireshark 
+    may use it as well.
     </para>
   </section>
   
   <section id="ChBuildInstallWinPcapUninstall">
     <title>Uninstall WinPcap</title>
     <para>
-	You can uninstall WinPcap independently of Wireshark, using the "WinPcap" 
-	entry in the "Add or Remove Programs" of the Control Panel.
+    You can uninstall WinPcap independently of Wireshark, using the "WinPcap" 
+    entry in the "Add or Remove Programs" of the Control Panel.
     </para>
-	<note><title>Note!</title>
+    <note><title>Note!</title>
     <para>
-	After uninstallation of WinPcap you can't capture anything with Wireshark.
+    After uninstallation of WinPcap you can't capture anything with Wireshark.
     </para>
-	</note>
+    </note>
     <para>
-	It might be a good idea to reboot Windows afterwards.
+    It might be a good idea to reboot Windows afterwards.
     </para>
   </section>
   </section>
diff --git a/docbook/wsug_src/WSUG_chapter_capture.xml b/docbook/wsug_src/WSUG_chapter_capture.xml
index 70e8fe48e1..c031da3db7 100644
--- a/docbook/wsug_src/WSUG_chapter_capture.xml
+++ b/docbook/wsug_src/WSUG_chapter_capture.xml
@@ -3,601 +3,600 @@
 
 <chapter id="ChapterCapture">
   <title>Capturing Live Network Data</title>
-  
   <section id="ChCapIntroduction">
-	<title>Introduction</title>
-	<para>
-	Capturing live network data is one of the major features of Wireshark.
-	</para>
-	<para>
-	The Wireshark capture engine provides the following features:
-	</para>
-	<para>
-	<itemizedlist>
-	<listitem><para>
-	Capture from different kinds of network hardware (Ethernet, Token Ring, 
-	ATM, ...).
-	</para></listitem>
-	<listitem><para>
-	Stop the capture on different triggers like: amount of captured data, 
-	captured time, captured number of packets.
-	</para></listitem>
-	<listitem><para>
-	Simultaneously show decoded packets while Wireshark keeps on capturing.
-	</para></listitem>
-	<listitem><para>
-	Filter packets, reducing the amount of data to be captured, see <xref 
-	linkend="ChCapCaptureFilterSection"/>.
-	</para></listitem>
-	<listitem><para>
-	Capturing into multiple files while doing a long term capture, and in 
-	addition the option to form a ringbuffer of these files, keeping only 
-	the last x files, useful for a "very long term" capture, see <xref 
-	linkend="ChCapCaptureFiles"/>.
-	</para></listitem>
-	<listitem><para>
-	Simultaneous capturing from multiple network interfaces.
-	</para></listitem>
-	</itemizedlist>
-	The capture engine still lacks the following features:
-	<itemizedlist>
-	<listitem><para>
-	Stop capturing (or doing some other action), depending on the captured 
-	data.
-	</para></listitem>
-	</itemizedlist>
-	</para>
+    <title>Introduction</title>
+    <para>
+    Capturing live network data is one of the major features of Wireshark.
+    </para>
+    <para>
+    The Wireshark capture engine provides the following features:
+    </para>
+    <para>
+    <itemizedlist>
+    <listitem><para>
+    Capture from different kinds of network hardware (Ethernet, Token Ring, 
+    ATM, ...).
+    </para></listitem>
+    <listitem><para>
+    Stop the capture on different triggers like: amount of captured data, 
+    captured time, captured number of packets.
+    </para></listitem>
+    <listitem><para>
+    Simultaneously show decoded packets while Wireshark keeps on capturing.
+    </para></listitem>
+    <listitem><para>
+    Filter packets, reducing the amount of data to be captured, see <xref 
+    linkend="ChCapCaptureFilterSection"/>.
+    </para></listitem>
+    <listitem><para>
+    Capturing into multiple files while doing a long term capture, and in 
+    addition the option to form a ringbuffer of these files, keeping only 
+    the last x files, useful for a "very long term" capture, see <xref 
+    linkend="ChCapCaptureFiles"/>.
+    </para></listitem>
+    <listitem><para>
+    Simultaneous capturing from multiple network interfaces.
+    </para></listitem>
+    </itemizedlist>
+    The capture engine still lacks the following features:
+    <itemizedlist>
+    <listitem><para>
+    Stop capturing (or doing some other action), depending on the captured 
+    data.
+    </para></listitem>
+    </itemizedlist>
+    </para>
   </section>
 
   <section id="ChCapPrerequisitesSection"><title>Prerequisites</title>
     <para>
-	Setting up Wireshark to capture packets for the first time can be tricky. 
-	</para>
-	<tip><title>Tip!</title><para>
-	A comprehensive guide "How To setup a Capture" is available at:
-	<ulink url="&WiresharkWikiPage;/CaptureSetup">&WiresharkWikiPage;/CaptureSetup</ulink>.
-	</para></tip>
-	<para>
-	Here are some common pitfalls:
+    Setting up Wireshark to capture packets for the first time can be tricky. 
+    </para>
+    <tip><title>Tip!</title><para>
+    A comprehensive guide "How To setup a Capture" is available at:
+    <ulink url="&WiresharkWikiPage;/CaptureSetup">&WiresharkWikiPage;/CaptureSetup</ulink>.
+    </para></tip>
+    <para>
+    Here are some common pitfalls:
       <itemizedlist>
-	<listitem>
-	  <para>
-		You need to have root / Administrator privileges to start a live 
-		capture.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		You need to choose the right network interface to capture packet data 
-		from.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		You need to capture at the right place in the network to see the 
-		traffic you want to see.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		... and a lot more!.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        You need to have root / Administrator privileges to start a live 
+        capture.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You need to choose the right network interface to capture packet data 
+        from.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You need to capture at the right place in the network to see the 
+        traffic you want to see.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        ... and a lot more!.
+      </para>
+    </listitem>
       </itemizedlist>
-	</para>
-	<para>
-	If you have any problems setting up your capture environment, you should 
-	have a look at the guide mentioned above.
-	</para>
+    </para>
+    <para>
+    If you have any problems setting up your capture environment, you should 
+    have a look at the guide mentioned above.
+    </para>
   </section>
 
   <section id="ChCapCapturingSection"><title>Start Capturing</title>
     <para>
       One of the following methods can be used to start capturing packets with 
-	  Wireshark:
+      Wireshark:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    You can get an overview of the available local interfaces using the 
-		"<inlinegraphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/>
-		Capture Interfaces" dialog box, see 
-		<xref linkend="ChCapCaptureInterfacesDialogWin32"/> or 
-		<xref linkend="ChCapCaptureInterfacesDialog"/>. You can start a 
-		capture from this dialog box, using (one of) the "Capture" button(s).
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    You can start capturing using the 
-		"<inlinegraphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/>
-		Capture Options" dialog box, see 
-		<xref linkend="ChCapCaptureOptionsDialog"/>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    If you have selected the right capture options before, you can 
-		immediately start a capture using the 
-		"<inlinegraphic entityref="WiresharkToolbarCaptureStart" format="PNG"/>
-		Capture Start" menu / toolbar item. The capture
-		process will start immediately.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    If you already know the name of the capture interface, you can start 
-		Wireshark from the command line and use the following:
-	    <programlisting>
+    <listitem>
+      <para>
+        You can get an overview of the available local interfaces using the 
+        "<inlinegraphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/>
+        Capture Interfaces" dialog box, see 
+        <xref linkend="ChCapCaptureInterfacesDialogWin32"/> or 
+        <xref linkend="ChCapCaptureInterfacesDialog"/>. You can start a 
+        capture from this dialog box, using (one of) the "Capture" button(s).
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        You can start capturing using the 
+        "<inlinegraphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/>
+        Capture Options" dialog box, see 
+        <xref linkend="ChCapCaptureOptionsDialog"/>.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If you have selected the right capture options before, you can 
+        immediately start a capture using the 
+        "<inlinegraphic entityref="WiresharkToolbarCaptureStart" format="PNG"/>
+        Capture Start" menu / toolbar item. The capture
+        process will start immediately.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If you already know the name of the capture interface, you can start 
+        Wireshark from the command line and use the following:
+        <programlisting>
 wireshark -i eth0 -k
-	    </programlisting>
-		This will start Wireshark capturing on interface eth0, more details 
-		can be found at: <xref linkend="ChCustCommandLine"/>.
-	  </para>
-	</listitem>
+        </programlisting>
+        This will start Wireshark capturing on interface eth0, more details 
+        can be found at: <xref linkend="ChCustCommandLine"/>.
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
     </section>
 
   <section id="ChCapInterfaceSection">
-	<title>The "Capture Interfaces" dialog box</title>
-	<para>
-	When you select "Interfaces..." from the Capture menu, Wireshark pops 
-	up the "Capture Interfaces" dialog box as shown in 
-	<xref linkend="ChCapCaptureInterfacesDialogWin32"/> or 
-	<xref linkend="ChCapCaptureInterfacesDialog"/>.
-	<warning><title>This dialog consumes lots of system resources!</title>
-	<para>
-	As the "Capture Interfaces" dialog is showing live captured data, it is 
-	consuming a lot of system resources. Close this dialog as soon as 
-	possible to prevent excessive system load.
-	</para>
-	</warning>
-	<note><title>Not all available interfaces may be displayed!</title>
-	<para>
-	This dialog box will only show the local interfaces Wireshark knows 
-	of. It will not show interfaces marked as hidden in <xref linkend="ChCustInterfaceOptionsSection"/>.
-	As Wireshark might not be able to detect all local interfaces, and it 
-	cannot detect the remote interfaces available, there could be more capture 
-	interfaces available than listed.
-	</para>
-	</note>
-	</para>
-	<para>
-	As it is possible to simultaneously capture packets from multiple interfaces,
-	the toggle buttons can be used to select one or more interfaces. 
-	</para>
-	<figure id="ChCapCaptureInterfacesDialogWin32">
-	<title>The "Capture Interfaces" dialog box on Microsoft Windows</title>
-	<graphic entityref="WiresharkCaptureInterfacesDialogWin32" format="PNG"/>
-	</figure>
-	<figure id="ChCapCaptureInterfacesDialog">
-	<title>The "Capture Interfaces" dialog box on Unix/Linux</title>
-	<graphic entityref="WiresharkCaptureInterfacesDialog" format="PNG"/>
-	</figure>
-	<variablelist>
-	  <varlistentry><term><command>Device (Unix/Linux only)</command></term>
-	    <listitem>
-	      <para>
-		  The interface device name.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Description</command></term>
-	    <listitem>
-	      <para>
-		  The interface description provided by the operating system, or the 
-		  user defined comment added in <xref linkend="ChCustInterfaceOptionsSection"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>IP</command></term>
-	    <listitem>
-	      <para>
-		  The first IP address Wireshark could find for this interface.
-		  You can click on the address to cycle through other addresses
-		  assigned to it, if available.
-		  If no address could be found "none" will be displayed.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Packets</command></term>
-	    <listitem>
-	      <para>
-		  The number of packets captured from this interface, since this 
-		  dialog was opened. Will be greyed out, if no packet was captured 
-		  in the last second.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Packets/s</command></term>
-	    <listitem>
-	      <para>
-		  Number of packets captured in the last second. Will be greyed out, 
-		  if no packet was captured in the last second.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Stop</command></term>
-	    <listitem>
-	      <para>
-		  Stop a currently running capture.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Start</command></term>
-	    <listitem>
-	      <para>
-		  Start a capture on all selected interfaces immediately, using the settings 
-		  from the last capture or the default settings, if no options have been
-		  set.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Options</command></term>
-	    <listitem>
-	      <para>
-		  Open the Capture Options dialog with the marked interfaces selected, see 
-		  <xref linkend="ChCapCaptureOptions"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Details (Microsoft Windows only)</command></term>
-	    <listitem>
-	      <para>
-		  Open a dialog with detailed information about the interface, see
-		  <xref linkend="ChCapInterfaceDetailsSection"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Help</command></term>
-	    <listitem>
-	      <para>
-		  Show this help page.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Close</command></term>
-	    <listitem>
-	      <para>
-		  Close this dialog box.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+    <title>The "Capture Interfaces" dialog box</title>
+    <para>
+    When you select "Interfaces..." from the Capture menu, Wireshark pops 
+    up the "Capture Interfaces" dialog box as shown in 
+    <xref linkend="ChCapCaptureInterfacesDialogWin32"/> or 
+    <xref linkend="ChCapCaptureInterfacesDialog"/>.
+    <warning><title>This dialog consumes lots of system resources!</title>
+    <para>
+    As the "Capture Interfaces" dialog is showing live captured data, it is 
+    consuming a lot of system resources. Close this dialog as soon as 
+    possible to prevent excessive system load.
+    </para>
+    </warning>
+    <note><title>Not all available interfaces may be displayed!</title>
+    <para>
+    This dialog box will only show the local interfaces Wireshark knows 
+    of. It will not show interfaces marked as hidden in <xref linkend="ChCustInterfaceOptionsSection"/>.
+    As Wireshark might not be able to detect all local interfaces, and it 
+    cannot detect the remote interfaces available, there could be more capture 
+    interfaces available than listed.
+    </para>
+    </note>
+    </para>
+    <para>
+    As it is possible to simultaneously capture packets from multiple interfaces,
+    the toggle buttons can be used to select one or more interfaces. 
+    </para>
+    <figure id="ChCapCaptureInterfacesDialogWin32">
+    <title>The "Capture Interfaces" dialog box on Microsoft Windows</title>
+    <graphic entityref="WiresharkCaptureInterfacesDialogWin32" format="PNG"/>
+    </figure>
+    <figure id="ChCapCaptureInterfacesDialog">
+    <title>The "Capture Interfaces" dialog box on Unix/Linux</title>
+    <graphic entityref="WiresharkCaptureInterfacesDialog" format="PNG"/>
+    </figure>
+    <variablelist>
+      <varlistentry><term><command>Device (Unix/Linux only)</command></term>
+        <listitem>
+          <para>
+          The interface device name.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Description</command></term>
+        <listitem>
+          <para>
+          The interface description provided by the operating system, or the 
+          user defined comment added in <xref linkend="ChCustInterfaceOptionsSection"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>IP</command></term>
+        <listitem>
+          <para>
+          The first IP address Wireshark could find for this interface.
+          You can click on the address to cycle through other addresses
+          assigned to it, if available.
+          If no address could be found "none" will be displayed.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Packets</command></term>
+        <listitem>
+          <para>
+          The number of packets captured from this interface, since this 
+          dialog was opened. Will be greyed out, if no packet was captured 
+          in the last second.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Packets/s</command></term>
+        <listitem>
+          <para>
+          Number of packets captured in the last second. Will be greyed out, 
+          if no packet was captured in the last second.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Stop</command></term>
+        <listitem>
+          <para>
+          Stop a currently running capture.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Start</command></term>
+        <listitem>
+          <para>
+          Start a capture on all selected interfaces immediately, using the settings 
+          from the last capture or the default settings, if no options have been
+          set.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Options</command></term>
+        <listitem>
+          <para>
+          Open the Capture Options dialog with the marked interfaces selected, see 
+          <xref linkend="ChCapCaptureOptions"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Details (Microsoft Windows only)</command></term>
+        <listitem>
+          <para>
+          Open a dialog with detailed information about the interface, see
+          <xref linkend="ChCapInterfaceDetailsSection"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Help</command></term>
+        <listitem>
+          <para>
+          Show this help page.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Close</command></term>
+        <listitem>
+          <para>
+          Close this dialog box.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
   </section>
 
     <section id="ChCapCaptureOptions">
       <title>The "Capture Options" dialog box</title>
       <para>
-	When you select Options... from the Capture menu (or use the corresponding 
-	item in the "Main" toolbar), Wireshark pops 
-	up the "Capture Options" dialog box as shown in 
-	<xref linkend="ChCapCaptureOptionsDialog"/>.
+    When you select Options... from the Capture menu (or use the corresponding 
+    item in the "Main" toolbar), Wireshark pops 
+    up the "Capture Options" dialog box as shown in 
+    <xref linkend="ChCapCaptureOptionsDialog"/>.
       </para>
       <figure id="ChCapCaptureOptionsDialog">
-	<title>The "Capture Options" dialog box</title>
-	<graphic entityref="WiresharkCaptureOptionsDialog"/>
+    <title>The "Capture Options" dialog box</title>
+    <graphic entityref="WiresharkCaptureOptionsDialog"/>
       </figure>
-	<tip><title>Tip!</title>
-	<para>
-	If you are unsure which options to choose in this dialog box, just try 
-	keeping the defaults as this should work well in many cases.
-	</para>
-	</tip>
-	<section><title>Capture frame</title>
-	<para>
-	The table shows the settings for all available interfaces:
- 	<itemizedlist>
-	    <listitem>
-	      <para>
-			The name of the interface and its IP addresses. If no address could 
-		  	be resolved from the system, "none" will be shown.
-	      </para>
-		<note>
-		  <title>Note</title>
-		  <para>loopback interfaces are not available on Windows platforms.</para>
-		  </note>
-	    </listitem>
-	    <listitem>
+    <tip><title>Tip!</title>
+    <para>
+    If you are unsure which options to choose in this dialog box, just try 
+    keeping the defaults as this should work well in many cases.
+    </para>
+    </tip>
+    <section><title>Capture frame</title>
+    <para>
+    The table shows the settings for all available interfaces:
+     <itemizedlist>
+        <listitem>
+          <para>
+            The name of the interface and its IP addresses. If no address could 
+              be resolved from the system, "none" will be shown.
+          </para>
+        <note>
+          <title>Note</title>
+          <para>loopback interfaces are not available on Windows platforms.</para>
+          </note>
+        </listitem>
+        <listitem>
               <para>
-			The link-layer header type.
-	      </para>
- 	    </listitem>
+            The link-layer header type.
+          </para>
+         </listitem>
             <listitem>
-	      <para>
-			The information whether promicuous mode is enabled or disabled.
-	      </para>
- 	    </listitem>
-	    <listitem>
-	      <para>
-		The maximum amount of data that will be captured for each packet. 
-		The default value is set to the 65535 bytes.
+          <para>
+            The information whether promicuous mode is enabled or disabled.
+          </para>
+         </listitem>
+        <listitem>
+          <para>
+        The maximum amount of data that will be captured for each packet. 
+        The default value is set to the 65535 bytes.
               </para>
- 	    </listitem>
-	    <listitem>
-	      <para>
-		The size of the kernel buffer that is reserved to keep the captured packets.
+         </listitem>
+        <listitem>
+          <para>
+        The size of the kernel buffer that is reserved to keep the captured packets.
               </para>
- 	    </listitem>
+         </listitem>
             <listitem>
-	      <para>
+          <para>
                   The information whether packets will be captured in monitor mode (Unix/Linux only).
               </para>
- 	    </listitem>
+         </listitem>
             <listitem>
-	      <para>
+          <para>
                   The chosen capture filter.
               </para>
- 	    </listitem>
-	</itemizedlist>
-	By marking the
-	checkboxes in the first column the interfaces are selected to be
-	captured from. By double-clicking on an interface the "Edit Interface Settings" 
-	dialog box as shown in 
-	<xref linkend="ChCapEditInterfacesSettingsDialog"/> will be opened.
-	</para>
-	  <variablelist>
-	   <varlistentry>
-	    <term>
-	      <command>Capture on all interfaces</command>
-	    </term>
-	    <listitem>
-	      <para>
-		 As Wireshark can capture on multiple interfaces, it is possible to choose to capture on all available interfaces.
-	      </para>
+         </listitem>
+    </itemizedlist>
+    By marking the
+    checkboxes in the first column the interfaces are selected to be
+    captured from. By double-clicking on an interface the "Edit Interface Settings" 
+    dialog box as shown in 
+    <xref linkend="ChCapEditInterfacesSettingsDialog"/> will be opened.
+    </para>
+      <variablelist>
+       <varlistentry>
+        <term>
+          <command>Capture on all interfaces</command>
+        </term>
+        <listitem>
+          <para>
+         As Wireshark can capture on multiple interfaces, it is possible to choose to capture on all available interfaces.
+          </para>
             </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
-	      <command>Capture all packets in promiscuous mode</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This checkbox allows you to specify that Wireshark 
-		should put all interfaces in promiscuous mode when capturing. 
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Capture Filter</command></term>
-	    <listitem>
-	      <para>
-		This field allows you to specify a capture filter for all interfaces
-		that are currently selected. Once a filter has been entered in this field,
-		the newly selected interfaces will inherit the filter.
-		Capture filters are discussed in more details in 
-		<xref linkend="ChCapCaptureFilterSection"/>. It defaults to empty, or 
-		  no filter.
-	      </para>
-	      <para>
-		You can also click on the button labeled "Capture Filter", and Wireshark 
-		will bring up the Capture Filters dialog box and allow you to create 
-		and/or select a filter.  Please see 
-		<xref linkend="ChWorkDefineFilterSection"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Compile selected BPFs</command></term>
-	    <listitem>
-	      <para>
-		This button allows you to compile the capture filter into BPF code and
-		pop up a window showing you the resulting pseudo code. This can help in 
-		understanding the working of the capture filter you created.
-		The "Compile selected BPFs" button leads you to 
-		<xref linkend="ChCapCompileSelectedBpfsDialog"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <command>Capture all packets in promiscuous mode</command>
+        </term>
+        <listitem>
+          <para>
+        This checkbox allows you to specify that Wireshark 
+        should put all interfaces in promiscuous mode when capturing. 
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Capture Filter</command></term>
+        <listitem>
+          <para>
+        This field allows you to specify a capture filter for all interfaces
+        that are currently selected. Once a filter has been entered in this field,
+        the newly selected interfaces will inherit the filter.
+        Capture filters are discussed in more details in 
+        <xref linkend="ChCapCaptureFilterSection"/>. It defaults to empty, or 
+          no filter.
+          </para>
+          <para>
+        You can also click on the button labeled "Capture Filter", and Wireshark 
+        will bring up the Capture Filters dialog box and allow you to create 
+        and/or select a filter.  Please see 
+        <xref linkend="ChWorkDefineFilterSection"/>
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Compile selected BPFs</command></term>
+        <listitem>
+          <para>
+        This button allows you to compile the capture filter into BPF code and
+        pop up a window showing you the resulting pseudo code. This can help in 
+        understanding the working of the capture filter you created.
+        The "Compile selected BPFs" button leads you to 
+        <xref linkend="ChCapCompileSelectedBpfsDialog"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
               <command>Manage Interfaces</command>
             </term>
             <listitem>
             <para>
-		The "Manage Interfaces" button leads you to 
-		<xref linkend="ChCapManageInterfacesDialog"/> where pipes can be defined,
-		local interfaces scanned or hidden, or remote interfaces added (Windows only).
+        The "Manage Interfaces" button leads you to 
+        <xref linkend="ChCapManageInterfacesDialog"/> where pipes can be defined,
+        local interfaces scanned or hidden, or remote interfaces added (Windows only).
             </para>
             </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
-	<section><title>Capture File(s) frame</title>
-	<para>
-	An explanation about capture file usage can be found in <xref 
-	linkend="ChCapCaptureFiles"/>.
-	</para>
-	<variablelist>	  
-	  <varlistentry><term><command>File</command></term>
-	    <listitem>
-	      <para>
-			This field allows you to specify the file name that will be 
-			used for the capture file. This field is left blank by default.
-			If the field is left blank, the capture data will be stored in a 
-			temporary file, see <xref linkend="ChCapCaptureFiles"/> for 
-			details.
-	      </para>
-	      <para>
-			You can also click on the button to the right of this field to 
-			browse through the filesystem.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Use multiple files</command></term>
-	    <listitem>
-	      <para>
-			Instead of using a single file, Wireshark will automatically switch 
-			to a new one, if a specific trigger condition is reached.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
-	      <command>Use pcap-ng format</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This checkbox allows you to specify that Wireshark saves the captured
-		packets in pcap-ng format. This next generation capture file format is
-		currently in development. If more than one interface is chosen for 
-		capturing, this checkbox is set by default. See 
-		<ulink url="&WiresharkWikiPcapNgPage;"/> for more details on pcap-ng.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Next file every n megabyte(s)</command></term>
-	    <listitem>
-	      <para>
-			Multiple files only: Switch to the next file after the given 
-			number of byte(s)/kilobyte(s)/megabyte(s)/gigabyte(s) have been
-			captured. 
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Next file every n minute(s)</command></term>
-	    <listitem>
-	      <para>
-			Multiple files only: Switch to the next file after the given 
-			number of second(s)/minutes(s)/hours(s)/days(s) have elapsed.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Ring buffer with n files</command></term>
-	    <listitem>
-	      <para>
-			Multiple files only: Form a ring buffer of the capture files, with 
-			the given number of files.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Stop capture after n file(s)</command></term>
-	    <listitem>
-	      <para>
-			Multiple files only: Stop capturing after switching to the next 
-			file the given number of times.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
-	<section><title>Stop Capture... frame</title>
-	<variablelist>	  
-	  <varlistentry><term><command>... after n packet(s)</command></term>
-	    <listitem>
-	      <para>
-			Stop capturing after the given number of packets have been
-			captured.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>... after n megabytes(s)</command></term>
-	    <listitem>
-	      <para>
-			Stop capturing after the given number of 
-			byte(s)/kilobyte(s)/megabyte(s)/gigabyte(s) have been captured.
-			This option is greyed out, if "Use multiple files" is selected.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>... after n minute(s)</command></term>
-	    <listitem>
-	      <para>
-			Stop capturing after the given number of 
-			second(s)/minutes(s)/hours(s)/days(s) have elapsed.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
-	<section><title>Display Options frame</title>
-	<variablelist>	  
-	  <varlistentry>
-	    <term>
-	      <command>Update list of packets in real time</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This option allows you to specify that Wireshark 
-		should update the packet list pane in real time. If you 
-		do not specify this, Wireshark does not display any 
-		packets until you stop the capture. When you check this,
-		Wireshark captures in a separate process 
-		and feeds the captures to the display process.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
-	      <command>Automatic scrolling in live capture</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This option allows you to specify that Wireshark 
-		should scroll the packet list pane as new packets come 
-		in, so you are always looking at the last packet.  If you 
-		do not specify this, Wireshark simply adds new packets onto 
-		the end of the list, but does not scroll the packet list 
-		pane. This option is greyed out if 
-		"Update list of packets in real time" is disabled.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
-	      <command>Hide capture info dialog</command>
-	    </term>
-	    <listitem>
-	      <para>
-		If this option is checked, the capture info dialog described in 
+      </varlistentry>
+    </variablelist>
+    </section>
+    <section><title>Capture File(s) frame</title>
+    <para>
+    An explanation about capture file usage can be found in <xref 
+    linkend="ChCapCaptureFiles"/>.
+    </para>
+    <variablelist>      
+      <varlistentry><term><command>File</command></term>
+        <listitem>
+          <para>
+            This field allows you to specify the file name that will be 
+            used for the capture file. This field is left blank by default.
+            If the field is left blank, the capture data will be stored in a 
+            temporary file, see <xref linkend="ChCapCaptureFiles"/> for 
+            details.
+          </para>
+          <para>
+            You can also click on the button to the right of this field to 
+            browse through the filesystem.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Use multiple files</command></term>
+        <listitem>
+          <para>
+            Instead of using a single file, Wireshark will automatically switch 
+            to a new one, if a specific trigger condition is reached.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <command>Use pcap-ng format</command>
+        </term>
+        <listitem>
+          <para>
+        This checkbox allows you to specify that Wireshark saves the captured
+        packets in pcap-ng format. This next generation capture file format is
+        currently in development. If more than one interface is chosen for 
+        capturing, this checkbox is set by default. See 
+        <ulink url="&WiresharkWikiPcapNgPage;"/> for more details on pcap-ng.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Next file every n megabyte(s)</command></term>
+        <listitem>
+          <para>
+            Multiple files only: Switch to the next file after the given 
+            number of byte(s)/kilobyte(s)/megabyte(s)/gigabyte(s) have been
+            captured. 
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Next file every n minute(s)</command></term>
+        <listitem>
+          <para>
+            Multiple files only: Switch to the next file after the given 
+            number of second(s)/minutes(s)/hours(s)/days(s) have elapsed.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Ring buffer with n files</command></term>
+        <listitem>
+          <para>
+            Multiple files only: Form a ring buffer of the capture files, with 
+            the given number of files.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Stop capture after n file(s)</command></term>
+        <listitem>
+          <para>
+            Multiple files only: Stop capturing after switching to the next 
+            file the given number of times.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+    </section>
+    <section><title>Stop Capture... frame</title>
+    <variablelist>      
+      <varlistentry><term><command>... after n packet(s)</command></term>
+        <listitem>
+          <para>
+            Stop capturing after the given number of packets have been
+            captured.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>... after n megabytes(s)</command></term>
+        <listitem>
+          <para>
+            Stop capturing after the given number of 
+            byte(s)/kilobyte(s)/megabyte(s)/gigabyte(s) have been captured.
+            This option is greyed out, if "Use multiple files" is selected.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>... after n minute(s)</command></term>
+        <listitem>
+          <para>
+            Stop capturing after the given number of 
+            second(s)/minutes(s)/hours(s)/days(s) have elapsed.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+    </section>
+    <section><title>Display Options frame</title>
+    <variablelist>      
+      <varlistentry>
+        <term>
+          <command>Update list of packets in real time</command>
+        </term>
+        <listitem>
+          <para>
+        This option allows you to specify that Wireshark 
+        should update the packet list pane in real time. If you 
+        do not specify this, Wireshark does not display any 
+        packets until you stop the capture. When you check this,
+        Wireshark captures in a separate process 
+        and feeds the captures to the display process.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <command>Automatic scrolling in live capture</command>
+        </term>
+        <listitem>
+          <para>
+        This option allows you to specify that Wireshark 
+        should scroll the packet list pane as new packets come 
+        in, so you are always looking at the last packet.  If you 
+        do not specify this, Wireshark simply adds new packets onto 
+        the end of the list, but does not scroll the packet list 
+        pane. This option is greyed out if 
+        "Update list of packets in real time" is disabled.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <command>Hide capture info dialog</command>
+        </term>
+        <listitem>
+          <para>
+        If this option is checked, the capture info dialog described in 
                 <xref linkend="ChCapRunningSection"/> will be hidden.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
-	<section><title>Name Resolution frame</title>
-	<variablelist>	  
-	  <varlistentry>
-	    <term><command>Enable MAC name resolution</command></term>
-	    <listitem>
-	      <para>
-		This option allows you to control whether or not 
-		Wireshark translates MAC addresses into names, see 
-		<xref linkend="ChAdvNameResolutionSection"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term><command>Enable network name resolution</command></term>
-	    <listitem>
-	      <para>
-		This option allows you to control whether or not 
-		Wireshark translates network addresses into names, see
-		<xref linkend="ChAdvNameResolutionSection"/>.
-	      </para>  
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term><command>Enable transport name resolution</command></term>
-	    <listitem>
-	      <para>
-		This option allows you to control whether or not 
-		Wireshark translates transport addresses into protocols, see
-		<xref linkend="ChAdvNameResolutionSection"/>.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
-	<section><title>Buttons</title>
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+    </section>
+    <section><title>Name Resolution frame</title>
+    <variablelist>      
+      <varlistentry>
+        <term><command>Enable MAC name resolution</command></term>
+        <listitem>
+          <para>
+        This option allows you to control whether or not 
+        Wireshark translates MAC addresses into names, see 
+        <xref linkend="ChAdvNameResolutionSection"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><command>Enable network name resolution</command></term>
+        <listitem>
+          <para>
+        This option allows you to control whether or not 
+        Wireshark translates network addresses into names, see
+        <xref linkend="ChAdvNameResolutionSection"/>.
+          </para>  
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><command>Enable transport name resolution</command></term>
+        <listitem>
+          <para>
+        This option allows you to control whether or not 
+        Wireshark translates transport addresses into protocols, see
+        <xref linkend="ChAdvNameResolutionSection"/>.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+    </section>
+    <section><title>Buttons</title>
       <para>
-	Once you have set the values you desire and have selected the 
-	options you need, simply click on <command>Start</command> to commence the 
-	capture, or <command>Cancel</command> to cancel the capture.
+    Once you have set the values you desire and have selected the 
+    options you need, simply click on <command>Start</command> to commence the 
+    capture, or <command>Cancel</command> to cancel the capture.
       </para>
       <para>
-	If you start a capture, Wireshark allows you to stop capturing when 
-	you have enough packets captured, for details see
-		<xref linkend="ChCapRunningSection"/>.
+    If you start a capture, Wireshark allows you to stop capturing when 
+    you have enough packets captured, for details see
+        <xref linkend="ChCapRunningSection"/>.
       </para>
     </section>
     </section>
@@ -617,168 +616,168 @@ wireshark -i eth0 -k
       </para>
       <variablelist>
           <varlistentry><term><command>IP address</command></term>
-	    <listitem>
-	      <para>
-		  The IP address(es) of the selected interface. If no address could 
-		  be resolved from the system, "none" will be shown.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Link-layer header type</command></term>
-	    <listitem>
-	      <para>
-		  Unless you are in the rare situation that you need this, just keep 
-		  the default. For a detailed description, see 
-		  <xref linkend="ChCapLinkLayerHeader"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Wireless settings (Windows only)</command></term>
-	    <listitem>
-	      <para>
-		Here you can set the settings for wireless capture using the AirPCap adapter.
-		For a detailed description, see the AirPCap Users Guide.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Remote settings (Windows only)</command></term>
-	    <listitem>
-	      <para>
-		Here you can set the settings for remote capture.
-		For a detailed description, see  <xref linkend="ChCapInterfaceRemoteSection"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
+        <listitem>
+          <para>
+          The IP address(es) of the selected interface. If no address could 
+          be resolved from the system, "none" will be shown.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Link-layer header type</command></term>
+        <listitem>
+          <para>
+          Unless you are in the rare situation that you need this, just keep 
+          the default. For a detailed description, see 
+          <xref linkend="ChCapLinkLayerHeader"/>
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Wireless settings (Windows only)</command></term>
+        <listitem>
+          <para>
+        Here you can set the settings for wireless capture using the AirPCap adapter.
+        For a detailed description, see the AirPCap Users Guide.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Remote settings (Windows only)</command></term>
+        <listitem>
+          <para>
+        Here you can set the settings for remote capture.
+        For a detailed description, see  <xref linkend="ChCapInterfaceRemoteSection"/>
+          </para>
+        </listitem>
+      </varlistentry>
           <varlistentry>
-	    <term>
-	      <command>Capture packets in promiscuous mode</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This checkbox allows you to specify that Wireshark 
-		should put the interface in promiscuous mode when capturing. 
-		If you do not specify this, Wireshark will only capture the 
-		packets going to or from your computer (not 
-		all packets on your LAN segment).
-	      </para>
-	      <note>
-		<title>Note</title>
-		<para>
-		  If some other process has put the interface in 
-		  promiscuous mode you may be capturing in promiscuous 
-		  mode even if you turn off this option.
-		</para>
-	      </note>
-	      <note>
-		<title>Note</title>
-		<para>
-		Even in promiscuous mode you still won't necessarily see all packets 
-		on your LAN segment, see <ulink url="&WiresharkFAQPromiscPage;"/> for 
-		some more explanations.
-		</para>
-	      </note>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Limit each packet to n bytes</command></term>
-	    <listitem>
-	      <para>
-		This field allows you to specify the maximum amount of 
-		data that will be captured for each packet, and is 
-		sometimes referred to as the <command>snaplen</command>. If disabled, 
-		the value is set to the maximum 65535, which will be sufficient for most
-		protocols. Some rules of thumb:
-	      </para>
-		<itemizedlist>
-	    <listitem>
-	      <para>
-			If you are unsure, just keep the default value.
-	      </para>
-	    </listitem>
-	    <listitem>
-	      <para>
-			If you don't need all of the data in a packet - for example, if you
-			only need the link-layer, IP, and TCP headers - you might want to
-			choose a small snapshot length, as less CPU time is required for
-			copying packets, less buffer space is required for packets, and thus
-			perhaps fewer packets will be dropped if traffic is very heavy.
-	      </para>
-	    </listitem>
-	    <listitem>
-	      <para>
-			If you don't capture all of the data in a packet, you might find that
-			the packet data you want is in the part that's dropped, or that
-			reassembly isn't possible as the data required for reassembly is
-			missing.
-	      </para>
-	    </listitem>
-		</itemizedlist>
-	    </listitem>
-	  </varlistentry>
+        <term>
+          <command>Capture packets in promiscuous mode</command>
+        </term>
+        <listitem>
+          <para>
+        This checkbox allows you to specify that Wireshark 
+        should put the interface in promiscuous mode when capturing. 
+        If you do not specify this, Wireshark will only capture the 
+        packets going to or from your computer (not 
+        all packets on your LAN segment).
+          </para>
+          <note>
+        <title>Note</title>
+        <para>
+          If some other process has put the interface in 
+          promiscuous mode you may be capturing in promiscuous 
+          mode even if you turn off this option.
+        </para>
+          </note>
+          <note>
+        <title>Note</title>
+        <para>
+        Even in promiscuous mode you still won't necessarily see all packets 
+        on your LAN segment, see <ulink url="&WiresharkFAQPromiscPage;"/> for 
+        some more explanations.
+        </para>
+          </note>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Limit each packet to n bytes</command></term>
+        <listitem>
+          <para>
+        This field allows you to specify the maximum amount of 
+        data that will be captured for each packet, and is 
+        sometimes referred to as the <command>snaplen</command>. If disabled, 
+        the value is set to the maximum 65535, which will be sufficient for most
+        protocols. Some rules of thumb:
+          </para>
+        <itemizedlist>
+        <listitem>
+          <para>
+            If you are unsure, just keep the default value.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            If you don't need all of the data in a packet - for example, if you
+            only need the link-layer, IP, and TCP headers - you might want to
+            choose a small snapshot length, as less CPU time is required for
+            copying packets, less buffer space is required for packets, and thus
+            perhaps fewer packets will be dropped if traffic is very heavy.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            If you don't capture all of the data in a packet, you might find that
+            the packet data you want is in the part that's dropped, or that
+            reassembly isn't possible as the data required for reassembly is
+            missing.
+          </para>
+        </listitem>
+        </itemizedlist>
+        </listitem>
+      </varlistentry>
           <varlistentry><term><command>Buffer size: n megabyte(s)</command></term>
-	    <listitem>
-	      <para>
-		  Enter the buffer size to be used while capturing. This is the size 
-		  of the kernel buffer which will keep the captured packets, until 
-		  they are written to disk. If you encounter packet drops, try 
-		  increasing this value.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term>
-	      <command>Capture packets in monitor mode (Unix/Linux only)</command>
-	    </term>
-	    <listitem>
-	      <para>
-		This checkbox allows you to setup the Wireless interface to capture
-		all traffic it can receive, not just the traffic on the BSS to which
-		it is associated, which can happen even when you set promiscuous mode.
-		Also it might be necessary to turn this option on in order to see
-		IEEE 802.11 headers and/or radio information from the captured frames.
-	      </para>
-	      <note>
-		<title>Note</title>
-		<para>
-		  In monitor mode the adapter might disassociate itself from the network
-		  it was associated to.
-		</para>
-	      </note>
-	    </listitem>
-	  </varlistentry>
+        <listitem>
+          <para>
+          Enter the buffer size to be used while capturing. This is the size 
+          of the kernel buffer which will keep the captured packets, until 
+          they are written to disk. If you encounter packet drops, try 
+          increasing this value.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term>
+          <command>Capture packets in monitor mode (Unix/Linux only)</command>
+        </term>
+        <listitem>
+          <para>
+        This checkbox allows you to setup the Wireless interface to capture
+        all traffic it can receive, not just the traffic on the BSS to which
+        it is associated, which can happen even when you set promiscuous mode.
+        Also it might be necessary to turn this option on in order to see
+        IEEE 802.11 headers and/or radio information from the captured frames.
+          </para>
+          <note>
+        <title>Note</title>
+        <para>
+          In monitor mode the adapter might disassociate itself from the network
+          it was associated to.
+        </para>
+          </note>
+        </listitem>
+      </varlistentry>
           <varlistentry><term><command>Capture Filter</command></term>
-	    <listitem>
-	      <para>
-		This field allows you to specify a capture filter. 
-		Capture filters are discussed in more details in 
-		<xref linkend="ChCapCaptureFilterSection"/>. It defaults to empty, or 
-		  no filter.
-	      </para>
-	      <para>
-		You can also click on the button labeled "Capture Filter", and Wireshark 
-		will bring up the Capture Filters dialog box and allow you to create 
-		and/or select a filter.  Please see 
-		<xref linkend="ChWorkDefineFilterSection"/>
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Compile BPF</command></term>
-	    <listitem>
-	      <para>
-		This button allows you to compile the capture filter into BPF code and
-		pop up a window showing you the resulting pseudo code. This can help in 
-		understanding the working of the capture filter you created.
-	      </para>
-	    </listitem>
-	  </varlistentry>
+        <listitem>
+          <para>
+        This field allows you to specify a capture filter. 
+        Capture filters are discussed in more details in 
+        <xref linkend="ChCapCaptureFilterSection"/>. It defaults to empty, or 
+          no filter.
+          </para>
+          <para>
+        You can also click on the button labeled "Capture Filter", and Wireshark 
+        will bring up the Capture Filters dialog box and allow you to create 
+        and/or select a filter.  Please see 
+        <xref linkend="ChWorkDefineFilterSection"/>
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Compile BPF</command></term>
+        <listitem>
+          <para>
+        This button allows you to compile the capture filter into BPF code and
+        pop up a window showing you the resulting pseudo code. This can help in 
+        understanding the working of the capture filter you created.
+          </para>
+        </listitem>
+      </varlistentry>
       </variablelist>
     </section>
 
      <section id="ChCapCompileSelectedBpfsSection">
       <title>The "Compile Results" dialog box</title>
       <para>
-	This figure shows the compile results of the selected interfaces. 
+    This figure shows the compile results of the selected interfaces. 
       </para>
-      	<figure id="ChCapCompileSelectedBpfsDialog">
+          <figure id="ChCapCompileSelectedBpfsDialog">
       <title>The "Compile Results" dialog box</title>
       <graphic entityref="WiresharkCaptureCompileSelectedBPFsDialog" format="PNG"/>
       </figure>
@@ -788,435 +787,435 @@ wireshark -i eth0 -k
  in the right window, when it is selected.
  </para>
  </section>
-	
+    
    <section id="ChCapManageInterfacesSection">
       <title>The "Add New Interfaces" dialog box</title>
       <para>
-	As a central point to manage interfaces this dialog box consists of three tabs
-	to add or remove interfaces.
+    As a central point to manage interfaces this dialog box consists of three tabs
+    to add or remove interfaces.
       </para>
      <figure id="ChCapManageInterfacesDialog">
       <title>The "Add New Interfaces" dialog box</title>
       <graphic entityref="WiresharkCaptureManageInterfacesDialog" format="PNG"/>
       </figure> 
-	<section>
-	<title>Add or remove pipes</title>
-	  <figure id="ChCapManageInterfacesPipesDialog">
+    <section>
+    <title>Add or remove pipes</title>
+      <figure id="ChCapManageInterfacesPipesDialog">
       <title>The "Add New Interfaces - Pipes" dialog box</title>
       <graphic entityref="WiresharkCaptureManageInterfacesPipesDialog" format="PNG"/>
       </figure>
-	<para>To successfully add a pipe, this pipe must have already been created.
-	Click the "New" button and type the name of the pipe including its path.
-	Alternatively, the "Browse" button can be used to locate the pipe.
-	With the "Save" button the pipe is added to the list of available interfaces. 
-	Afterwards, other pipes can be added.
-	</para>
-	<para>
-	To remove a pipe from the list of interfaces it first has to be selected. Then
-	click the "Delete" button. 
-	</para>
-	</section>
-	<section>
-	<title>Add or hide local interfaces</title>
-	  <figure id="ChCapManageInterfacesLocalDialog">
+    <para>To successfully add a pipe, this pipe must have already been created.
+    Click the "New" button and type the name of the pipe including its path.
+    Alternatively, the "Browse" button can be used to locate the pipe.
+    With the "Save" button the pipe is added to the list of available interfaces. 
+    Afterwards, other pipes can be added.
+    </para>
+    <para>
+    To remove a pipe from the list of interfaces it first has to be selected. Then
+    click the "Delete" button. 
+    </para>
+    </section>
+    <section>
+    <title>Add or hide local interfaces</title>
+      <figure id="ChCapManageInterfacesLocalDialog">
       <title>The "Add New Interfaces - Local Interfaces" dialog box</title>
       <graphic entityref="WiresharkCaptureManageInterfacesLocalDialog" format="PNG"/>
       </figure>
-	<para>
-	The tab "Local Interfaces" contains a list of available local interfaces, including
-	the hidden ones, which are not shown in the other lists.
-	</para>
-	<para>
-	If a new local interface is added, for example, a wireless interface has been 
-	activated, it is not automatically added to the list to prevent the constant scanning
-	for a change in the list of available interfaces. To renew the list a rescan can be done.
-	</para>
-	<para>
-	One way to hide an interface is to change the preferences. If the "Hide" checkbox 
-	is activated and the "Apply" button clicked, the interface will not be seen in the 
-	lists of the "Capture Options" or "Capture Interfaces" dialog box any more. The changes
-	are also saved in the "Preferences" file.
-	</para>
-	</section>
-	<section>
-	<title>Add or hide remote interfaces</title>
-	  <figure id="ChCapManageInterfacesRemoteDialog">
+    <para>
+    The tab "Local Interfaces" contains a list of available local interfaces, including
+    the hidden ones, which are not shown in the other lists.
+    </para>
+    <para>
+    If a new local interface is added, for example, a wireless interface has been 
+    activated, it is not automatically added to the list to prevent the constant scanning
+    for a change in the list of available interfaces. To renew the list a rescan can be done.
+    </para>
+    <para>
+    One way to hide an interface is to change the preferences. If the "Hide" checkbox 
+    is activated and the "Apply" button clicked, the interface will not be seen in the 
+    lists of the "Capture Options" or "Capture Interfaces" dialog box any more. The changes
+    are also saved in the "Preferences" file.
+    </para>
+    </section>
+    <section>
+    <title>Add or hide remote interfaces</title>
+      <figure id="ChCapManageInterfacesRemoteDialog">
       <title>The "Add New Interfaces - Remote Interfaces" dialog box</title>
       <graphic entityref="WiresharkCaptureManageInterfacesRemoteDialog" format="PNG"/>
       </figure>
-	<para>
-	In this tab interfaces on remote hosts can be added. One or more of these
-	interfaces can be hidden. In contrast to the local interfaces they are not
-	saved in the "Preferences" file. 
-	</para>
-	<para>
-	To remove a host including all its interfaces from the list, it has to be
-	selected. Then click the "Delete" button.
-	</para>
-	<para>
-	For a detailed description, see  <xref linkend="ChCapInterfaceRemoteSection"/>
-	</para>
-	</section>
+    <para>
+    In this tab interfaces on remote hosts can be added. One or more of these
+    interfaces can be hidden. In contrast to the local interfaces they are not
+    saved in the "Preferences" file. 
+    </para>
+    <para>
+    To remove a host including all its interfaces from the list, it has to be
+    selected. Then click the "Delete" button.
+    </para>
+    <para>
+    For a detailed description, see  <xref linkend="ChCapInterfaceRemoteSection"/>
+    </para>
+    </section>
     </section>
 
     <section id="ChCapInterfaceRemoteSection">
       <title>The "Remote Capture Interfaces" dialog box</title>
       <para>
-	  Besides doing capture on local interfaces Wireshark is capable of
-	  reaching out across the network to a so called capture daemon or service
-	  processes to receive captured data from.
+      Besides doing capture on local interfaces Wireshark is capable of
+      reaching out across the network to a so called capture daemon or service
+      processes to receive captured data from.
       </para>
       <note><title>Microsoft Windows only</title>
       <para>
-	  This dialog and capability is only available on Microsoft Windows. On
-	  Linux/Unix you can achieve the same effect (securely) through an SSH
-	  tunnel.
+      This dialog and capability is only available on Microsoft Windows. On
+      Linux/Unix you can achieve the same effect (securely) through an SSH
+      tunnel.
       </para>
       </note>
       <para>
-	  The Remote Packet Capture Protocol service must first be running on the
-	  target platform before Wireshark can connect to it. The easiest way is
-	  to install WinPcap from <ulink url="&WinPcapDownloadWebsite;"/> on the
-	  target. Once installation is completed go to the Services control panel,
-	  find the Remote Packet Capture Protocol service and start it.
+      The Remote Packet Capture Protocol service must first be running on the
+      target platform before Wireshark can connect to it. The easiest way is
+      to install WinPcap from <ulink url="&WinPcapDownloadWebsite;"/> on the
+      target. Once installation is completed go to the Services control panel,
+      find the Remote Packet Capture Protocol service and start it.
       </para>
       <note><title>Note</title>
       <para>
-	  Make sure you have outside access to port 2002 on the target platform.
-	  This is the port where the Remote Packet Capture Protocol service can
-	  be reached, by default.
+      Make sure you have outside access to port 2002 on the target platform.
+      This is the port where the Remote Packet Capture Protocol service can
+      be reached, by default.
       </para>
       </note>
       <para>
-	  To access the Remote Capture Interfaces dialog use the 
-	  "Add New Interfaces - Remote" dialog, see
-	  <xref linkend="ChCapManageInterfacesRemoteDialog"/>, and select "Add".
+      To access the Remote Capture Interfaces dialog use the 
+      "Add New Interfaces - Remote" dialog, see
+      <xref linkend="ChCapManageInterfacesRemoteDialog"/>, and select "Add".
       </para>
       <section><title>Remote Capture Interfaces</title>
       <figure id="ChCapInterfaceRemoteDialog">
-	<title>The "Remote Capture Interfaces" dialog box</title>
-	<graphic entityref="WiresharkCaptureOptionsRemoteInterfacesDialog" format="PNG"/>
+    <title>The "Remote Capture Interfaces" dialog box</title>
+    <graphic entityref="WiresharkCaptureOptionsRemoteInterfacesDialog" format="PNG"/>
       </figure>
       <para>
-	  You have to set the following parameter in this dialog:
+      You have to set the following parameter in this dialog:
       </para>
 
-	<variablelist>
-	  <varlistentry><term><command>Host</command></term>
-	    <listitem>
-	      <para>
-		  Enter the IP address or host name of the target platform where the
-		  Remote Packet Capture Protocol service is listening. The drop down list
-		  contains the hosts that have previously been successfully contacted.
-		  The list can be emptied by choosing "Clear list" from the drop down list. 
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Port</command></term>
-	    <listitem>
-	      <para>
-		  Set the port number where the Remote Packet Capture Protocol service
-		  is listening on. Leave open to use the default port (2002).
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Null authentication</command></term>
-	    <listitem>
-	      <para>
-		  Select this if you don't need authentication to take place for a
-		  remote capture to be started. This depends on the target platform.
-		  Configuring the target platform like this makes it insecure.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Password authentication</command></term>
-	    <listitem>
-	      <para>
-		  This is the normal way of connecting to a target platform. Set the
-		  credentials needed to connect to the Remote Packet Capture Protocol
-		  service.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+    <variablelist>
+      <varlistentry><term><command>Host</command></term>
+        <listitem>
+          <para>
+          Enter the IP address or host name of the target platform where the
+          Remote Packet Capture Protocol service is listening. The drop down list
+          contains the hosts that have previously been successfully contacted.
+          The list can be emptied by choosing "Clear list" from the drop down list. 
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Port</command></term>
+        <listitem>
+          <para>
+          Set the port number where the Remote Packet Capture Protocol service
+          is listening on. Leave open to use the default port (2002).
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Null authentication</command></term>
+        <listitem>
+          <para>
+          Select this if you don't need authentication to take place for a
+          remote capture to be started. This depends on the target platform.
+          Configuring the target platform like this makes it insecure.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Password authentication</command></term>
+        <listitem>
+          <para>
+          This is the normal way of connecting to a target platform. Set the
+          credentials needed to connect to the Remote Packet Capture Protocol
+          service.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
       </section>
      <!-- <section><title>Remote Capture</title>
       <para>
-	  When the connection to the Remote Packet Capture Protocol service is
-	  successfully established the "Capture Options" dialog looks like this,
-	  see <xref linkend="ChCapInterfaceRemoteCapDialog"/>.
+      When the connection to the Remote Packet Capture Protocol service is
+      successfully established the "Capture Options" dialog looks like this,
+      see <xref linkend="ChCapInterfaceRemoteCapDialog"/>.
       </para>
       <figure id="ChCapInterfaceRemoteCapDialog">
-	<title>The "Remote Capture" dialog box</title>
-	<graphic entityref="WiresharkCaptureOptionsRemoteCaptureDialog" format="PNG"/>
+    <title>The "Remote Capture" dialog box</title>
+    <graphic entityref="WiresharkCaptureOptionsRemoteCaptureDialog" format="PNG"/>
       </figure>
       <para>
-	  The Interface dropdown list now shows the IP address or host name of the
-	  Remote Packet Capture Protocol service and the other field shows the
-	  interfaces on the remote target. After selecting the desired interface
-	  just click <command>Start</command> to start the remote capture.
+      The Interface dropdown list now shows the IP address or host name of the
+      Remote Packet Capture Protocol service and the other field shows the
+      interfaces on the remote target. After selecting the desired interface
+      just click <command>Start</command> to start the remote capture.
       </para>
       </section> -->
       <section><title>Remote Capture Settings</title>
       <para>
-	  The remote capture can be further fine tuned to match your situation.
-	  The <command>Remote Settings</command> button in 
-	  <xref linkend="ChCapEditInterfacesSettingsDialog"/> gives you this option.
-	  It pops up the dialog shown in
-	  <xref linkend="ChCapInterfaceRemoteSettingsDialog"/>.
+      The remote capture can be further fine tuned to match your situation.
+      The <command>Remote Settings</command> button in 
+      <xref linkend="ChCapEditInterfacesSettingsDialog"/> gives you this option.
+      It pops up the dialog shown in
+      <xref linkend="ChCapInterfaceRemoteSettingsDialog"/>.
       </para>
       <figure id="ChCapInterfaceRemoteSettingsDialog">
-	<title>The "Remote Capture Settings" dialog box</title>
-	<graphic entityref="WiresharkCaptureOptionsRemoteSettingsDialog" format="PNG"/>
+    <title>The "Remote Capture Settings" dialog box</title>
+    <graphic entityref="WiresharkCaptureOptionsRemoteSettingsDialog" format="PNG"/>
       </figure>
       <para>
-	  You can set the following parameters in this dialog:
+      You can set the following parameters in this dialog:
       </para>
-	<variablelist>
-	  <varlistentry><term><command>Do not capture own RPCAP traffic</command></term>
-	    <listitem>
-	      <para>
-		  This option sets a capture filter so that the traffic flowing back
-		  from the Remote Packet Capture Protocol service to Wireshark isn't
-		  captured as well and also send back. The recursion in this saturates
-		  the link with duplicate traffic.
-	      </para>
-	      <para>
-		  You only should switch this off when capturing on an interface other
-		  then the interface connecting back to Wireshark.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Use UDP for data transfer</command></term>
-	    <listitem>
-	      <para>
-		  Remote capture control and data flows over a TCP connection. This
-		  option allows you to choose an UDP stream for data transfer.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Sampling option None</command></term>
-	    <listitem>
-	      <para>
-		  This option instructs the Remote Packet Capture Protocol service to
-		  send back all captured packets which have passed the capture filter.
-		  This is usually not a problem on a remote capture session with
-		  sufficient bandwidth.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Sampling option 1 of x packets</command></term>
-	    <listitem>
-	      <para>
-		  This option limits the Remote Packet Capture Protocol service to send
-		  only a sub sampling of the captured data, in terms of number of
-		  packets. This allows capture over a narrow band remote capture
-		  session of a higher bandwidth interface.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Sampling option 1 every x milliseconds</command></term>
-	    <listitem>
-	      <para>
-		  This option limits the Remote Packet Capture Protocol service to send
-		  only a sub sampling of the captured data, in terms of time. This
-		  allows capture over a narrow band capture session of a higher
-		  bandwidth interface.
-	      </para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
+    <variablelist>
+      <varlistentry><term><command>Do not capture own RPCAP traffic</command></term>
+        <listitem>
+          <para>
+          This option sets a capture filter so that the traffic flowing back
+          from the Remote Packet Capture Protocol service to Wireshark isn't
+          captured as well and also send back. The recursion in this saturates
+          the link with duplicate traffic.
+          </para>
+          <para>
+          You only should switch this off when capturing on an interface other
+          then the interface connecting back to Wireshark.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Use UDP for data transfer</command></term>
+        <listitem>
+          <para>
+          Remote capture control and data flows over a TCP connection. This
+          option allows you to choose an UDP stream for data transfer.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Sampling option None</command></term>
+        <listitem>
+          <para>
+          This option instructs the Remote Packet Capture Protocol service to
+          send back all captured packets which have passed the capture filter.
+          This is usually not a problem on a remote capture session with
+          sufficient bandwidth.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Sampling option 1 of x packets</command></term>
+        <listitem>
+          <para>
+          This option limits the Remote Packet Capture Protocol service to send
+          only a sub sampling of the captured data, in terms of number of
+          packets. This allows capture over a narrow band remote capture
+          session of a higher bandwidth interface.
+          </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Sampling option 1 every x milliseconds</command></term>
+        <listitem>
+          <para>
+          This option limits the Remote Packet Capture Protocol service to send
+          only a sub sampling of the captured data, in terms of time. This
+          allows capture over a narrow band capture session of a higher
+          bandwidth interface.
+          </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
       </section>
     </section>
 
     <section id="ChCapInterfaceDetailsSection">
       <title>The "Interface Details" dialog box</title>
       <para>
-	When you select Details from the Capture Interface menu, Wireshark pops 
-	up the "Interface Details" dialog box as shown in 
-	<xref linkend="ChCapInterfaceDetailsDialog"/>. This dialog shows various 
-	characteristics and statistics for the selected interface.
+    When you select Details from the Capture Interface menu, Wireshark pops 
+    up the "Interface Details" dialog box as shown in 
+    <xref linkend="ChCapInterfaceDetailsDialog"/>. This dialog shows various 
+    characteristics and statistics for the selected interface.
       </para>
       <note><title>Microsoft Windows only</title>
       <para>This dialog is only available on Microsoft Windows</para>
       </note>
       <figure id="ChCapInterfaceDetailsDialog">
-	<title>The "Interface Details" dialog box</title>
-	<graphic entityref="WiresharkCaptureInterfaceDetailsDialog" format="JPG"/>
+    <title>The "Interface Details" dialog box</title>
+    <graphic entityref="WiresharkCaptureInterfaceDetailsDialog" format="JPG"/>
       </figure>
     </section>
 
     <section id="ChCapCaptureFiles"><title>Capture files and file modes</title>
-	<para>
-	While capturing, the underlying libpcap capturing engine will grab the 
-	packets from the network card and keep the packet data in a (relatively) 
-	small kernel buffer. This data is read by Wireshark and saved into 
-	the capture file(s) the user specified.
-	</para>
+    <para>
+    While capturing, the underlying libpcap capturing engine will grab the 
+    packets from the network card and keep the packet data in a (relatively) 
+    small kernel buffer. This data is read by Wireshark and saved into 
+    the capture file(s) the user specified.
+    </para>
 
-	<para>
-	Different modes of operation are available when saving this packet data to 
-	the capture file(s).
-	</para>
-	
-	<tip><title>Tip!</title>
-	<para>
-	Working with large files (several 100 MB's) can be quite slow. If you plan 
-	to do a long term capture or capturing from a high traffic network, think 
-	about using one of the "Multiple files" options. This  will spread the 
-	captured packets over several smaller files which can be much more 
-	pleasant to work with.
-	</para>
-	</tip>
-	<note><title>Note!</title>
-	<para>
-	Using Multiple files may cut context related information.
-	Wireshark keeps context information of the loaded packet data, so it can 
-	report context related problems (like a stream error) and keeps information
-	about context related protocols (e.g. where data is exchanged at the 
-	establishing phase and only referred to in later packets). 
-	As it keeps this information only for the loaded file, using one of 
-	the multiple file modes may cut these contexts. If the establishing phase 
-	is saved in one file and the things you would like to see is in another, 
-	you might not see some of the valuable context related information.
-	</para>
-	</note>
-	<tip><title>Tip!</title>
-	<para>
-	Information about the folders used for the capture file(s), can be found 
-	in <xref linkend="AppFiles"/>. 
-	</para>
-	</tip>
-	
+    <para>
+    Different modes of operation are available when saving this packet data to 
+    the capture file(s).
+    </para>
+    
+    <tip><title>Tip!</title>
+    <para>
+    Working with large files (several 100 MB's) can be quite slow. If you plan 
+    to do a long term capture or capturing from a high traffic network, think 
+    about using one of the "Multiple files" options. This  will spread the 
+    captured packets over several smaller files which can be much more 
+    pleasant to work with.
+    </para>
+    </tip>
+    <note><title>Note!</title>
+    <para>
+    Using Multiple files may cut context related information.
+    Wireshark keeps context information of the loaded packet data, so it can 
+    report context related problems (like a stream error) and keeps information
+    about context related protocols (e.g. where data is exchanged at the 
+    establishing phase and only referred to in later packets). 
+    As it keeps this information only for the loaded file, using one of 
+    the multiple file modes may cut these contexts. If the establishing phase 
+    is saved in one file and the things you would like to see is in another, 
+    you might not see some of the valuable context related information.
+    </para>
+    </note>
+    <tip><title>Tip!</title>
+    <para>
+    Information about the folders used for the capture file(s), can be found 
+    in <xref linkend="AppFiles"/>. 
+    </para>
+    </tip>
+    
     <table id="ChCapTabCaptureFiles"><title>Capture file mode selected by capture options</title>
       <tgroup cols="5">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	  <colspec colnum="3" colwidth="80pt"/>
-	  <colspec colnum="4" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>"File" option</entry>
-		<entry>"Use multiple files" option</entry>
-		<entry>"Ring buffer with n files" option</entry>
-		<entry>Mode</entry>
-		<entry>Resulting filename(s) used</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry>-</entry>
-		<entry>-</entry>
-		<entry>-</entry>
-		<entry><command>Single temporary file</command></entry>
-		<entry>wiresharkXXXXXX (where XXXXXX is a unique number)</entry>
-	      </row>
-	      <row>
-		<entry>foo.cap</entry>
-		<entry>-</entry>
-		<entry>-</entry>
-		<entry><command>Single named file</command></entry>
-		<entry>foo.cap</entry>
-	      </row>
-	      <row>
-		<entry>foo.cap</entry>
-		<entry>x</entry>
-		<entry>-</entry>
-		<entry><command>Multiple files, continuous</command></entry>
-		<entry>foo_00001_20100205110102.cap, foo_00002_20100205110318.cap, ...</entry>
-	      </row>
-	      <row>
-		<entry>foo.cap</entry>
-		<entry>x</entry>
-		<entry>x</entry>
-		<entry><command>Multiple files, ring buffer</command></entry>
-		<entry>foo_00001_20100205110102.cap, foo_00002_20100205110318.cap, ...</entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+      <colspec colnum="3" colwidth="80pt"/>
+      <colspec colnum="4" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>"File" option</entry>
+        <entry>"Use multiple files" option</entry>
+        <entry>"Ring buffer with n files" option</entry>
+        <entry>Mode</entry>
+        <entry>Resulting filename(s) used</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry>-</entry>
+        <entry>-</entry>
+        <entry>-</entry>
+        <entry><command>Single temporary file</command></entry>
+        <entry>wiresharkXXXXXX (where XXXXXX is a unique number)</entry>
+          </row>
+          <row>
+        <entry>foo.cap</entry>
+        <entry>-</entry>
+        <entry>-</entry>
+        <entry><command>Single named file</command></entry>
+        <entry>foo.cap</entry>
+          </row>
+          <row>
+        <entry>foo.cap</entry>
+        <entry>x</entry>
+        <entry>-</entry>
+        <entry><command>Multiple files, continuous</command></entry>
+        <entry>foo_00001_20100205110102.cap, foo_00002_20100205110318.cap, ...</entry>
+          </row>
+          <row>
+        <entry>foo.cap</entry>
+        <entry>x</entry>
+        <entry>x</entry>
+        <entry><command>Multiple files, ring buffer</command></entry>
+        <entry>foo_00001_20100205110102.cap, foo_00002_20100205110318.cap, ...</entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
-	<variablelist>
-	  <varlistentry>
-	    <term><command>Single temporary file</command></term>
-	    <listitem>
-	<para>
-	A temporary file will be created and used (this is the default). After the 
-	capturing is stopped, this file can be saved later under a user specified 
-	name.
-	</para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term><command>Single named file</command></term>
-	    <listitem>
-	<para>
-	A single capture file will be used. If you want to place the new capture 
-	file to a specific folder, choose this mode.
-	</para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term><command>Multiple files, continuous</command></term>
-	    <listitem>
-	<para>
-	Like the "Single named file" mode, but a new file is created and used, 
-	after reaching one of the multiple file switch conditions (one of the 
-	"Next file every ..." values).
-	</para>
-	    </listitem>
-	  </varlistentry>
-	  <varlistentry>
-	    <term><command>Multiple files, ring buffer</command></term>
-	    <listitem>
-	<para>
-	Much like "Multiple files continuous", reaching one of the multiple files 
-	switch conditions (one of the "Next file every ..." values) will switch 
-	to the next file. This will be a newly created file if value of "Ring 
-	buffer with n files" is not reached, otherwise it will replace the oldest 
-	of the formerly used files (thus forming a "ring").
-	</para>
-	<para>
-	This mode will limit the maximum disk usage, even for an unlimited amount of 
-	capture input data, keeping the latest captured data.
-	</para>
-	    </listitem>
-	  </varlistentry>
-	</variablelist>
-	</section>
+    <variablelist>
+      <varlistentry>
+        <term><command>Single temporary file</command></term>
+        <listitem>
+    <para>
+    A temporary file will be created and used (this is the default). After the 
+    capturing is stopped, this file can be saved later under a user specified 
+    name.
+    </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><command>Single named file</command></term>
+        <listitem>
+    <para>
+    A single capture file will be used. If you want to place the new capture 
+    file to a specific folder, choose this mode.
+    </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><command>Multiple files, continuous</command></term>
+        <listitem>
+    <para>
+    Like the "Single named file" mode, but a new file is created and used, 
+    after reaching one of the multiple file switch conditions (one of the 
+    "Next file every ..." values).
+    </para>
+        </listitem>
+      </varlistentry>
+      <varlistentry>
+        <term><command>Multiple files, ring buffer</command></term>
+        <listitem>
+    <para>
+    Much like "Multiple files continuous", reaching one of the multiple files 
+    switch conditions (one of the "Next file every ..." values) will switch 
+    to the next file. This will be a newly created file if value of "Ring 
+    buffer with n files" is not reached, otherwise it will replace the oldest 
+    of the formerly used files (thus forming a "ring").
+    </para>
+    <para>
+    This mode will limit the maximum disk usage, even for an unlimited amount of 
+    capture input data, keeping the latest captured data.
+    </para>
+        </listitem>
+      </varlistentry>
+    </variablelist>
+    </section>
 
   <section id="ChCapLinkLayerHeader"><title>Link-layer header type</title>
-	<para>
-	In the usual case, you won't have to choose this link-layer header type. 
-	The following paragraphs describe the exceptional cases, where
-	selecting this type is possible, so you will have a guide of what to do:
-	</para>
+    <para>
+    In the usual case, you won't have to choose this link-layer header type. 
+    The following paragraphs describe the exceptional cases, where
+    selecting this type is possible, so you will have a guide of what to do:
+    </para>
     <para>
     If you are capturing on an 802.11 device on some versions of BSD, this 
-	might offer a choice of "Ethernet" or "802.11".  "Ethernet" will cause 
-	the captured packets to have fake Ethernet headers; "802.11" will cause 
-	them to have IEEE 802.11 headers.  Unless the capture needs to be read by 
-	an application that doesn't support 802.11 headers, you should select 
-	"802.11".
-	</para>
-	<para>
+    might offer a choice of "Ethernet" or "802.11".  "Ethernet" will cause 
+    the captured packets to have fake Ethernet headers; "802.11" will cause 
+    them to have IEEE 802.11 headers.  Unless the capture needs to be read by 
+    an application that doesn't support 802.11 headers, you should select 
+    "802.11".
+    </para>
+    <para>
     If you are capturing on an Endace DAG card connected to a synchronous 
-	serial line, this might offer a choice of "PPP over serial" or 
-	"Cisco HDLC"; if the protocol on the serial line is PPP, select 
-	"PPP over serial", and if the protocol on the serial line is Cisco HDLC, 
-	select "Cisco HDLC".
-	</para>
-	<para>
+    serial line, this might offer a choice of "PPP over serial" or 
+    "Cisco HDLC"; if the protocol on the serial line is PPP, select 
+    "PPP over serial", and if the protocol on the serial line is Cisco HDLC, 
+    select "Cisco HDLC".
+    </para>
+    <para>
     If you are capturing on an Endace DAG card connected to an ATM network, 
-	this might offer a choice of "RFC 1483 IP-over-ATM" or "Sun raw ATM".  
-	If the only traffic being captured is RFC 1483 LLC-encapsulated IP, or if 
-	the capture needs to be read by an application that doesn't support SunATM 
-	headers, select "RFC 1483 IP-over-ATM", otherwise select "Sun raw ATM".
-	</para>
-	<para>
+    this might offer a choice of "RFC 1483 IP-over-ATM" or "Sun raw ATM".  
+    If the only traffic being captured is RFC 1483 LLC-encapsulated IP, or if 
+    the capture needs to be read by an application that doesn't support SunATM 
+    headers, select "RFC 1483 IP-over-ATM", otherwise select "Sun raw ATM".
+    </para>
+    <para>
     If you are capturing on an Ethernet device, this might offer a choice of 
-	"Ethernet" or "DOCSIS".  If you are capturing traffic from a Cisco Cable 
-	Modem Termination System that is putting DOCSIS traffic onto the Ethernet 
-	to be captured, select "DOCSIS", otherwise select "Ethernet".
+    "Ethernet" or "DOCSIS".  If you are capturing traffic from a Cisco Cable 
+    Modem Termination System that is putting DOCSIS traffic onto the Ethernet 
+    to be captured, select "DOCSIS", otherwise select "Ethernet".
     </para>
   </section>
 
@@ -1224,22 +1223,22 @@ wireshark -i eth0 -k
     <para>
       Wireshark uses the libpcap filter language for capture filters. 
       This is explained in the tcpdump man page, which can be hard to 
-	  understand, so it's explained here to some extent.
+      understand, so it's explained here to some extent.
     </para>
     <tip>
       <title>Tip!</title>
       <para>
-	  You will find a lot of Capture Filter examples at <ulink 
-	  url="&WiresharkWikiCaptureFiltersPage;">&WiresharkWikiCaptureFiltersPage;</ulink>.
+      You will find a lot of Capture Filter examples at <ulink 
+      url="&WiresharkWikiCaptureFiltersPage;">&WiresharkWikiCaptureFiltersPage;</ulink>.
       </para>
     </tip>
     <para>
       You enter the capture filter into the Filter field of the Wireshark 
       Capture Options dialog box, as shown in 
       <xref linkend="ChCapCaptureOptionsDialog"/>. The following is an outline 
-	  of the syntax of the <command>tcpdump</command> capture filter language. 
-	  See the expression option at the tcpdump manual page for details:
-	  <ulink url="&TcpdumpManpage;"/>.
+      of the syntax of the <command>tcpdump</command> capture filter language. 
+      See the expression option at the tcpdump manual page for details:
+      <ulink url="&TcpdumpManpage;"/>.
     </para>
     <para>
       A capture filter takes the form of a series of primitive expressions 
@@ -1251,214 +1250,222 @@ wireshark -i eth0 -k
       An example is shown in <xref linkend="ChCapExFilt1"/>.
 
       <example id="ChCapExFilt1">
-	<title>
-	  A capture filter for telnet that captures traffic to and from a 
-	  particular host
-	</title>
-	<programlisting>
+    <title>
+      A capture filter for telnet that captures traffic to and from a 
+      particular host
+    </title>
+    <programlisting>
 tcp port 23 and host 10.0.0.5
-	</programlisting>
+    </programlisting>
       </example>
       This example captures telnet traffic to and from the host 
       10.0.0.5, and shows how to use two primitives and the 
       <command>and</command> conjunction.  Another example is shown in 
       <xref linkend="ChCapExFilt2"/>, and shows how to capture all 
-	telnet traffic except that from 10.0.0.5.
-	<example id="ChCapExFilt2">
-	  <title>
-	    Capturing all telnet traffic not from 10.0.0.5</title>
-	  <programlisting>
+    telnet traffic except that from 10.0.0.5.
+    <example id="ChCapExFilt2">
+      <title>
+        Capturing all telnet traffic not from 10.0.0.5</title>
+      <programlisting>
 tcp port 23 and not src host 10.0.0.5
-	  </programlisting>
-	</example>
+      </programlisting>
+    </example>
       </para>
 
       <para>
-	  XXX - add examples to the following list.
+      XXX - add examples to the following list.
       </para>
       <para>
       A primitive is simply one of the following:
       <variablelist>
-	<varlistentry>
-	  <term><command>[src|dst] host &lt;host></command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on a host IP 
-	      address or name. You can optionally precede the 
-	      primitive with the keyword <command>src|dst</command> 
-	      to specify that you are only interested in source or 
-	      destination addresses. If these are not present, 
-	      packets where the specified address appears as either 
-	      the source or the destination address will be selected.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>
-	    <command>ether [src|dst] host &lt;ehost></command>
-	  </term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on Ethernet host 
-	      addresses. You can optionally include the keyword 
-	      <command>src|dst</command> between the keywords 
-	      <command>ether</command> and <command>host</command> 
-	      to specify that you are only interested in source 
-	      or destination addresses.  If these are not present, 
-	      packets where the specified address appears in either 
-	      the source or destination address will be selected.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>gateway host &lt;host></command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on packets that 
-	      used <command>host</command> as a gateway. That is, where 
-	      the Ethernet source or destination was 
-	      <command>host</command> but neither the source nor 
-	      destination IP address was <command>host</command>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>
-	    <command>
-	      [src|dst] net &lt;net> [{mask &lt;mask>}|{len &lt;len>}]
-	    </command>
-	  </term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on network numbers. 
-	      You can optionally precede this primitive with the 
-	      keyword <command>src|dst</command> to specify that you 
-	      are only interested in a source or destination network. 
-	      If neither of these are present, packets will be 
-	      selected that have the specified network in either the
-	      source or destination address.  In addition, you can 
-	      specify either the netmask or the CIDR prefix for the 
-	      network if they are different from your own. 
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term>
-	    <command>[tcp|udp] [src|dst] port &lt;port></command>
-	  </term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on TCP and UDP port 
-	      numbers. You can optionally precede this primitive with 
-	      the keywords <command>src|dst</command> and 
-	      <command>tcp|udp</command> which allow you to specify 
-	      that you are only interested in source or destination 
-	      ports and TCP or UDP packets respectively.  The 
-	      keywords <command>tcp|udp</command> must appear before 
-	      <command>src|dst</command>.
-	    </para>
-	    <para>
-	      If these are not specified, packets will be selected 
-	      for both the TCP and UDP protocols and when the 
-	      specified address appears in either the source or 
-	      destination port field.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>less|greater &lt;length></command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on packets whose 
-	      length was less than or equal to the specified length, 
-	      or greater than or equal to the specified length, 
-	      respectively.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>ip|ether proto &lt;protocol></command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on the specified 
-	      protocol at either the Ethernet layer or the IP layer.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>ether|ip broadcast|multicast</command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to filter on either 
-	      Ethernet or IP broadcasts or multicasts.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>&lt;expr> relop &lt;expr></command></term>
-	  <listitem>
-	    <para>
-	      This primitive allows you to create complex filter 
-	      expressions that select bytes or ranges of bytes in 
-	      packets.  Please see the tcpdump man page at
-		  <ulink url="&TcpdumpManpage;"/> for more details.
-	    </para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry>
+      <term><command>[src|dst] host &lt;host></command></term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on a host IP 
+          address or name. You can optionally precede the 
+          primitive with the keyword <command>src|dst</command> 
+          to specify that you are only interested in source or 
+          destination addresses. If these are not present, 
+          packets where the specified address appears as either 
+          the source or the destination address will be selected.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        <command>ether [src|dst] host &lt;ehost></command>
+      </term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on Ethernet host 
+          addresses. You can optionally include the keyword 
+          <command>src|dst</command> between the keywords 
+          <command>ether</command> and <command>host</command> 
+          to specify that you are only interested in source 
+          or destination addresses.  If these are not present, 
+          packets where the specified address appears in either 
+          the source or destination address will be selected.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>gateway host &lt;host></command></term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on packets that 
+          used <command>host</command> as a gateway. That is, where 
+          the Ethernet source or destination was 
+          <command>host</command> but neither the source nor 
+          destination IP address was <command>host</command>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        <command>
+          [src|dst] net &lt;net> [{mask &lt;mask>}|{len &lt;len>}]
+        </command>
+      </term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on network numbers. 
+          You can optionally precede this primitive with the 
+          keyword <command>src|dst</command> to specify that you 
+          are only interested in a source or destination network. 
+          If neither of these are present, packets will be 
+          selected that have the specified network in either the
+          source or destination address.  In addition, you can 
+          specify either the netmask or the CIDR prefix for the 
+          network if they are different from your own. 
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        <command>[tcp|udp] [src|dst] port &lt;port></command>
+      </term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on TCP and UDP port 
+          numbers. You can optionally precede this primitive with 
+          the keywords <command>src|dst</command> and 
+          <command>tcp|udp</command> which allow you to specify 
+          that you are only interested in source or destination 
+          ports and TCP or UDP packets respectively.  The 
+          keywords <command>tcp|udp</command> must appear before 
+          <command>src|dst</command>.
+        </para>
+        <para>
+          If these are not specified, packets will be selected 
+          for both the TCP and UDP protocols and when the 
+          specified address appears in either the source or 
+          destination port field.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>less|greater &lt;length></command></term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on packets whose 
+          length was less than or equal to the specified length, 
+          or greater than or equal to the specified length, 
+          respectively.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>ip|ether proto &lt;protocol></command></term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on the specified 
+          protocol at either the Ethernet layer or the IP layer.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>ether|ip broadcast|multicast</command></term>
+      <listitem>
+        <para>
+          This primitive allows you to filter on either 
+          Ethernet or IP broadcasts or multicasts.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>&lt;expr> relop &lt;expr></command></term>
+      <listitem>
+        <para>
+          This primitive allows you to create complex filter 
+          expressions that select bytes or ranges of bytes in 
+          packets.  Please see the tcpdump man page at
+          <ulink url="&TcpdumpManpage;"/> for more details.
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </para>
   <section id="ChCapCaptureAutoFilterSection">
     <title>Automatic Remote Traffic Filtering</title>
     <para>
-	If Wireshark is running remotely (using e.g. SSH, an exported X11 window, 
-	a terminal server, ...), the remote content has to be transported over 
-	the network, adding a lot of (usually unimportant) packets to the actually 
-	interesting traffic.
+    If Wireshark is running remotely (using e.g. SSH, an exported X11 window, 
+    a terminal server, ...), the remote content has to be transported over 
+    the network, adding a lot of (usually unimportant) packets to the actually 
+    interesting traffic.
     </para>
-    <para>	
-	To avoid this, Wireshark tries to figure out if it's remotely connected 
-	(by looking at some specific environment variables) and automatically 
-	creates a capture filter that matches aspects of the connection.  
+    <para>    
+    To avoid this, Wireshark tries to figure out if it's remotely connected 
+    (by looking at some specific environment variables) and automatically 
+    creates a capture filter that matches aspects of the connection.  
     </para>
-    <para>		
-	The following environment variables are analyzed:
+    <para>        
+    The following environment variables are analyzed:
     </para>
       <variablelist>
-	<varlistentry>
-	  <term><command>SSH_CONNECTION</command> (ssh)</term>
-	  <listitem>
-    <para>	
-   	&lt;remote IP> &lt;remote port> &lt;local IP> &lt;local port>
+    <varlistentry>
+      <term><command>SSH_CONNECTION</command> (ssh)</term>
+      <listitem>
+    <para>    
+       &lt;remote IP> &lt;remote port> &lt;local IP> &lt;local port>
     </para>
-	  </listitem>
-	</varlistentry>
-	
-	<varlistentry>
-	  <term><command>SSH_CLIENT</command> (ssh)</term>
-	  <listitem>
-    <para>	
-   	&lt;remote IP> &lt;remote port> &lt;local port>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>SSH_CLIENT</command> (ssh)</term>
+      <listitem>
+    <para>    
+       &lt;remote IP> &lt;remote port> &lt;local port>
     </para>
-	  </listitem>
-	</varlistentry>
-	
-	<varlistentry>
-	  <term><command>REMOTEHOST</command> (tcsh, others?)</term>
-	  <listitem>
-    <para>	
-   	&lt;remote name>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>REMOTEHOST</command> (tcsh, others?)</term>
+      <listitem>
+    <para>    
+       &lt;remote name>
     </para>
-	  </listitem>
-	</varlistentry>
-	
-	<varlistentry>
-	  <term><command>DISPLAY</command> (x11)</term>
-	  <listitem>
-    <para>	
-   	[remote name]:&lt;display num>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>DISPLAY</command> (x11)</term>
+      <listitem>
+    <para>    
+       [remote name]:&lt;display num>
     </para>
-	  </listitem>
-	</varlistentry>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>SESSIONNAME</command> (terminal server)</term>
+      <listitem>
+    <para>    
+       &lt;remote name>
+    </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
   <para>
   On Windows it asks the operating system if it's running in a Remote Desktop Services
@@ -1469,87 +1476,87 @@ tcp port 23 and not src host 10.0.0.5
 
   <section id="ChCapRunningSection"><title>While a Capture is running ...</title>
     <para>
-	While a capture is running, the following dialog box is shown:
+    While a capture is running, the following dialog box is shown:
       <figure id="ChCapCaptureInfoDialog">
-	<title>The "Capture Info" dialog box</title>
-	<graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/>
+    <title>The "Capture Info" dialog box</title>
+    <graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/>
       </figure>
-	This dialog box will inform you about the number of captured packets and 
-	the time since the capture was started. The selection of which protocols
-	are counted cannot be changed.
-	</para>
-	  <tip><title>Tip!</title>
-	  <para>
-	  This Capture Info dialog box can be hidden, using the "Hide capture info 
-	  dialog" option in the Capture Options dialog box.
-	  </para>
-	  </tip>
-	<section id="ChCapStopSection"><title>Stop the running capture</title>
+    This dialog box will inform you about the number of captured packets and 
+    the time since the capture was started. The selection of which protocols
+    are counted cannot be changed.
+    </para>
+      <tip><title>Tip!</title>
+      <para>
+      This Capture Info dialog box can be hidden, using the "Hide capture info 
+      dialog" option in the Capture Options dialog box.
+      </para>
+      </tip>
+    <section id="ChCapStopSection"><title>Stop the running capture</title>
     <para>
       A running capture session will be stopped in one of the following ways:
       <orderedlist>
-	<listitem>
-	  <para>Using the 
-	  "<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
-	  Stop" button from the <command>Capture Info dialog box
-	  </command>.
-	  </para>
-	  <note><title>Note!</title>
-	  <para>
-	  The Capture Info dialog box might be hidden, if the option "Hide capture 
-	  info dialog" is used.
-	  </para>
-	  </note>
-	</listitem>
-	<listitem>
-	  <para>Using the <command>menu item</command>
-	  "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
-	  Stop". 
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>Using the <command>toolbar item</command>
-	  "<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
-	  Stop". 
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>Pressing the accelerator keys: <command>Ctrl+E</command>. 
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>The capture will be automatically stopped, if one of the 
-	  <command>Stop Conditions</command> is exceeded, e.g. the maximum amount 
-	  of data was captured.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>Using the 
+      "<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
+      Stop" button from the <command>Capture Info dialog box
+      </command>.
+      </para>
+      <note><title>Note!</title>
+      <para>
+      The Capture Info dialog box might be hidden, if the option "Hide capture 
+      info dialog" is used.
+      </para>
+      </note>
+    </listitem>
+    <listitem>
+      <para>Using the <command>menu item</command>
+      "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
+      Stop". 
+      </para>
+    </listitem>
+    <listitem>
+      <para>Using the <command>toolbar item</command>
+      "<inlinegraphic entityref="WiresharkToolbarCaptureStop" format="PNG"/>
+      Stop". 
+      </para>
+    </listitem>
+    <listitem>
+      <para>Pressing the accelerator keys: <command>Ctrl+E</command>. 
+      </para>
+    </listitem>
+    <listitem>
+      <para>The capture will be automatically stopped, if one of the 
+      <command>Stop Conditions</command> is exceeded, e.g. the maximum amount 
+      of data was captured.
+      </para>
+    </listitem>
       </orderedlist>
     </para>
     </section>
-	<section id="ChCapRestartSection"><title>Restart a running capture</title>
+    <section id="ChCapRestartSection"><title>Restart a running capture</title>
     <para>
       A running capture session can be restarted with the same capture options 
-	  as the last time, this will remove all packets previously captured.
-	  This can be useful, if some uninteresting packets are captured and 
-	  there's no need to keep them.
+      as the last time, this will remove all packets previously captured.
+      This can be useful, if some uninteresting packets are captured and 
+      there's no need to keep them.
     </para>
-    <para>	  
-	  Restart is a convenience function and 
-	  equivalent to a capture stop following by an immediate capture start. 
-	  A restart can be triggered in one of the following ways:
+    <para>      
+      Restart is a convenience function and 
+      equivalent to a capture stop following by an immediate capture start. 
+      A restart can be triggered in one of the following ways:
       <orderedlist>
-	<listitem>
-	  <para>Using the <command>menu item</command>
-	  "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/>
-	  Restart". 
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>Using the <command>toolbar item</command> 
-	  "<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/>
-	  Restart". 
-	  </para>
-	</listitem>
+    <listitem>
+      <para>Using the <command>menu item</command>
+      "Capture/<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/>
+      Restart". 
+      </para>
+    </listitem>
+    <listitem>
+      <para>Using the <command>toolbar item</command> 
+      "<inlinegraphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/>
+      Restart". 
+      </para>
+    </listitem>
       </orderedlist>
     </para>
     </section>
diff --git a/docbook/wsug_src/WSUG_chapter_customize.xml b/docbook/wsug_src/WSUG_chapter_customize.xml
index 34456a3922..9849b43451 100644
--- a/docbook/wsug_src/WSUG_chapter_customize.xml
+++ b/docbook/wsug_src/WSUG_chapter_customize.xml
@@ -6,32 +6,32 @@
 
   <section id="ChCustIntroduction"><title>Introduction</title>
     <para>
-	Wireshark's default behaviour will usually suit your needs pretty well.
-	However, as you become more familiar with Wireshark, it can be customized
-	in various ways to suit your needs even better. In this chapter we explore:
-	<itemizedlist>
-	<listitem>
-	  <para>
-	    How to start Wireshark with command line parameters
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to colorize the packet list
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to control protocol dissection
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to use the various preference settings
-	  </para>
-	</listitem>
-	</itemizedlist>
-	</para>
+    Wireshark's default behaviour will usually suit your needs pretty well.
+    However, as you become more familiar with Wireshark, it can be customized
+    in various ways to suit your needs even better. In this chapter we explore:
+    <itemizedlist>
+    <listitem>
+      <para>
+        How to start Wireshark with command line parameters
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to colorize the packet list
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to control protocol dissection
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to use the various preference settings
+      </para>
+    </listitem>
+    </itemizedlist>
+    </para>
   </section>
 
   <section id="ChCustCommandLine"><title>Start Wireshark from the command line</title>
@@ -46,10 +46,10 @@
       command line parameters. To see what they are, simply enter the
       command <command>wireshark -h</command> and the help information
       shown in <xref linkend="ChCustEx1"/> (or something similar) should be
-	  printed.
-	<example id="ChCustEx1">
-	  <title>Help information available from Wireshark</title>
-	  <programlisting>
+      printed.
+    <example id="ChCustEx1">
+      <title>Help information available from Wireshark</title>
+      <programlisting>
 Wireshark 1.9.0 (SVN Rev 47047 from /trunk)
 Interactively dump and analyze network traffic.
 See http://www.wireshark.org for more information.
@@ -117,9 +117,9 @@ Miscellaneous:
   --display=DISPLAY        X display to use
 
 </programlisting>
-	</example>
+    </example>
 
-	We will examine each of the command line options in turn.
+    We will examine each of the command line options in turn.
     </para>
     <para>
       The first thing to notice is that issuing the command
@@ -127,457 +127,457 @@ Miscellaneous:
       <application>Wireshark</application>.
       However, you can include as many of the command line parameters as
       you like. Their meanings are as follows ( in alphabetical order ):
-	  XXX - is the alphabetical order a good choice? Maybe better task based?
+      XXX - is the alphabetical order a good choice? Maybe better task based?
       <variablelist>
-	  <varlistentry><term><command>-a &lt;capture autostop condition></command></term>
-	  <listitem>
-		<para>
-    	Specify a criterion that specifies when Wireshark is to stop writing
-		to a capture file. The criterion is of the form test:value, where test
-		is one of:
-		<variablelist>
-		<varlistentry><term><command>duration</command>:value</term>
-			<listitem><para>
-			Stop writing to a capture file after value of seconds have elapsed.
-			</para></listitem>
-		</varlistentry>
-		<varlistentry><term><command>filesize</command>:value</term>
-			<listitem><para>
-			Stop writing to a capture file after it reaches a size of value
-			kilobytes (where a kilobyte is 1000 bytes, not 1024 bytes). If
-			this option is used together with the -b option, Wireshark will
-			stop writing to the current capture file and switch to the next
-			one if filesize is reached.
-			</para></listitem>
-		</varlistentry>
-		<varlistentry><term><command>files</command>:value</term>
-			<listitem><para>
-			Stop writing to capture files after value number of files were
-			written.
-			</para></listitem>
-		</varlistentry>
-		</variablelist>
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-b &lt;capture ring buffer option></command></term>
-	  <listitem>
-	    <para>
-		If a maximum capture file size was specified, this option causes Wireshark to run
-		in "ring buffer" mode, with the specified number of files. In "ring
-		buffer" mode, Wireshark will write to several capture files. Their
-		name is based on the number of the file and on the creation date and
-		time.
-	    </para>
-	    <para>
-		When the first capture file fills up Wireshark will switch to writing
-		to the next file, and so on.  With the <command>files</command> option it's
-		also possible to form a "ring buffer."  This will fill up new files until the
-		number of files specified, at which point the data in the first file will be
-		discarded so a new file can be written.
-	    </para>
-	    <para>
-		If the optional <command>duration</command> is specified, Wireshark will also
-		switch to the next file when the specified number of seconds has elapsed even
-		if the current file is not completely fills up.
-	    </para>
-	    <para>
-		<variablelist>
-		<varlistentry><term><command>duration</command>:value</term>
-			<listitem><para>
-			Switch to the next file after value seconds have elapsed, even
-			if the current file is not completely filled up.
-			</para></listitem>
-		</varlistentry>
-		<varlistentry><term><command>filesize</command>:value</term>
-			<listitem><para>
-			Switch to the next file after it reaches a size of value kilobytes
-			(where a kilobyte is 1000 bytes, not 1024 bytes).
-			</para></listitem>
-		</varlistentry>
-		<varlistentry><term><command>files</command>:value</term>
-			<listitem><para>
-			Begin again with the first file after value number of files were
-			written (form a ring buffer).
-			</para></listitem>
-		</varlistentry>
-		</variablelist>
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-B &lt;capture buffer size (Win32 only)></command></term>
-	  <listitem>
-	    <para>
-	      Win32 only: set capture buffer size (in MB, default is 1MB). This
-		  is used by the capture driver to buffer packet data until that
-		  data can be written to disk. If you encounter packet drops while
-		  capturing, try to increase this size.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-c &lt;capture packet count></command></term>
-	  <listitem>
-	    <para>
-	      This option specifies the maximum number of packets to capture
-	      when capturing live data.  It would be used in conjunction
-	      with the <command>-k</command> option.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-D</command></term>
-	  <listitem>
-	    <para>
+      <varlistentry><term><command>-a &lt;capture autostop condition></command></term>
+      <listitem>
+        <para>
+        Specify a criterion that specifies when Wireshark is to stop writing
+        to a capture file. The criterion is of the form test:value, where test
+        is one of:
+        <variablelist>
+        <varlistentry><term><command>duration</command>:value</term>
+            <listitem><para>
+            Stop writing to a capture file after value of seconds have elapsed.
+            </para></listitem>
+        </varlistentry>
+        <varlistentry><term><command>filesize</command>:value</term>
+            <listitem><para>
+            Stop writing to a capture file after it reaches a size of value
+            kilobytes (where a kilobyte is 1000 bytes, not 1024 bytes). If
+            this option is used together with the -b option, Wireshark will
+            stop writing to the current capture file and switch to the next
+            one if filesize is reached.
+            </para></listitem>
+        </varlistentry>
+        <varlistentry><term><command>files</command>:value</term>
+            <listitem><para>
+            Stop writing to capture files after value number of files were
+            written.
+            </para></listitem>
+        </varlistentry>
+        </variablelist>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-b &lt;capture ring buffer option></command></term>
+      <listitem>
+        <para>
+        If a maximum capture file size was specified, this option causes Wireshark to run
+        in "ring buffer" mode, with the specified number of files. In "ring
+        buffer" mode, Wireshark will write to several capture files. Their
+        name is based on the number of the file and on the creation date and
+        time.
+        </para>
+        <para>
+        When the first capture file fills up Wireshark will switch to writing
+        to the next file, and so on.  With the <command>files</command> option it's
+        also possible to form a "ring buffer."  This will fill up new files until the
+        number of files specified, at which point the data in the first file will be
+        discarded so a new file can be written.
+        </para>
+        <para>
+        If the optional <command>duration</command> is specified, Wireshark will also
+        switch to the next file when the specified number of seconds has elapsed even
+        if the current file is not completely fills up.
+        </para>
+        <para>
+        <variablelist>
+        <varlistentry><term><command>duration</command>:value</term>
+            <listitem><para>
+            Switch to the next file after value seconds have elapsed, even
+            if the current file is not completely filled up.
+            </para></listitem>
+        </varlistentry>
+        <varlistentry><term><command>filesize</command>:value</term>
+            <listitem><para>
+            Switch to the next file after it reaches a size of value kilobytes
+            (where a kilobyte is 1000 bytes, not 1024 bytes).
+            </para></listitem>
+        </varlistentry>
+        <varlistentry><term><command>files</command>:value</term>
+            <listitem><para>
+            Begin again with the first file after value number of files were
+            written (form a ring buffer).
+            </para></listitem>
+        </varlistentry>
+        </variablelist>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-B &lt;capture buffer size (Win32 only)></command></term>
+      <listitem>
+        <para>
+          Win32 only: set capture buffer size (in MB, default is 1MB). This
+          is used by the capture driver to buffer packet data until that
+          data can be written to disk. If you encounter packet drops while
+          capturing, try to increase this size.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-c &lt;capture packet count></command></term>
+      <listitem>
+        <para>
+          This option specifies the maximum number of packets to capture
+          when capturing live data.  It would be used in conjunction
+          with the <command>-k</command> option.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-D</command></term>
+      <listitem>
+        <para>
 Print a list of the interfaces on which Wireshark can capture, and
 exit.  For each network interface, a number and an
 interface name, possibly followed by a text description of the
 interface, is printed.  The interface name or the number can be supplied
 to the <command>-i</command> flag to specify an interface on which to capture.
-	    </para>
-	    <para>
+        </para>
+        <para>
 This can be useful on systems that don't have a command to list them
 (e.g., Windows systems, or UNIX systems lacking <command>ifconfig -a</command>);
 the number can be useful on Windows 2000 and later systems, where the
 interface name is a somewhat complex string.
-	    </para>
-	    <para>
+        </para>
+        <para>
 Note that "can capture" means that Wireshark was able to open
 that device to do a live capture; if, on your system, a program doing a
 network capture must be run from an account with special privileges (for
 example, as root), then, if Wireshark is run with the <command>-D</command> flag and
 is not run from such an account, it will not list any interfaces.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-f &lt;capture filter></command></term>
-	  <listitem>
-	    <para>
-	      This option sets the initial capture filter expression to
-	      be used when capturing packets.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-g &lt;packet number></command></term>
-	  <listitem>
-	    <para>
-	      After reading in a capture file using the -r flag, go to the given
-		  packet number.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-h</command></term>
-	  <listitem>
-	    <para>
-	      The <command>-h</command> option requests Wireshark to print
-	      its version and usage instructions (as shown above) and exit.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-i &lt;capture interface></command></term>
-	  <listitem>
-	    <para>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-f &lt;capture filter></command></term>
+      <listitem>
+        <para>
+          This option sets the initial capture filter expression to
+          be used when capturing packets.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-g &lt;packet number></command></term>
+      <listitem>
+        <para>
+          After reading in a capture file using the -r flag, go to the given
+          packet number.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-h</command></term>
+      <listitem>
+        <para>
+          The <command>-h</command> option requests Wireshark to print
+          its version and usage instructions (as shown above) and exit.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-i &lt;capture interface></command></term>
+      <listitem>
+        <para>
 Set the name of the network interface or pipe to use for live packet
 capture.
-	    </para>
-	    <para>
+        </para>
+        <para>
 Network interface names should match one of the names listed in
 <command>wireshark -D</command> (described above); a number, as reported by
 <command>wireshark -D</command>, can also be used.  If you're using UNIX, <command>netstat
 -i</command> or <command>ifconfig -a</command> might also work to list interface names,
 although not all versions of UNIX support the <command>-a</command> flag to <command>ifconfig</command>.
-	    </para>
-	    <para>
+        </para>
+        <para>
 If no interface is specified, Wireshark searches the list of
 interfaces, choosing the first non-loopback interface if there are any
 non-loopback interfaces, and choosing the first loopback interface if
 there are no non-loopback interfaces; if there are no interfaces,
 Wireshark reports an error and doesn't start the capture.
-	    </para>
-	    <para>
+        </para>
+        <para>
 Pipe names should be either the name of a FIFO (named pipe) or ``-'' to
 read data from the standard input.  Data read from pipes must be in
 standard libpcap format.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-J &lt;jump filter></command></term>
-	  <listitem>
-	    <para>
-	      After reading in a capture file using the <command>-r</command>
-	      flag, jump to the first packet which matches the filter expression.
-	      The filter expression is in display filter format. If an exact match
-	      cannot be found the first packet afterwards is selected.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-j</command></term>
-	  <listitem>
-	    <para>
-	      Use this option after the <command>-J</command> option to search
-	      backwards for a first packet to go to.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-k</command></term>
-	  <listitem>
-	    <para>
-	      The <command>-k</command> option specifies that Wireshark
-	      should start capturing packets immediately.  This option
-	      requires the use of the <command>-i</command> parameter to
-	      specify the interface that packet capture will occur from.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-l</command></term>
-	  <listitem>
-	    <para>
-	      This option turns on automatic scrolling if the packet
-	      list pane is being updated automatically as packets arrive
-	      during a capture ( as specified by the <command>-S</command>
-	      flag).
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-L</command></term>
-	  <listitem>
-	    <para>
-		  List the data link types supported by the interface and exit.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-m &lt;font></command></term>
-	  <listitem>
-	    <para>
-	      This option sets the name of the font used for most text
-	      displayed by Wireshark. XXX - add an example!
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-n</command></term>
-	  <listitem>
-	    <para>
-		Disable network object name resolution (such as hostname, TCP and UDP
-		port names).
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-N &lt;name resolving flags></command></term>
-	  <listitem>
-	    <para>
-	      Turns on name resolving for particular types of addresses
-	      and port numbers; the argument is a string that may contain
-	      the letters <command>m</command> to enable MAC address
-	      resolution, <command>n</command> to enable network address
-	      resolution, and <command>t</command> to enable transport-layer
-	      port number resolution.  This overrides <command>-n</command>
-	      if both <command>-N</command> and <command>-n</command> are
-	      present. The letter C enables concurrent (asynchronous) DNS lookups.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>-o &lt;preference/recent settings&gt;</command></term>
-	  <listitem>
-	    <para>
-	      Sets a preference or recent value, overriding the default value and
-	      any value read from a preference/recent file.  The argument to the
-	      flag is a string of the form prefname:value, where prefname
-	      is the name of the preference (which is the same name that
-	      would appear in the preference/recent file), and value is the value
-	      to which it should be set.  Multiple instances of
-	      <command>-o &lt;preference settings&gt; </command> can be
-	      given on a single command line.
-	    </para>
-	    <para>An example of setting a single preference would be: </para>
-	    <para>
-	      <command>
-		wireshark -o mgcp.display_dissect_tree:TRUE
-	      </command>
-	    </para>
-	    <para>
-	      An example of setting multiple preferences would be:
-	    </para>
-	    <para>
-	      <command>
-		wireshark -o mgcp.display_dissect_tree:TRUE -o mgcp.udp.callagent_port:2627
-	      </command>
-	    </para>
-	    <tip><title>Tip!</title>
-	      <para>
-		You can get a list of all available preference strings from the
-		preferences file, see <xref linkend="AppFiles"/>.
-	      </para>
-	    </tip>
-	    <para>User access tables can be overridden using "uat," followed by
-	    the UAT file name and a valid record for the file: </para>
-	    <para>
-	      <command>
-		wireshark -o "uat:user_dlts:\"User 0 (DLT=147)\",\"http\",\"0\",\"\",\"0\",\"\""
-	      </command>
-	    </para>
-	    <para>
-	      The example above would dissect packets with a libpcap data
-	      link type 147 as HTTP, just as if you had configured it in the
-	      DLT_USER protocol preferences.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-p</command></term>
-	  <listitem>
-	    <para>
-	      Don't put the interface into promiscuous mode.  Note that
-	      the interface might be in promiscuous mode for some other
-	      reason; hence, -p cannot be used to ensure that the only
-	      traffic that is captured is traffic sent to or from the
-	      machine on which Wireshark is running, broadcast traffic, and
-	      multicast traffic to addresses received by that machine.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-P &lt;path setting></command></term>
-	  <listitem>
-		<para>
-		Special path settings usually detected automatically. This is used
-		for special cases, e.g. starting Wireshark from a known location on
-		an USB stick.
-		</para>
-		<para>
-		The criterion is of the form key:path, where key is one of:
-		<variablelist>
-		<varlistentry><term><command>persconf</command>:path</term>
-			<listitem><para>
-			path of personal configuration files, like the preferences files.
-			</para></listitem>
-		</varlistentry>
-		<varlistentry><term><command>persdata</command>:path</term>
-			<listitem><para>
-			path of personal data files, it's the folder initially opened.
-			After the initialization, the recent file will keep the folder
-			last used.
-			</para></listitem>
-		</varlistentry>
-		</variablelist>
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-Q</command></term>
-	  <listitem>
-	    <para>
-	      This option forces Wireshark to exit when capturing is
-	      complete. It can be used with the <command>-c</command> option.
-	      It must be used in conjunction with the
-	      <command>-i</command> and <command>-w</command> options.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-r &lt;infile></command></term>
-	  <listitem>
-	    <para>
-	      This option provides the name of a capture file for Wireshark
-	      to read and display. This capture file can be in one of the
-	      formats Wireshark understands.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-R &lt;read (display) filter></command></term>
-	  <listitem>
-	    <para>
-	      This option specifies a display filter to be applied when
-	      reading packets from a capture file. The syntax of this
-	      filter is that of the display filters discussed in
-	      <xref linkend="ChWorkDisplayFilterSection"/>.  Packets not
-		  matching the filter are discarded.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-s &lt;capture snaplen></command></term>
-	  <listitem>
-	    <para>
-	      This option specifies the snapshot length to use when
-	      capturing packets. Wireshark will only capture
-	      <command>&lt;snaplen></command> bytes of data for each packet.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-S</command></term>
-	  <listitem>
-	    <para>
-	      This option specifies that Wireshark will display packets as
-	      it captures them. This is done by capturing in one process
-	      and displaying them in a separate process. This is the same
-		  as "Update list of packets in real time" in the Capture Options
-		  dialog box.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>-t &lt;time stamp format></command></term>
-	  <listitem>
-	    <para>
-	      This option sets the format of packet timestamps that are
-	      displayed in the packet list window.  The format can be one of:
-	      <itemizedlist>
-		<listitem>
-		  <para>
-		    <command>r</command> relative, which specifies timestamps are
-		    displayed relative to the first packet captured.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>a</command> absolute, which specifies that actual times
-			be displayed for all packets.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>ad</command> absolute with date, which specifies that
-			actual dates and times be displayed for all packets.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>d</command> delta, which specifies that timestamps
-		    are relative to the previous packet.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>e</command> epoch, which specifies that timestamps
-		    are seconds since epoch (Jan 1, 1970 00:00:00)
-		  </para>
-		</listitem>
-	      </itemizedlist>
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-v</command></term>
-	  <listitem>
-	    <para>
-	      The <command>-v</command> option requests
-	      Wireshark to print out its version information and exit.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-w &lt;savefile></command></term>
-	  <listitem>
-	    <para>
-	      This option sets the name of the <command>savefile</command>
-	      to be used when saving a capture file.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-y &lt;capture link type></command></term>
-	  <listitem>
-	    <para>
-		If a capture is started from the command line with -k, set the data
-		link type to use while capturing packets. The values reported by -L
-		are the values that can be used.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-X &lt;eXtension option></command></term>
-	  <listitem>
-	    <para>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-J &lt;jump filter></command></term>
+      <listitem>
+        <para>
+          After reading in a capture file using the <command>-r</command>
+          flag, jump to the first packet which matches the filter expression.
+          The filter expression is in display filter format. If an exact match
+          cannot be found the first packet afterwards is selected.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-j</command></term>
+      <listitem>
+        <para>
+          Use this option after the <command>-J</command> option to search
+          backwards for a first packet to go to.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-k</command></term>
+      <listitem>
+        <para>
+          The <command>-k</command> option specifies that Wireshark
+          should start capturing packets immediately.  This option
+          requires the use of the <command>-i</command> parameter to
+          specify the interface that packet capture will occur from.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-l</command></term>
+      <listitem>
+        <para>
+          This option turns on automatic scrolling if the packet
+          list pane is being updated automatically as packets arrive
+          during a capture ( as specified by the <command>-S</command>
+          flag).
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-L</command></term>
+      <listitem>
+        <para>
+          List the data link types supported by the interface and exit.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-m &lt;font></command></term>
+      <listitem>
+        <para>
+          This option sets the name of the font used for most text
+          displayed by Wireshark. XXX - add an example!
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-n</command></term>
+      <listitem>
+        <para>
+        Disable network object name resolution (such as hostname, TCP and UDP
+        port names).
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-N &lt;name resolving flags></command></term>
+      <listitem>
+        <para>
+          Turns on name resolving for particular types of addresses
+          and port numbers; the argument is a string that may contain
+          the letters <command>m</command> to enable MAC address
+          resolution, <command>n</command> to enable network address
+          resolution, and <command>t</command> to enable transport-layer
+          port number resolution.  This overrides <command>-n</command>
+          if both <command>-N</command> and <command>-n</command> are
+          present. The letter C enables concurrent (asynchronous) DNS lookups.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>-o &lt;preference/recent settings&gt;</command></term>
+      <listitem>
+        <para>
+          Sets a preference or recent value, overriding the default value and
+          any value read from a preference/recent file.  The argument to the
+          flag is a string of the form prefname:value, where prefname
+          is the name of the preference (which is the same name that
+          would appear in the preference/recent file), and value is the value
+          to which it should be set.  Multiple instances of
+          <command>-o &lt;preference settings&gt; </command> can be
+          given on a single command line.
+        </para>
+        <para>An example of setting a single preference would be: </para>
+        <para>
+          <command>
+        wireshark -o mgcp.display_dissect_tree:TRUE
+          </command>
+        </para>
+        <para>
+          An example of setting multiple preferences would be:
+        </para>
+        <para>
+          <command>
+        wireshark -o mgcp.display_dissect_tree:TRUE -o mgcp.udp.callagent_port:2627
+          </command>
+        </para>
+        <tip><title>Tip!</title>
+          <para>
+        You can get a list of all available preference strings from the
+        preferences file, see <xref linkend="AppFiles"/>.
+          </para>
+        </tip>
+        <para>User access tables can be overridden using "uat," followed by
+        the UAT file name and a valid record for the file: </para>
+        <para>
+          <command>
+        wireshark -o "uat:user_dlts:\"User 0 (DLT=147)\",\"http\",\"0\",\"\",\"0\",\"\""
+          </command>
+        </para>
+        <para>
+          The example above would dissect packets with a libpcap data
+          link type 147 as HTTP, just as if you had configured it in the
+          DLT_USER protocol preferences.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-p</command></term>
+      <listitem>
+        <para>
+          Don't put the interface into promiscuous mode.  Note that
+          the interface might be in promiscuous mode for some other
+          reason; hence, -p cannot be used to ensure that the only
+          traffic that is captured is traffic sent to or from the
+          machine on which Wireshark is running, broadcast traffic, and
+          multicast traffic to addresses received by that machine.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-P &lt;path setting></command></term>
+      <listitem>
+        <para>
+        Special path settings usually detected automatically. This is used
+        for special cases, e.g. starting Wireshark from a known location on
+        an USB stick.
+        </para>
+        <para>
+        The criterion is of the form key:path, where key is one of:
+        <variablelist>
+        <varlistentry><term><command>persconf</command>:path</term>
+            <listitem><para>
+            path of personal configuration files, like the preferences files.
+            </para></listitem>
+        </varlistentry>
+        <varlistentry><term><command>persdata</command>:path</term>
+            <listitem><para>
+            path of personal data files, it's the folder initially opened.
+            After the initialization, the recent file will keep the folder
+            last used.
+            </para></listitem>
+        </varlistentry>
+        </variablelist>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-Q</command></term>
+      <listitem>
+        <para>
+          This option forces Wireshark to exit when capturing is
+          complete. It can be used with the <command>-c</command> option.
+          It must be used in conjunction with the
+          <command>-i</command> and <command>-w</command> options.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-r &lt;infile></command></term>
+      <listitem>
+        <para>
+          This option provides the name of a capture file for Wireshark
+          to read and display. This capture file can be in one of the
+          formats Wireshark understands.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-R &lt;read (display) filter></command></term>
+      <listitem>
+        <para>
+          This option specifies a display filter to be applied when
+          reading packets from a capture file. The syntax of this
+          filter is that of the display filters discussed in
+          <xref linkend="ChWorkDisplayFilterSection"/>.  Packets not
+          matching the filter are discarded.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-s &lt;capture snaplen></command></term>
+      <listitem>
+        <para>
+          This option specifies the snapshot length to use when
+          capturing packets. Wireshark will only capture
+          <command>&lt;snaplen></command> bytes of data for each packet.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-S</command></term>
+      <listitem>
+        <para>
+          This option specifies that Wireshark will display packets as
+          it captures them. This is done by capturing in one process
+          and displaying them in a separate process. This is the same
+          as "Update list of packets in real time" in the Capture Options
+          dialog box.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>-t &lt;time stamp format></command></term>
+      <listitem>
+        <para>
+          This option sets the format of packet timestamps that are
+          displayed in the packet list window.  The format can be one of:
+          <itemizedlist>
+        <listitem>
+          <para>
+            <command>r</command> relative, which specifies timestamps are
+            displayed relative to the first packet captured.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>a</command> absolute, which specifies that actual times
+            be displayed for all packets.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>ad</command> absolute with date, which specifies that
+            actual dates and times be displayed for all packets.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>d</command> delta, which specifies that timestamps
+            are relative to the previous packet.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>e</command> epoch, which specifies that timestamps
+            are seconds since epoch (Jan 1, 1970 00:00:00)
+          </para>
+        </listitem>
+          </itemizedlist>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-v</command></term>
+      <listitem>
+        <para>
+          The <command>-v</command> option requests
+          Wireshark to print out its version information and exit.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-w &lt;savefile></command></term>
+      <listitem>
+        <para>
+          This option sets the name of the <command>savefile</command>
+          to be used when saving a capture file.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-y &lt;capture link type></command></term>
+      <listitem>
+        <para>
+        If a capture is started from the command line with -k, set the data
+        link type to use while capturing packets. The values reported by -L
+        are the values that can be used.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-X &lt;eXtension option></command></term>
+      <listitem>
+        <para>
         Specify an option to be passed to a TShark module. The eXtension
         option is in the form extension_key:value, where extension_key can
         be:
@@ -585,17 +585,17 @@ standard libpcap format.
         <para>
         <command>lua_script</command>:lua_script_filename; Tells Wireshark to load the given script in addition to the default Lua scripts.
         </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>-z &lt;statistics-string></command></term>
-	  <listitem>
-	    <para>
-		Get Wireshark to collect various types of statistics and display the
-		result in a window that updates in semi-real time.
-		XXX - add more details here!
-		</para>
-	  </listitem>
-	</varlistentry>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>-z &lt;statistics-string></command></term>
+      <listitem>
+        <para>
+        Get Wireshark to collect various types of statistics and display the
+        result in a window that updates in semi-real time.
+        XXX - add more details here!
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </para>
   </section>
@@ -610,9 +610,9 @@ standard libpcap format.
     <tip>
       <title>Tip!</title>
       <para>
-	  You will find a lot of Coloring Rule examples at the <command>Wireshark
-	  Wiki Coloring Rules page</command> at <ulink
-	  url="&WiresharkWikiColoringRulesPage;">&WiresharkWikiColoringRulesPage;</ulink>.
+      You will find a lot of Coloring Rule examples at the <command>Wireshark
+      Wiki Coloring Rules page</command> at <ulink
+      url="&WiresharkWikiColoringRulesPage;">&WiresharkWikiColoringRulesPage;</ulink>.
       </para>
     </tip>
     <para>
@@ -645,18 +645,18 @@ standard libpcap format.
       color filters installed already.
     </para>
     <note><title>Note!</title>
-	<para>
+    <para>
           You will need to carefully select the order the coloring rules are listed
           as they are applied in order from top to bottom.
-	  So, more specific rules need to be listed before more general rules.
-	  For example, if you have a color rule for UDP before the one for DNS,
-	  the color rule for DNS will never be applied (as DNS uses UDP, so the
-	  UDP rule will match first).
-	</para>
+      So, more specific rules need to be listed before more general rules.
+      For example, if you have a color rule for UDP before the one for DNS,
+      the color rule for DNS will never be applied (as DNS uses UDP, so the
+      UDP rule will match first).
+    </para>
     </note>
     <para>
-	  If this is the first time you have used Coloring Rules, click on the New
-	  button which will bring up the Edit color filter dialog box as shown in
+      If this is the first time you have used Coloring Rules, click on the New
+      button which will bring up the Edit color filter dialog box as shown in
       <xref linkend="ChCustEditColorDialog"/>.
     </para>
     <figure id="ChCustEditColorDialog">
@@ -667,16 +667,16 @@ standard libpcap format.
       In the Edit Color dialog box, simply enter a name for the color filter,
       and enter a filter string in the Filter text field.
       <xref linkend="ChCustEditColorDialog"/> shows the values
-	<command>arp</command> and <command>arp</command> which means that
-	the name of the color filter is <command>arp</command> and the filter
-	will select protocols of type <command>arp</command>.  Once you have
-	entered these values, you can choose a foreground and background
-	color for packets that match the filter expression.  Click on
-	<command>Foreground color...</command> or
-	<command>Background color...</command> to achieve this and
-	Wireshark will pop up the Choose foreground/background color for
-	protocol dialog box as shown in
-	<xref linkend="ChCustChooseColorDialog"/>.
+    <command>arp</command> and <command>arp</command> which means that
+    the name of the color filter is <command>arp</command> and the filter
+    will select protocols of type <command>arp</command>.  Once you have
+    entered these values, you can choose a foreground and background
+    color for packets that match the filter expression.  Click on
+    <command>Foreground color...</command> or
+    <command>Background color...</command> to achieve this and
+    Wireshark will pop up the Choose foreground/background color for
+    protocol dialog box as shown in
+    <xref linkend="ChCustChooseColorDialog"/>.
     </para>
     <figure id="ChCustChooseColorDialog">
       <title>The "Choose color" dialog box</title>
@@ -688,20 +688,20 @@ standard libpcap format.
     <note>
       <title>Note!</title>
       <para>
-	You must select a color in the colorbar next to the colorwheel to
-	load values into the RGB values. Alternatively, you can set the
-	values to select the color you want.
+    You must select a color in the colorbar next to the colorwheel to
+    load values into the RGB values. Alternatively, you can set the
+    values to select the color you want.
       </para>
     </note>
     <para>
       <xref linkend="ChCustColorFilterMany"/> shows an example of several color
-	filters being used in Wireshark. You may not like the color choices,
-	however, feel free to choose your own.
+    filters being used in Wireshark. You may not like the color choices,
+    however, feel free to choose your own.
     </para>
     <para>
-	If you are uncertain which coloring rule actually took place for a
-	specific packet, have a look at the [Coloring Rule Name: ...] and
-	[Coloring Rule String: ...] fields.
+    If you are uncertain which coloring rule actually took place for a
+    specific packet, have a look at the [Coloring Rule Name: ...] and
+    [Coloring Rule String: ...] fields.
     </para>
     <figure id="ChCustColorFilterMany">
       <title>Using color filters with Wireshark</title>
@@ -710,44 +710,44 @@ standard libpcap format.
   </section>
 
   <section id="ChCustProtocolDissectionSection">
-	<title>Control Protocol dissection</title>
-	<para>
-		The user can control how protocols are dissected.
-	</para>
-	<para>
-		Each protocol has its own dissector, so dissecting a complete packet will
-		typically involve several dissectors. As Wireshark tries to find the
-		right dissector for each packet (using static "routes" and heuristics
-		"guessing"), it might choose the wrong dissector in your specific
-		case. For example, Wireshark won't know if you use a common protocol
-		on an uncommon TCP port, e.g. using HTTP on TCP port 800 instead of
-		the standard port 80.
-	</para>
-	<para>
-		There are two ways to control the relations between protocol
-		dissectors: disable a protocol dissector completely or temporarily
-		divert the way Wireshark calls the dissectors.
-	</para>
-	<section id="ChAdvEnabledProtocols"><title>The "Enabled Protocols" dialog
-	box</title>
-	<para>
-		The Enabled Protocols dialog box lets you enable or
-		disable specific protocols; all protocols are enabled by default.
-		When a protocol is disabled, Wireshark stops processing a packet
-		whenever that protocol is encountered.
-	</para>
-	<note><title>Note!</title>
-		<para>
-		Disabling a protocol will prevent information about higher-layer
-		protocols from being displayed.  For example,
-		suppose you disabled the IP protocol and selected
-		a packet containing Ethernet, IP, TCP, and HTTP
-		information.  The Ethernet information would be
-		displayed, but the IP, TCP and HTTP information
-		would not - disabling IP would prevent it and
-		the other protocols from being displayed.
-		</para>
-	</note>
+    <title>Control Protocol dissection</title>
+    <para>
+        The user can control how protocols are dissected.
+    </para>
+    <para>
+        Each protocol has its own dissector, so dissecting a complete packet will
+        typically involve several dissectors. As Wireshark tries to find the
+        right dissector for each packet (using static "routes" and heuristics
+        "guessing"), it might choose the wrong dissector in your specific
+        case. For example, Wireshark won't know if you use a common protocol
+        on an uncommon TCP port, e.g. using HTTP on TCP port 800 instead of
+        the standard port 80.
+    </para>
+    <para>
+        There are two ways to control the relations between protocol
+        dissectors: disable a protocol dissector completely or temporarily
+        divert the way Wireshark calls the dissectors.
+    </para>
+    <section id="ChAdvEnabledProtocols"><title>The "Enabled Protocols" dialog
+    box</title>
+    <para>
+        The Enabled Protocols dialog box lets you enable or
+        disable specific protocols; all protocols are enabled by default.
+        When a protocol is disabled, Wireshark stops processing a packet
+        whenever that protocol is encountered.
+    </para>
+    <note><title>Note!</title>
+        <para>
+        Disabling a protocol will prevent information about higher-layer
+        protocols from being displayed.  For example,
+        suppose you disabled the IP protocol and selected
+        a packet containing Ethernet, IP, TCP, and HTTP
+        information.  The Ethernet information would be
+        displayed, but the IP, TCP and HTTP information
+        would not - disabling IP would prevent it and
+        the other protocols from being displayed.
+        </para>
+    </note>
         <para>
           To enable/disable protocols select the <command>Enabled Protocols...</command>
           item from the <command>Analyze</command> menu; Wireshark will pop up the "Enabled Protocols"
@@ -757,72 +757,72 @@ standard libpcap format.
       <title>The "Enabled Protocols" dialog box</title>
       <graphic entityref="WiresharkEnabledProtocols" format="PNG"/>
     </figure>
-	<para>
-		To disable or enable a protocol, simply click on it using the
-		mouse or press the space bar when the protocol is highlighted.
+    <para>
+        To disable or enable a protocol, simply click on it using the
+        mouse or press the space bar when the protocol is highlighted.
                 Note that typing the first few letters
                 of the protocol name when the Enabled Protocols dialog box is active
                 will temporarily open a search text box and
                 automatically select the first matching protocol name (if it exists).
-	</para>
-	<warning><title>Warning!</title>
-		<para>
-		You have to use the Save button to save your settings. The OK or Apply
-		buttons will not save your changes permanently, so they will be lost
-		when Wireshark is closed.
-		</para>
-	</warning>
+    </para>
+    <warning><title>Warning!</title>
+        <para>
+        You have to use the Save button to save your settings. The OK or Apply
+        buttons will not save your changes permanently, so they will be lost
+        when Wireshark is closed.
+        </para>
+    </warning>
     <para>
       You can choose from the following actions:
       <orderedlist>
-	<listitem>
-	  <para>
-	    <command>Enable All</command>: Enable all protocols in the list.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Disable All</command>: Disable all protocols in the list.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Invert</command>: Toggle the state of all protocols in the
-		list.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>OK</command>: Apply the changes and close the dialog box.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Apply</command>: Apply the changes and keep the dialog box
-		open.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Save</command>: Save the settings to the disabled_protos, see
-		<xref linkend="AppFiles"/> for details.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Cancel</command>: Cancel the changes and close the dialog box.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        <command>Enable All</command>: Enable all protocols in the list.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Disable All</command>: Disable all protocols in the list.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Invert</command>: Toggle the state of all protocols in the
+        list.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>OK</command>: Apply the changes and close the dialog box.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Apply</command>: Apply the changes and keep the dialog box
+        open.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Save</command>: Save the settings to the disabled_protos, see
+        <xref linkend="AppFiles"/> for details.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Cancel</command>: Cancel the changes and close the dialog box.
+      </para>
+    </listitem>
       </orderedlist>
     </para>
-	</section>
+    </section>
 
     <section id="ChAdvDecodeAs"><title>User Specified Decodes</title>
-	<para>
-		The "Decode As" functionality let you temporarily divert specific
-		protocol dissections. This might be useful for example, if you do some
-		uncommon experiments on your network.
-	</para>
+    <para>
+        The "Decode As" functionality let you temporarily divert specific
+        protocol dissections. This might be useful for example, if you do some
+        uncommon experiments on your network.
+    </para>
         <para>
           Decode As is accessed by selecting the <command>Decode As...</command> item from
           the <command>Analyze</command> menu; Wireshark will pop up the "Decode As"
@@ -833,88 +833,88 @@ standard libpcap format.
       <title>The "Decode As" dialog box</title>
       <graphic scale="100" entityref="WiresharkDecodeAs" format="PNG"/>
     </figure>
-	The content of this dialog box depends on the selected packet when it
-	was opened.
-	<warning><title>Warning!</title>
-		<para>
-		These settings will be lost if you quit Wireshark or change profile,
-		unless you save the entries in the <command>Show User Specified Decodes...</command>
-		windows (<xref linkend="ChAdvDecodeAsShow"/>).
-		</para>
-	</warning>
+    The content of this dialog box depends on the selected packet when it
+    was opened.
+    <warning><title>Warning!</title>
+        <para>
+        These settings will be lost if you quit Wireshark or change profile,
+        unless you save the entries in the <command>Show User Specified Decodes...</command>
+        windows (<xref linkend="ChAdvDecodeAsShow"/>).
+        </para>
+    </warning>
       <orderedlist>
-	<listitem>
-	  <para>
-	    <command>Decode</command>: Decode packets the selected way.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Do not decode</command>: Do not decode packets the selected
-		way.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Link/Network/Transport</command>: Specify the network layer
-		at which "Decode As" should take place. Which of these pages are
-		available depends on the content of the selected packet when this
-		dialog box is opened.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Show Current</command>: Open a dialog box showing the
-		current list of user specified decodes.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>OK</command>: Apply the currently selected decode and close
-		the dialog box.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Apply</command>: Apply the currently selected decode and keep
-		the dialog box open.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Cancel</command>: Cancel the changes and close the dialog box.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        <command>Decode</command>: Decode packets the selected way.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Do not decode</command>: Do not decode packets the selected
+        way.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Link/Network/Transport</command>: Specify the network layer
+        at which "Decode As" should take place. Which of these pages are
+        available depends on the content of the selected packet when this
+        dialog box is opened.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Show Current</command>: Open a dialog box showing the
+        current list of user specified decodes.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>OK</command>: Apply the currently selected decode and close
+        the dialog box.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Apply</command>: Apply the currently selected decode and keep
+        the dialog box open.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Cancel</command>: Cancel the changes and close the dialog box.
+      </para>
+    </listitem>
       </orderedlist>
-	</para>
-	</section>
+    </para>
+    </section>
 
     <section id="ChAdvDecodeAsShow"><title>Show User Specified Decodes</title>
     <para>
-	This dialog box shows the currently active user specified decodes. These entries
-	can be saved into current profile for later session.
+    This dialog box shows the currently active user specified decodes. These entries
+    can be saved into current profile for later session.
     <figure id="ChAdvDecodeAsShowFig">
       <title>The "Decode As: Show" dialog box</title>
       <graphic entityref="WiresharkDecodeAsShow" format="PNG"/>
     </figure>
       <orderedlist>
-	<listitem>
-	  <para>
-	    <command>OK</command>: Close this dialog box.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Save</command>: Save the entries in the table into current profile.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Clear</command>: Removes all user specified decodes without updating the profile.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        <command>OK</command>: Close this dialog box.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Save</command>: Save the entries in the table into current profile.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Clear</command>: Removes all user specified decodes without updating the profile.
+      </para>
+    </listitem>
       </orderedlist>
-	</para>
+    </para>
   </section>
   </section>
 
@@ -925,49 +925,49 @@ standard libpcap format.
       the <command>Edit</command> menu; and Wireshark
       will pop up the Preferences dialog box as shown in
       <xref linkend="ChCustGUIPrefPage"/>, with the "User Interface" page as
-	  default. On the left side is a tree where you can select the page to be
-	  shown.
-	  <note><title>Note!</title>
-	  <para>
-	  Preference settings are added frequently. For a recent explanation of
-	  the preference pages and their settings have a look at the
-	  <command>Wireshark Wiki Preferences page</command> at <ulink
-	  url="&WiresharkWikiPreferencesPage;">&WiresharkWikiPreferencesPage;</ulink>.
+      default. On the left side is a tree where you can select the page to be
+      shown.
+      <note><title>Note!</title>
+      <para>
+      Preference settings are added frequently. For a recent explanation of
+      the preference pages and their settings have a look at the
+      <command>Wireshark Wiki Preferences page</command> at <ulink
+      url="&WiresharkWikiPreferencesPage;">&WiresharkWikiPreferencesPage;</ulink>.
       </para>
       </note>
-	  <warning>
-		<title>Warning!</title>
-		<para>
-		The OK or Apply button will not save the preference settings,
-		you'll have to save the settings by clicking the Save button.
-		</para>
-	  </warning>
-	<itemizedlist>
-		<listitem>
-		  <para>
-	  		The <command>OK</command> button will apply the preferences
-			settings and close the dialog.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-	  		The <command>Apply</command> button will apply the preferences
-			settings and keep the dialog open.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-	  		The <command>Save</command> button will apply the preferences
-			settings, save the settings on the hard disk and keep the dialog open.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-	  		The <command>Cancel</command> button will restore all preferences
-			settings to the last saved state.
-		  </para>
-		</listitem>
-	</itemizedlist>
+      <warning>
+        <title>Warning!</title>
+        <para>
+        The OK or Apply button will not save the preference settings,
+        you'll have to save the settings by clicking the Save button.
+        </para>
+      </warning>
+    <itemizedlist>
+        <listitem>
+          <para>
+              The <command>OK</command> button will apply the preferences
+            settings and close the dialog.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+              The <command>Apply</command> button will apply the preferences
+            settings and keep the dialog open.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+              The <command>Save</command> button will apply the preferences
+            settings, save the settings on the hard disk and keep the dialog open.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+              The <command>Cancel</command> button will restore all preferences
+            settings to the last saved state.
+          </para>
+        </listitem>
+    </itemizedlist>
     </para>
     <figure id="ChCustGUIPrefPage">
       <title>The preferences dialog box</title>
@@ -989,26 +989,26 @@ standard libpcap format.
     <para>Each row contains options for each interface available on your computer.</para>
     <itemizedlist>
       <listitem>
-	<para><command>Device</command>: the device name provided by the operating system.</para>
+    <para><command>Device</command>: the device name provided by the operating system.</para>
       </listitem>
       <listitem>
-	<para><command>Description</command>: provided by the operating system.</para>
+    <para><command>Description</command>: provided by the operating system.</para>
       </listitem>
       <listitem>
-	<para><command>Default link-layer</command>: each interface may provide several
-	link-layer header types. The default link-layer chosen here is the one used when you
-	first start Wireshark.  It is also possible to change this value in
-	<xref linkend="ChCapCaptureOptions"/> when you start a capture.
-	For a detailed description, see <xref linkend="ChCapLinkLayerHeader"/>.</para>
+    <para><command>Default link-layer</command>: each interface may provide several
+    link-layer header types. The default link-layer chosen here is the one used when you
+    first start Wireshark.  It is also possible to change this value in
+    <xref linkend="ChCapCaptureOptions"/> when you start a capture.
+    For a detailed description, see <xref linkend="ChCapLinkLayerHeader"/>.</para>
       </listitem>
       <listitem>
-	<para><command>Comment</command>: a user provided description of the interface.
-	This comment will be used as a description instead of the operating system
-	description.</para>
+    <para><command>Comment</command>: a user provided description of the interface.
+    This comment will be used as a description instead of the operating system
+    description.</para>
       </listitem>
       <listitem>
-	<para><command>Hide?</command>: enable this option to hide the interface from other
-	parts of the program.</para>
+    <para><command>Hide?</command>: enable this option to hide the interface from other
+    parts of the program.</para>
       </listitem>
     </itemizedlist>
     </section>
@@ -1026,129 +1026,129 @@ standard libpcap format.
     <para>
       Configuration files stored in the Profiles:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    Preferences (preferences) (<xref linkend="ChCustPreferencesSection"/>)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Capture Filters (cfilters) (<xref linkend="ChWorkDefineFilterSection"/>)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Display Filters (dfilters) (<xref linkend="ChWorkDefineFilterSection"/>)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Coloring Rules (colorfilters) (<xref linkend="ChCustColorizationSection"/>)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Disabled Protocols (disabled_protos) (<xref linkend="ChAdvEnabledProtocols"/>)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    User Accessible Tables:
-	    <itemizedlist>
-	      <listitem>
-		<para>
-		  Custom HTTP headers (custom_http_header_fields)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  Custom IMF headers (imf_header_fields)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  Custom LDAP AttributeValue types (custom_ldap_attribute_types)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  Display Filter Macros (dfilter_macros) (<xref linkend="ChDisplayFilterMacrosSection"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  ESS Category Attributes (ess_category_attributes) (<xref linkend="ChEssCategoryAttributes"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  GeoIP Database Paths (geoip_db_paths) (<xref linkend="ChGeoIPDbPaths"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  K12 Protocols (k12_protos) (<xref linkend="ChK12ProtocolsSection"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  Object Identifier Names and Associated Syntaxes (<xref linkend="ChObjectIdentifiers"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  PRES Users Context List (pres_context_list) (<xref linkend="ChPresContextList"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  SCCP Users Table (sccp_users) (<xref linkend="ChSccpUsers"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  SNMP Enterprise Specific Trap Types (snmp_specific_traps) (<xref linkend="ChSNMPEnterpriseSpecificTrapTypes"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  SNMP Users (snmp_users) (<xref linkend="ChSNMPUsersSection"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  User DLTs Table (user_dlts) (<xref linkend="ChUserDLTsSection"/>)
-		</para>
-	      </listitem>
-	      <listitem>
-		<para>
-		  IKEv2 decryption table (ikev2_decryption_table) (<xref linkend="ChIKEv2DecryptionSection"/>)
-		</para>
-	      </listitem>
-	    </itemizedlist>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Changed dissector assignments (decode_as_entries), which can be set in <command>Decode As...</command>
-	    dialog box (<xref linkend="ChAdvDecodeAs"/>), and further saved in the <command>User Specified Decodes...</command>
-	    window (<xref linkend="ChAdvDecodeAsShow"/>).
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Some recent settings (recent), such as pane sizes in the Main window
-	    (<xref linkend="ChUseMainWindowSection"/>), column widths in the packet list
-	    (<xref linkend="ChUsePacketListPaneSection"/>), all selections in the "View" menu
-	    (<xref linkend="ChUseViewMenuSection"/>) and the last directory navigated to in the
-	    File Open dialog.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Preferences (preferences) (<xref linkend="ChCustPreferencesSection"/>)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Capture Filters (cfilters) (<xref linkend="ChWorkDefineFilterSection"/>)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Display Filters (dfilters) (<xref linkend="ChWorkDefineFilterSection"/>)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Coloring Rules (colorfilters) (<xref linkend="ChCustColorizationSection"/>)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Disabled Protocols (disabled_protos) (<xref linkend="ChAdvEnabledProtocols"/>)
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        User Accessible Tables:
+        <itemizedlist>
+          <listitem>
+        <para>
+          Custom HTTP headers (custom_http_header_fields)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          Custom IMF headers (imf_header_fields)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          Custom LDAP AttributeValue types (custom_ldap_attribute_types)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          Display Filter Macros (dfilter_macros) (<xref linkend="ChDisplayFilterMacrosSection"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          ESS Category Attributes (ess_category_attributes) (<xref linkend="ChEssCategoryAttributes"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          GeoIP Database Paths (geoip_db_paths) (<xref linkend="ChGeoIPDbPaths"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          K12 Protocols (k12_protos) (<xref linkend="ChK12ProtocolsSection"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          Object Identifier Names and Associated Syntaxes (<xref linkend="ChObjectIdentifiers"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          PRES Users Context List (pres_context_list) (<xref linkend="ChPresContextList"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          SCCP Users Table (sccp_users) (<xref linkend="ChSccpUsers"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          SNMP Enterprise Specific Trap Types (snmp_specific_traps) (<xref linkend="ChSNMPEnterpriseSpecificTrapTypes"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          SNMP Users (snmp_users) (<xref linkend="ChSNMPUsersSection"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          User DLTs Table (user_dlts) (<xref linkend="ChUserDLTsSection"/>)
+        </para>
+          </listitem>
+          <listitem>
+        <para>
+          IKEv2 decryption table (ikev2_decryption_table) (<xref linkend="ChIKEv2DecryptionSection"/>)
+        </para>
+          </listitem>
+        </itemizedlist>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Changed dissector assignments (decode_as_entries), which can be set in <command>Decode As...</command>
+        dialog box (<xref linkend="ChAdvDecodeAs"/>), and further saved in the <command>User Specified Decodes...</command>
+        window (<xref linkend="ChAdvDecodeAsShow"/>).
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Some recent settings (recent), such as pane sizes in the Main window
+        (<xref linkend="ChUseMainWindowSection"/>), column widths in the packet list
+        (<xref linkend="ChUsePacketListPaneSection"/>), all selections in the "View" menu
+        (<xref linkend="ChUseViewMenuSection"/>) and the last directory navigated to in the
+        File Open dialog.
+      </para>
+    </listitem>
       </itemizedlist>
       <note><title>Other configurations</title>
       <para>
-	All other configurations are stored in the personal configuration folder,
-	and are common to all profiles.
+    All other configurations are stored in the personal configuration folder,
+    and are common to all profiles.
       </para>
       </note>
     </para>
@@ -1158,92 +1158,92 @@ standard libpcap format.
     </figure>
     <para>
       <variablelist>
-	<varlistentry><term><command>New</command></term>
-	<listitem>
-	  <para>
-	    This button adds a new profile to the profiles list.  The name of the
-	    created profile is "New profile" and can be changed in the Properties field.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Copy</command></term>
-	<listitem>
-	  <para>
-	    This button adds a new profile to the profiles list, copying all configuration
-	    from the profile currently selected in the list.  The name of the created
-	    profile is the same as the copied profile, with the text "(copy)" applied.
-	    The name can be changed in the Properties field.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Delete</command></term>
-	<listitem>
-	  <para>
-	    This button deletes the selected profile, including all configuration
-	    files used in this profile.  It is not possible to delete the "Default" profile.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Configuration Profiles</command></term>
-	<listitem>
-	  <para>
-	    You can select a configuration profile from this list (which will fill
-	    in the profile name in the fields down at the bottom of the dialog box).
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Profile name:</command></term>
-	<listitem>
-	  <para>
-	    You can change the name of the currently selected profile here.
-	  </para>
-	  <note><title>Used as a folder name</title>
-	  <para>
-	    The profile name will be used as a folder name in the configured
-	    "Personal configurations" folder. If adding multiple profiles with the
-	    same name, only one profile will be created.
-	  </para>
-	  </note>
-	  <note><title>Illegal characters</title>
-	  <para>
-	    On Windows the profile name cannot start or end with a period (.), and cannot contain
-	    any of the following characters: <command>\ / : * ? " &lt; &gt; |</command>
-	  </para>
-	  <para>
-	    On Unix the profile name cannot contain the '<command>/</command>' character.
-	  </para>
-	  </note>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>OK</command></term>
-	<listitem>
-	  <para>
-	    This button saves all changes, applies the selected profile and closes the dialog.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Apply</command></term>
-	<listitem>
-	  <para>
-	    This button saves all changes, applies the selected profile and keeps the dialog open.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Cancel</command></term>
-	<listitem>
-	  <para>
-	    Close this dialog. This will discard unsaved settings, new profiles will not be added
-	    and deleted profiles will not be deleted.
-	  </para>
-	</listitem>
-	</varlistentry>
-	<varlistentry><term><command>Help</command></term>
-	<listitem>
-	  <para>
-	    Show this help page.
-	  </para>
-	</listitem>
-	</varlistentry>
+    <varlistentry><term><command>New</command></term>
+    <listitem>
+      <para>
+        This button adds a new profile to the profiles list.  The name of the
+        created profile is "New profile" and can be changed in the Properties field.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Copy</command></term>
+    <listitem>
+      <para>
+        This button adds a new profile to the profiles list, copying all configuration
+        from the profile currently selected in the list.  The name of the created
+        profile is the same as the copied profile, with the text "(copy)" applied.
+        The name can be changed in the Properties field.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Delete</command></term>
+    <listitem>
+      <para>
+        This button deletes the selected profile, including all configuration
+        files used in this profile.  It is not possible to delete the "Default" profile.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Configuration Profiles</command></term>
+    <listitem>
+      <para>
+        You can select a configuration profile from this list (which will fill
+        in the profile name in the fields down at the bottom of the dialog box).
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Profile name:</command></term>
+    <listitem>
+      <para>
+        You can change the name of the currently selected profile here.
+      </para>
+      <note><title>Used as a folder name</title>
+      <para>
+        The profile name will be used as a folder name in the configured
+        "Personal configurations" folder. If adding multiple profiles with the
+        same name, only one profile will be created.
+      </para>
+      </note>
+      <note><title>Illegal characters</title>
+      <para>
+        On Windows the profile name cannot start or end with a period (.), and cannot contain
+        any of the following characters: <command>\ / : * ? " &lt; &gt; |</command>
+      </para>
+      <para>
+        On Unix the profile name cannot contain the '<command>/</command>' character.
+      </para>
+      </note>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>OK</command></term>
+    <listitem>
+      <para>
+        This button saves all changes, applies the selected profile and closes the dialog.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Apply</command></term>
+    <listitem>
+      <para>
+        This button saves all changes, applies the selected profile and keeps the dialog open.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Cancel</command></term>
+    <listitem>
+      <para>
+        Close this dialog. This will discard unsaved settings, new profiles will not be added
+        and deleted profiles will not be deleted.
+      </para>
+    </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Help</command></term>
+    <listitem>
+      <para>
+        Show this help page.
+      </para>
+    </listitem>
+    </varlistentry>
       </variablelist>
     </para>
   </section>
@@ -1257,33 +1257,33 @@ standard libpcap format.
 
   <section id="ChDisplayFilterMacrosSection"><title>Display Filter Macros</title>
     <para>
-	Display Filter Macros are a mechanism to create shortcuts for complex filters. For example defining a
-	display filter macro named <command>tcp_conv</command> whose text is
-	<command> ( (ip.src == $1 and ip.dst == $2 and tcp.srcport == $3 and tcp.dstport == $4) or
-	(ip.src == $2 and ip.dst == $1 and tcp.srcport == $4 and tcp.dstport == $3) ) </command>
-	would allow to use a display filter like <command>${tcp_conv:10.1.1.2;10.1.1.3;1200;1400}</command>
-	instead of typing the whole filter.
+    Display Filter Macros are a mechanism to create shortcuts for complex filters. For example defining a
+    display filter macro named <command>tcp_conv</command> whose text is
+    <command> ( (ip.src == $1 and ip.dst == $2 and tcp.srcport == $3 and tcp.dstport == $4) or
+    (ip.src == $2 and ip.dst == $1 and tcp.srcport == $4 and tcp.dstport == $3) ) </command>
+    would allow to use a display filter like <command>${tcp_conv:10.1.1.2;10.1.1.3;1200;1400}</command>
+    instead of typing the whole filter.
       </para>
     <para>
-	Display Filter Macros can be managed with a <xref linkend="ChUserTable"/> by selecting
-	<command>Analyze &#x2192; Display Filter Macros</command> from the menu.
-	The User Table has  the following fields
+    Display Filter Macros can be managed with a <xref linkend="ChUserTable"/> by selecting
+    <command>Analyze &#x2192; Display Filter Macros</command> from the menu.
+    The User Table has  the following fields
       </para>
             <variablelist>
-	  <varlistentry><term><command>Name</command></term>
-	  <listitem>
-		<para>
-			The name of the macro.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Text</command></term>
-	  <listitem>
-		<para>
-			The replacement text for the macro it uses $1, $2, $3, ... as the input arguments.
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>Name</command></term>
+      <listitem>
+        <para>
+            The name of the macro.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Text</command></term>
+      <listitem>
+        <para>
+            The replacement text for the macro it uses $1, $2, $3, ... as the input arguments.
+        </para>
+      </listitem>
+      </varlistentry>
       </variablelist>
 
   </section>
@@ -1358,72 +1358,72 @@ standard libpcap format.
          This table is handled by an <xref linkend="ChUserTable"/> with the following fields.
       </para>
       <variablelist>
-	  <varlistentry><term><command>Initiator's SPI</command></term>
-	  <listitem>
-		<para>
-			Initiator's SPI of the IKE_SA. This field takes hexadecimal string without "0x" prefix
+      <varlistentry><term><command>Initiator's SPI</command></term>
+      <listitem>
+        <para>
+            Initiator's SPI of the IKE_SA. This field takes hexadecimal string without "0x" prefix
                         and the length must be 16 hex chars (represents 8 octets).
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Responder's SPI</command></term>
-	  <listitem>
-		<para>
-			Responder's SPI of the IKE_SA. This field takes hexadecimal string without "0x" prefix
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Responder's SPI</command></term>
+      <listitem>
+        <para>
+            Responder's SPI of the IKE_SA. This field takes hexadecimal string without "0x" prefix
                         and the length must be 16 hex chars (represents 8 octets).
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>SK_ei</command></term>
-	  <listitem>
-		<para>
-			Key used to encrypt/decrypt IKEv2 packets from initiator to responder.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>SK_ei</command></term>
+      <listitem>
+        <para>
+            Key used to encrypt/decrypt IKEv2 packets from initiator to responder.
                         This field takes hexadecimal string without "0x" prefix and its length
                         must meet the requirement of the encryption algorithm selected.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>SK_er</command></term>
-	  <listitem>
-		<para>
-			Key used to encrypt/decrypt IKEv2 packets from responder to initiator.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>SK_er</command></term>
+      <listitem>
+        <para>
+            Key used to encrypt/decrypt IKEv2 packets from responder to initiator.
                         This field takes hexadecimal string without "0x" prefix and its length
                         must meet the requirement of the encryption algorithm selected.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  	  <varlistentry><term><command>Encryption Algorithm</command></term>
-	  <listitem>
-		<para>
-			Encryption algorithm of the IKE_SA.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>SK_ai</command></term>
-	  <listitem>
-		<para>
-			Key used to calculate Integrity Checksum Data for IKEv2 packets from responder to initiator.
+        </para>
+      </listitem>
+      </varlistentry>
+            <varlistentry><term><command>Encryption Algorithm</command></term>
+      <listitem>
+        <para>
+            Encryption algorithm of the IKE_SA.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>SK_ai</command></term>
+      <listitem>
+        <para>
+            Key used to calculate Integrity Checksum Data for IKEv2 packets from responder to initiator.
                         This field takes hexadecimal string without "0x" prefix and its length
                         must meet the requirement of the integrity algorithm selected.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>SK_ar</command></term>
-	  <listitem>
-		<para>
-			Key used to calculate Integrity Checksum Data for IKEv2 packets from initiator to responder.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>SK_ar</command></term>
+      <listitem>
+        <para>
+            Key used to calculate Integrity Checksum Data for IKEv2 packets from initiator to responder.
                         This field takes hexadecimal string without "0x" prefix and its length
                         must meet the requirement of the integrity algorithm selected.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Integrity Algorithm</command></term>
-	  <listitem>
-		<para>
-			Integrity algorithm of the IKE_SA.
-		</para>
-	  </listitem>
-	  </varlistentry>
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Integrity Algorithm</command></term>
+      <listitem>
+        <para>
+            Integrity algorithm of the IKE_SA.
+        </para>
+      </listitem>
+      </varlistentry>
 
       </variablelist>
   </section>
@@ -1445,21 +1445,21 @@ standard libpcap format.
       <varlistentry><term><command>OID</command></term>
       <listitem>
           <para>
-	    The string representation of the Object Identifier e.g. "2.5.4.6".
+        The string representation of the Object Identifier e.g. "2.5.4.6".
           </para>
       </listitem>
       </varlistentry>
       <varlistentry><term><command>Name</command></term>
       <listitem>
           <para>
-	    The name that should be displayed by Wireshark when the Object Identifier is dissected e.g. ("c");
+        The name that should be displayed by Wireshark when the Object Identifier is dissected e.g. ("c");
           </para>
       </listitem>
       </varlistentry>
       <varlistentry><term><command>Syntax</command></term>
       <listitem>
           <para>
-	    The syntax of the value associated with the Object Identifier. This must be one of the syntaxes that Wireshark already knows about (e.g. "PrintableString").
+        The syntax of the value associated with the Object Identifier. This must be one of the syntaxes that Wireshark already knows about (e.g. "PrintableString").
           </para>
       </listitem>
       </varlistentry>
@@ -1486,7 +1486,7 @@ standard libpcap format.
       <listitem>
           <para>
             The object identifier representing the abstract syntax name, which defines the protocol that is
-	    carried over this association.
+        carried over this association.
           </para>
       </listitem>
       </varlistentry>
@@ -1502,37 +1502,37 @@ standard libpcap format.
          This table is handled by an <xref linkend="ChUserTable"/> with the following fields.
       </para>
       <variablelist>
-	  <varlistentry><term><command>Network Indicator</command></term>
-	  <listitem>
-		<para>
-			An Integer representing the network indicator for which this association is valid.
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>Network Indicator</command></term>
+      <listitem>
+        <para>
+            An Integer representing the network indicator for which this association is valid.
+        </para>
+      </listitem>
+      </varlistentry>
 
-	  <varlistentry><term><command>Called DPCs</command></term>
-	  <listitem>
-		<para>
-			An range of integers representing the dpcs for which this association is valid.
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>Called DPCs</command></term>
+      <listitem>
+        <para>
+            An range of integers representing the dpcs for which this association is valid.
+        </para>
+      </listitem>
+      </varlistentry>
 
-	  <varlistentry><term><command>Called SSNs</command></term>
-	  <listitem>
-		<para>
-			An range of integers representing the ssns for which this association is valid.
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>Called SSNs</command></term>
+      <listitem>
+        <para>
+            An range of integers representing the ssns for which this association is valid.
+        </para>
+      </listitem>
+      </varlistentry>
 
-	  <varlistentry><term><command>User protocol</command></term>
-	  <listitem>
-		<para>
-			The protocol that is carried over this association
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>User protocol</command></term>
+      <listitem>
+        <para>
+            The protocol that is carried over this association
+        </para>
+      </listitem>
+      </varlistentry>
 
 
       </variablelist>
@@ -1672,31 +1672,31 @@ standard libpcap format.
 
     <section id="ChK12ProtocolsSection"><title>Tektronix K12xx/15 RF5 protocols Table</title>
     <para>
-	The Tektronix K12xx/15 rf5 file format uses helper files (*.stk) to identify the various protocols that are
-	used by a certain interface. Wireshark doesn't read these stk files, it uses a table that helps it identify
-	which lowest layer protocol to use.
+    The Tektronix K12xx/15 rf5 file format uses helper files (*.stk) to identify the various protocols that are
+    used by a certain interface. Wireshark doesn't read these stk files, it uses a table that helps it identify
+    which lowest layer protocol to use.
    </para>
    <para>
          Stk file to protocol matching is handled by an <xref linkend="ChUserTable"/> with the following fields.
       </para>
       <variablelist>
-	  <varlistentry><term><command>Match string</command></term>
-	  <listitem>
-		<para>
-		   A partial match for an stk filename, the first match wins, so if you have a specific case and a
-		   general one the specific one must appear first in the list.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Protocol</command></term>
-	  <listitem>
-		<para>
-			This is the name of the encapsulating protocol (the lowest layer in the packet data) it can be either
-			just the name of the protocol (e.g. mtp2, eth_witoutfcs, sscf-nni ) or the name of the encapsulation
-			protocol and the "application" protocol over it separated by a colon (e.g sscop:sscf-nni, sscop:alcap, sscop:nbap, ...)
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>Match string</command></term>
+      <listitem>
+        <para>
+           A partial match for an stk filename, the first match wins, so if you have a specific case and a
+           general one the specific one must appear first in the list.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Protocol</command></term>
+      <listitem>
+        <para>
+            This is the name of the encapsulating protocol (the lowest layer in the packet data) it can be either
+            just the name of the protocol (e.g. mtp2, eth_witoutfcs, sscf-nni ) or the name of the encapsulation
+            protocol and the "application" protocol over it separated by a colon (e.g sscop:sscf-nni, sscop:alcap, sscop:nbap, ...)
+        </para>
+      </listitem>
+      </varlistentry>
       </variablelist>
   </section>
 
@@ -1708,48 +1708,48 @@ standard libpcap format.
          This table is handled by an <xref linkend="ChUserTable"/> with the following fields.
       </para>
       <variablelist>
-	  <varlistentry><term><command>DLT</command></term>
-	  <listitem>
-		<para>
-			One of the user dlts.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Payload protocol</command></term>
-	  <listitem>
-		<para>
-			This is the name of the payload protocol (the lowest layer in the packet data). (e.g. "eth" for ethernet, "ip" for IPv4)
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Header size</command></term>
-	  <listitem>
-		<para>
-			If there is a header protocol (before the payload protocol) this tells which size this header is. A value of 0 disables the header protocol.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Header protocol</command></term>
-	  <listitem>
-		<para>
-			The name of the header protocol to be used (uses "data" as default).
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  	  <varlistentry><term><command>Trailer size</command></term>
-	  <listitem>
-		<para>
-			If there is a trailer protocol (after the payload protocol) this tells which size this trailer is. A value of 0 disables the trailer protocol.
-		</para>
-	  </listitem>
-	  </varlistentry>
-	  <varlistentry><term><command>Trailer protocol</command></term>
-	  <listitem>
-		<para>
-			The name of the trailer protocol to be used (uses "data" as default).
-		</para>
-	  </listitem>
-	  </varlistentry>
+      <varlistentry><term><command>DLT</command></term>
+      <listitem>
+        <para>
+            One of the user dlts.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Payload protocol</command></term>
+      <listitem>
+        <para>
+            This is the name of the payload protocol (the lowest layer in the packet data). (e.g. "eth" for ethernet, "ip" for IPv4)
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Header size</command></term>
+      <listitem>
+        <para>
+            If there is a header protocol (before the payload protocol) this tells which size this header is. A value of 0 disables the header protocol.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Header protocol</command></term>
+      <listitem>
+        <para>
+            The name of the header protocol to be used (uses "data" as default).
+        </para>
+      </listitem>
+      </varlistentry>
+            <varlistentry><term><command>Trailer size</command></term>
+      <listitem>
+        <para>
+            If there is a trailer protocol (after the payload protocol) this tells which size this trailer is. A value of 0 disables the trailer protocol.
+        </para>
+      </listitem>
+      </varlistentry>
+      <varlistentry><term><command>Trailer protocol</command></term>
+      <listitem>
+        <para>
+            The name of the trailer protocol to be used (uses "data" as default).
+        </para>
+      </listitem>
+      </varlistentry>
 
       </variablelist>
   </section>
diff --git a/docbook/wsug_src/WSUG_chapter_introduction.xml b/docbook/wsug_src/WSUG_chapter_introduction.xml
index 789bcaea9c..903a789be9 100644
--- a/docbook/wsug_src/WSUG_chapter_introduction.xml
+++ b/docbook/wsug_src/WSUG_chapter_introduction.xml
@@ -7,176 +7,176 @@
   <section id="ChIntroWhatIs">
     <title>What is <application>Wireshark?</application></title>
     <para>
-	Wireshark is a network packet analyzer. A network packet
-	analyzer will try to capture network packets and tries to display
-	that packet data as detailed as possible.
+    Wireshark is a network packet analyzer. A network packet
+    analyzer will try to capture network packets and tries to display
+    that packet data as detailed as possible.
     </para>
     <para>
-	You could think of a network packet analyzer as a measuring device used to
-	examine what's going on inside a network cable, just like a voltmeter is
-	used by an electrician to examine what's going on inside an electric cable
-	(but at a higher level, of course).
+    You could think of a network packet analyzer as a measuring device used to
+    examine what's going on inside a network cable, just like a voltmeter is
+    used by an electrician to examine what's going on inside an electric cable
+    (but at a higher level, of course).
     </para>
     <para>
-	In the past, such tools were either very expensive, proprietary, or both.
-	However, with the advent of Wireshark, all that has changed.
+    In the past, such tools were either very expensive, proprietary, or both.
+    However, with the advent of Wireshark, all that has changed.
     </para>
     <para>
-	<application>Wireshark</application> is perhaps one of the best open
-	source packet analyzers available today.
-	</para>
+    <application>Wireshark</application> is perhaps one of the best open
+    source packet analyzers available today.
+    </para>
 
   <section id="ChIntroPurposes"><title>Some intended purposes</title>
-	<para>
-	Here are some examples people use Wireshark for:
+    <para>
+    Here are some examples people use Wireshark for:
       <itemizedlist>
-	<listitem><para>
-	  network administrators use it to <command>troubleshoot network
-	   problems</command>
-	</para></listitem>
-	<listitem><para>
-	  network security engineers use it to <command>examine security
-	  problems</command>
-	</para></listitem>
-	<listitem><para>
-	  developers use it to <command>debug protocol implementations</command>
-	</para></listitem>
-	<listitem><para>
-	  people use it to <command>learn network protocol</command>
-	  internals
-	</para></listitem>
+    <listitem><para>
+      network administrators use it to <command>troubleshoot network
+       problems</command>
+    </para></listitem>
+    <listitem><para>
+      network security engineers use it to <command>examine security
+      problems</command>
+    </para></listitem>
+    <listitem><para>
+      developers use it to <command>debug protocol implementations</command>
+    </para></listitem>
+    <listitem><para>
+      people use it to <command>learn network protocol</command>
+      internals
+    </para></listitem>
       </itemizedlist>
-	  Beside these examples, Wireshark can be helpful in many other situations
-	  too.
-	</para>
+      Beside these examples, Wireshark can be helpful in many other situations
+      too.
+    </para>
   </section>
 
   <section id="ChIntroFeatures"><title>Features</title>
-	<para>
-	The following are some of the many features Wireshark provides:
+    <para>
+    The following are some of the many features Wireshark provides:
       <itemizedlist>
-	<listitem>
-	  <para>Available for <command>UNIX</command> and <command>Windows</command>.</para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Capture</command> live packet data from a network interface.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Display packets with <command>very detailed protocol information</command>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Open and Save</command> packet data captured.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    <command>Import and Export</command> packet data from and to a lot of
-		other capture programs.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Filter packets</command> on many criteria.</para>
-	</listitem>
-	<listitem>
-	  <para><command>Search</command> for packets on many criteria.</para>
-	</listitem>
-	<listitem>
-	  <para><command>Colorize</command> packet display based on filters.</para>
-	</listitem>
-	<listitem>
-	  <para>Create various <command>statistics</command>.</para>
-	</listitem>
-	<listitem>
-	  <para>... and <command>a lot more!</command></para>
-	</listitem>
+    <listitem>
+      <para>Available for <command>UNIX</command> and <command>Windows</command>.</para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Capture</command> live packet data from a network interface.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Display packets with <command>very detailed protocol information</command>.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Open and Save</command> packet data captured.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        <command>Import and Export</command> packet data from and to a lot of
+        other capture programs.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Filter packets</command> on many criteria.</para>
+    </listitem>
+    <listitem>
+      <para><command>Search</command> for packets on many criteria.</para>
+    </listitem>
+    <listitem>
+      <para><command>Colorize</command> packet display based on filters.</para>
+    </listitem>
+    <listitem>
+      <para>Create various <command>statistics</command>.</para>
+    </listitem>
+    <listitem>
+      <para>... and <command>a lot more!</command></para>
+    </listitem>
       </itemizedlist>
       However, to really appreciate its power, you have to start using it.
     </para>
     <para>
       <xref linkend="ChIntroFig1"/> shows <application>Wireshark</application>
-	having captured some packets and waiting for you to examine
-	them.
-	<figure id="ChIntroFig1">
-	  <title>
-	    <application>Wireshark</application> captures packets and allows
-	    you to examine their content.
-	  </title>
-	  <graphic entityref="WiresharkMain1" format="PNG"/>
-	</figure>
-    </para>
-	</section>
+    having captured some packets and waiting for you to examine
+    them.
+    <figure id="ChIntroFig1">
+      <title>
+        <application>Wireshark</application> captures packets and allows
+        you to examine their content.
+      </title>
+      <graphic entityref="WiresharkMain1" format="PNG"/>
+    </figure>
+    </para>
+    </section>
 
-	<section>
-	<title>Live capture from many different network media</title>
-	<para>
-	  Wireshark can capture traffic from many different network media types
-	  - and despite its name - including wireless LAN as well.
-	  Which media types are supported, depends on many things like the
-	  operating system you are using.
-	  An overview of the supported media types can be found at:
-	  <ulink url="&WiresharkMediaPage;"/>.
-	</para>
-	</section>
+    <section>
+    <title>Live capture from many different network media</title>
+    <para>
+      Wireshark can capture traffic from many different network media types
+      - and despite its name - including wireless LAN as well.
+      Which media types are supported, depends on many things like the
+      operating system you are using.
+      An overview of the supported media types can be found at:
+      <ulink url="&WiresharkMediaPage;"/>.
+    </para>
+    </section>
 
     <section><title>Import files from many other capture programs</title>
-	<para>
-	    Wireshark can open packets captured from a large number of
-		other capture programs. For a list of input formats see
-		<xref linkend="ChIOInputFormatsSection"/>.
-	</para>
+    <para>
+        Wireshark can open packets captured from a large number of
+        other capture programs. For a list of input formats see
+        <xref linkend="ChIOInputFormatsSection"/>.
+    </para>
     </section>
     <section><title>Export files for many other capture programs</title>
-	<para>
-	    Wireshark can save packets captured in a large number of formats of
-		other capture programs. For a list of output formats see
-		<xref linkend="ChIOOutputFormatsSection"/>.
-	</para>
+    <para>
+        Wireshark can save packets captured in a large number of formats of
+        other capture programs. For a list of output formats see
+        <xref linkend="ChIOOutputFormatsSection"/>.
+    </para>
     </section>
 
-	<section>
-	<title>Many protocol decoders</title>
-	<para>
+    <section>
+    <title>Many protocol decoders</title>
+    <para>
       There are protocol decoders (or dissectors, as they are
       known in Wireshark) for a great many protocols:
-	  see <xref linkend="AppProtocols"/>.
-	</para>
-	</section>
+      see <xref linkend="AppProtocols"/>.
+    </para>
+    </section>
 
-	<section><title>Open Source Software</title>
+    <section><title>Open Source Software</title>
     <para>
       Wireshark is an open source software project, and is released under
       the <ulink url="&GPLWebsite;">GNU General Public License</ulink> (GPL).
-	  You can freely use Wireshark on any number of computers you like, without
-	  worrying about license keys or fees or such. In addition, all source
-	  code is freely available under the GPL. Because of that, it is very easy
-	  for people to add new protocols to Wireshark, either as plugins, or built
-	  into the source, and they often do!
+      You can freely use Wireshark on any number of computers you like, without
+      worrying about license keys or fees or such. In addition, all source
+      code is freely available under the GPL. Because of that, it is very easy
+      for people to add new protocols to Wireshark, either as plugins, or built
+      into the source, and they often do!
     </para>
-	</section>
+    </section>
 
     <section id="ChIntroNoFeatures"><title>What Wireshark is not</title>
-	<para>
-	Here are some things Wireshark does not provide:
+    <para>
+    Here are some things Wireshark does not provide:
       <itemizedlist>
-	<listitem><para>
-	  Wireshark isn't an intrusion detection system.  It will not warn you when
-	  someone does strange things on your network that he/she isn't allowed to
-	  do. However, if strange things happen, Wireshark might help you figure
-	  out what is really going on.
-	</para></listitem>
-	<listitem><para>
-	  Wireshark will not manipulate things on the network, it will only
-	  "measure" things from it. Wireshark doesn't send packets on the network
-	  or do other active things (except for name resolutions, but even
-	  that can be disabled).
-	</para></listitem>
+    <listitem><para>
+      Wireshark isn't an intrusion detection system.  It will not warn you when
+      someone does strange things on your network that he/she isn't allowed to
+      do. However, if strange things happen, Wireshark might help you figure
+      out what is really going on.
+    </para></listitem>
+    <listitem><para>
+      Wireshark will not manipulate things on the network, it will only
+      "measure" things from it. Wireshark doesn't send packets on the network
+      or do other active things (except for name resolutions, but even
+      that can be disabled).
+    </para></listitem>
       </itemizedlist>
-	</para>
+    </para>
     </section>
   </section>
 
@@ -184,158 +184,158 @@
     <title>System Requirements</title>
     <para>What you'll need to get Wireshark up and running ...</para>
 
-	<section><title>General Remarks</title>
-    <para>
-	<itemizedlist>
-	<listitem><para>The values below are the minimum requirements and only
-	"rules of thumb" for use on a moderately used network</para></listitem>
-	<listitem><para>Working with a busy network can easily produce huge
-	memory and disk space usage! For example: Capturing on a fully saturated
-	100MBit/s Ethernet will produce ~ 750MBytes/min! Having a fast processor,
-	lots of memory and disk space is a good idea in that case.</para></listitem>
-	<listitem><para>If Wireshark is running out of memory it crashes,
-	see: <ulink url="http://wiki.wireshark.org/KnownBugs/OutOfMemory"/>
-	for details and workarounds</para></listitem>
-	<listitem><para>Wireshark won't benefit much from Multiprocessor/Hyperthread
-	systems as time consuming tasks like filtering packets are single threaded.
-	No rule is without exception: during an "Update list of packets in real
-	time" capture, capturing traffic runs in one process and dissecting and
-	displaying packets runs in another process - which should benefit from two
-	processors.</para></listitem>
-	</itemizedlist>
+    <section><title>General Remarks</title>
+    <para>
+    <itemizedlist>
+    <listitem><para>The values below are the minimum requirements and only
+    "rules of thumb" for use on a moderately used network</para></listitem>
+    <listitem><para>Working with a busy network can easily produce huge
+    memory and disk space usage! For example: Capturing on a fully saturated
+    100MBit/s Ethernet will produce ~ 750MBytes/min! Having a fast processor,
+    lots of memory and disk space is a good idea in that case.</para></listitem>
+    <listitem><para>If Wireshark is running out of memory it crashes,
+    see: <ulink url="http://wiki.wireshark.org/KnownBugs/OutOfMemory"/>
+    for details and workarounds</para></listitem>
+    <listitem><para>Wireshark won't benefit much from Multiprocessor/Hyperthread
+    systems as time consuming tasks like filtering packets are single threaded.
+    No rule is without exception: during an "Update list of packets in real
+    time" capture, capturing traffic runs in one process and dissecting and
+    displaying packets runs in another process - which should benefit from two
+    processors.</para></listitem>
+    </itemizedlist>
     </para>
     </section>
 
-	<section><title>Microsoft Windows</title>
-    <para>
-	<itemizedlist>
-	<listitem><para>Windows XP Home, XP Pro, XP Tablet PC, XP Media
-	Center, Server 2003, Vista, 2008, 7, or 2008 R2
-	</para></listitem>
-	<listitem><para>Any modern 32-bit x86 or 64-bit AMD64/x86-64 processor.
-	</para></listitem>
-	<listitem><para>128MB available RAM. Larger capture files require more RAM.
-	</para></listitem>
-	<listitem><para>75MB available disk space. Capture files require additional disk space.
-	</para></listitem>
-	<listitem><para>800*600 (1280*1024 or higher recommended) resolution with
-	at least 65536 (16bit) colors (256 colors should work if Wireshark is
-	installed with the "legacy GTK1" selection of the Wireshark 1.0.x releases)
-	</para></listitem>
-	<listitem><para>A supported network card for capturing:
-	</para>
-	<itemizedlist>
-	<listitem><para>
-	  Ethernet: Any card supported by Windows should work. See the wiki
-	  pages on <ulink
-	  url="http://wiki.wireshark.org/CaptureSetup/Ethernet">Ethernet
-	  capture</ulink> and <ulink
-	  url="http://wiki.wireshark.org/CaptureSetup/Offloading">offloading</ulink>
-	  for issues that may affect your environment.
-	</para></listitem>
-	<listitem><para>
-	  802.11: See the <ulink
-	  url="http://wiki.wireshark.org/CaptureSetup/WLAN#head-02456742c655394c9e948a4c9a59d3441c92782f">Wireshark
-	  wiki page</ulink>. Capturing raw 802.11 information may be difficult without special equipment.
-	</para></listitem>
-	<listitem><para>
-	  Other media: See <ulink
-	  url="http://wiki.wireshark.org/CaptureSetup/NetworkMedia"/>
-	</para></listitem>
-	</itemizedlist>
-	</listitem>
-	</itemizedlist>
+    <section><title>Microsoft Windows</title>
+    <para>
+    <itemizedlist>
+    <listitem><para>Windows XP Home, XP Pro, XP Tablet PC, XP Media
+    Center, Server 2003, Vista, 2008, 7, or 2008 R2
+    </para></listitem>
+    <listitem><para>Any modern 32-bit x86 or 64-bit AMD64/x86-64 processor.
+    </para></listitem>
+    <listitem><para>128MB available RAM. Larger capture files require more RAM.
+    </para></listitem>
+    <listitem><para>75MB available disk space. Capture files require additional disk space.
+    </para></listitem>
+    <listitem><para>800*600 (1280*1024 or higher recommended) resolution with
+    at least 65536 (16bit) colors (256 colors should work if Wireshark is
+    installed with the "legacy GTK1" selection of the Wireshark 1.0.x releases)
+    </para></listitem>
+    <listitem><para>A supported network card for capturing:
+    </para>
+    <itemizedlist>
+    <listitem><para>
+      Ethernet: Any card supported by Windows should work. See the wiki
+      pages on <ulink
+      url="http://wiki.wireshark.org/CaptureSetup/Ethernet">Ethernet
+      capture</ulink> and <ulink
+      url="http://wiki.wireshark.org/CaptureSetup/Offloading">offloading</ulink>
+      for issues that may affect your environment.
+    </para></listitem>
+    <listitem><para>
+      802.11: See the <ulink
+      url="http://wiki.wireshark.org/CaptureSetup/WLAN#head-02456742c655394c9e948a4c9a59d3441c92782f">Wireshark
+      wiki page</ulink>. Capturing raw 802.11 information may be difficult without special equipment.
+    </para></listitem>
+    <listitem><para>
+      Other media: See <ulink
+      url="http://wiki.wireshark.org/CaptureSetup/NetworkMedia"/>
+    </para></listitem>
+    </itemizedlist>
+    </listitem>
+    </itemizedlist>
 
-	Remarks:
+    Remarks:
 
-	<itemizedlist>
-	<listitem><para>
-	  Many older Windows versions are no longer supported for three reasons:
-	  None of the developers use those systems which makes support
-	  difficult. The libraries Wireshark depends on (GTK, WinPcap, …) have
-	  dropped support for older releases. Microsoft <ulink
-	  url="http://support.microsoft.com/gp/lifeselect">has also dropped
-	  support for these systems</ulink>.
-	</para></listitem>
-	<listitem><para>
-	  Windows 95, 98 and ME are no longer supported. The "old technology"
-	  releases of Windows lack memory protection (specifically <ulink
-	  url="http://msdn.microsoft.com/en-us/library/aa366898.aspx">VirtualProtect</ulink>)
-	  which we use to improve program safety and security. The last known
-	  version to work was Ethereal 0.10.14 (which includes WinPcap 3.1). You
-	  can get it from <ulink url="http://ethereal.com/download.html" />.
-	  According to <ulink
-	  url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1130">this
-	  bug report</ulink>, you may need to install Ethereal 0.10.0 on some
-	  systems.
-	</para>
-	<para>
+    <itemizedlist>
+    <listitem><para>
+      Many older Windows versions are no longer supported for three reasons:
+      None of the developers use those systems which makes support
+      difficult. The libraries Wireshark depends on (GTK, WinPcap, …) have
+      dropped support for older releases. Microsoft <ulink
+      url="http://support.microsoft.com/gp/lifeselect">has also dropped
+      support for these systems</ulink>.
+    </para></listitem>
+    <listitem><para>
+      Windows 95, 98 and ME are no longer supported. The "old technology"
+      releases of Windows lack memory protection (specifically <ulink
+      url="http://msdn.microsoft.com/en-us/library/aa366898.aspx">VirtualProtect</ulink>)
+      which we use to improve program safety and security. The last known
+      version to work was Ethereal 0.10.14 (which includes WinPcap 3.1). You
+      can get it from <ulink url="http://ethereal.com/download.html" />.
+      According to <ulink
+      url="https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1130">this
+      bug report</ulink>, you may need to install Ethereal 0.10.0 on some
+      systems.
+    </para>
+    <para>
           Microsoft retired support for Windows 98 and ME in 2006.
-	</para></listitem>
-	<listitem><para>
-	  Windows NT 4.0 no longer works with Wireshark. The last known version
-	  to work was Wireshark 0.99.4 (which includes WinPcap 3.1). You still
-	  can get it from <ulink
-	  url="http://www.wireshark.org/download/win32/all-versions/wireshark-setup-0.99.4.exe"
-	  />.
-	</para>
-	<para>
-	  Microsoft retired support for Windows NT 4.0 in 2004.
-	</para></listitem>
-	<listitem><para>
-	  Windows 2000 no longer works with Wireshark. The last known version
-	  to work was Wireshark 1.2.x (which includes WinPcap 4.1.2). You still
-	  can get it from <ulink
-	  url="http://www.wireshark.org/download/win32/all-versions/" />.
-	</para>
-	<para>
-	  Microsoft retired support for Windows 2000 in 2010.
-	</para></listitem>
-	<listitem><para>
-	  Windows CE and the embedded versions of Windows are not currently supported.
-	</para></listitem>
-	<listitem><para>
-	  Multiple monitor setups are supported but may behave a bit
-  	  strangely.
-	</para></listitem>
-	</itemizedlist>
-    </para>
-	</section>
+    </para></listitem>
+    <listitem><para>
+      Windows NT 4.0 no longer works with Wireshark. The last known version
+      to work was Wireshark 0.99.4 (which includes WinPcap 3.1). You still
+      can get it from <ulink
+      url="http://www.wireshark.org/download/win32/all-versions/wireshark-setup-0.99.4.exe"
+      />.
+    </para>
+    <para>
+      Microsoft retired support for Windows NT 4.0 in 2004.
+    </para></listitem>
+    <listitem><para>
+      Windows 2000 no longer works with Wireshark. The last known version
+      to work was Wireshark 1.2.x (which includes WinPcap 4.1.2). You still
+      can get it from <ulink
+      url="http://www.wireshark.org/download/win32/all-versions/" />.
+    </para>
+    <para>
+      Microsoft retired support for Windows 2000 in 2010.
+    </para></listitem>
+    <listitem><para>
+      Windows CE and the embedded versions of Windows are not currently supported.
+    </para></listitem>
+    <listitem><para>
+      Multiple monitor setups are supported but may behave a bit
+        strangely.
+    </para></listitem>
+    </itemizedlist>
+    </para>
+    </section>
 
-	<section><title>Unix / Linux</title>
+    <section><title>Unix / Linux</title>
     <para>
       Wireshark currently runs on most UNIX platforms.
-	  The system requirements should be comparable to the Windows values
-	  listed above.
+      The system requirements should be comparable to the Windows values
+      listed above.
     </para>
     <para>
       Binary packages are available for at least the following platforms:
     </para>
-	<para>
-	<itemizedlist>
-	<listitem><para>Apple Mac OS X</para></listitem>
-	<listitem><para>Debian GNU/Linux</para></listitem>
-	<listitem><para>FreeBSD</para></listitem>
-	<listitem><para>Gentoo Linux</para></listitem>
-	<listitem><para>HP-UX</para></listitem>
-	<listitem><para>Mandriva Linux</para></listitem>
-	<listitem><para>NetBSD</para></listitem>
-	<listitem><para>OpenPKG</para></listitem>
-	<listitem><para>Red Hat Enterprise/Fedora Linux</para></listitem>
-	<listitem><para>rPath Linux</para></listitem>
-	<listitem><para>Sun Solaris/i386</para></listitem>
-	<listitem><para>Sun Solaris/Sparc</para></listitem>
-	<listitem><para>Canonical Ubuntu</para></listitem>
-	</itemizedlist>
-	</para>
+    <para>
+    <itemizedlist>
+    <listitem><para>Apple Mac OS X</para></listitem>
+    <listitem><para>Debian GNU/Linux</para></listitem>
+    <listitem><para>FreeBSD</para></listitem>
+    <listitem><para>Gentoo Linux</para></listitem>
+    <listitem><para>HP-UX</para></listitem>
+    <listitem><para>Mandriva Linux</para></listitem>
+    <listitem><para>NetBSD</para></listitem>
+    <listitem><para>OpenPKG</para></listitem>
+    <listitem><para>Red Hat Enterprise/Fedora Linux</para></listitem>
+    <listitem><para>rPath Linux</para></listitem>
+    <listitem><para>Sun Solaris/i386</para></listitem>
+    <listitem><para>Sun Solaris/Sparc</para></listitem>
+    <listitem><para>Canonical Ubuntu</para></listitem>
+    </itemizedlist>
+    </para>
     <para>
       If a binary package is not available for your platform, you should
       download the source and try to build it.
-	  Please report your experiences
-	  to <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;
-	  </ulink>.
+      Please report your experiences
+      to <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;
+      </ulink>.
     </para>
-	</section>
+    </section>
 
   </section>
 
@@ -348,12 +348,12 @@
       downloading.
     </para>
     <para>
-	A new Wireshark version will typically become available every 4-8 months.
+    A new Wireshark version will typically become available every 4-8 months.
     </para>
     <para>
-	If you want to be notified about new Wireshark releases, you should
-	subscribe to the wireshark-announce mailing list. You will find more
-	details in <xref linkend="ChIntroMailingLists"/>.
+    If you want to be notified about new Wireshark releases, you should
+    subscribe to the wireshark-announce mailing list. You will find more
+    details in <xref linkend="ChIntroMailingLists"/>.
     </para>
   </section>
 
@@ -363,7 +363,7 @@
       In late 1997, Gerald Combs needed a tool for tracking down
       networking problems and wanted to learn more about networking, so
       he started writing Ethereal (the former name of the Wireshark project)
-	  as a way to solve both problems.
+      as a way to solve both problems.
     </para>
     <para>
       Ethereal was initially released, after several pauses in development,
@@ -377,8 +377,8 @@
     </para>
     <para>
       In October, 1998, Guy Harris of Network Appliance was looking for
-	  something better than tcpview, so he started applying patches and
-	  contributing dissectors to Ethereal.
+      something better than tcpview, so he started applying patches and
+      contributing dissectors to Ethereal.
     </para>
     <para>
       In late 1998, Richard Sharpe, who was giving TCP/IP courses, saw its
@@ -418,13 +418,13 @@
       protocol dissectors to Wireshark, and it is expected that this will
       continue.  You can find a list of the people who have contributed
       code to Wireshark by checking the about dialog box of Wireshark, or at
-	  the <ulink url="&WiresharkAuthorsPage;">authors</ulink> page on the
+      the <ulink url="&WiresharkAuthorsPage;">authors</ulink> page on the
       Wireshark web site.
     </para>
     <para>
       Wireshark is an open source software project, and is released under
       the <ulink url="&GPLWebsite;">GNU General Public License</ulink> (GPL).
-	  All source code is freely available under the GPL.  You are welcome to
+      All source code is freely available under the GPL.  You are welcome to
       modify Wireshark to suit your own needs, and it would be appreciated
       if you contribute your improvements back to the Wireshark team.
     </para>
@@ -432,31 +432,31 @@
       You gain three benefits by contributing your improvements back to the
       community:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    Other people who find your contributions useful will appreciate
-	    them, and you will know that you have helped people in the
-	    same way that the developers of Wireshark have helped people.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The developers of Wireshark might improve your changes even more,
-		as there's always room for improvement. Or they may implement some
-		advanced things on top of your code, which can be useful for yourself
-		too.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The maintainers and developers of Wireshark will maintain your
-	    code as well, fixing it when API changes or other changes are
-	    made, and generally keeping it in tune with what is happening
-	    with Wireshark. So if Wireshark is updated (which is done often),
-		you can get a new Wireshark version from the website and your changes
-		will already be included without any effort for you.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Other people who find your contributions useful will appreciate
+        them, and you will know that you have helped people in the
+        same way that the developers of Wireshark have helped people.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The developers of Wireshark might improve your changes even more,
+        as there's always room for improvement. Or they may implement some
+        advanced things on top of your code, which can be useful for yourself
+        too.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The maintainers and developers of Wireshark will maintain your
+        code as well, fixing it when API changes or other changes are
+        made, and generally keeping it in tune with what is happening
+        with Wireshark. So if Wireshark is updated (which is done often),
+        you can get a new Wireshark version from the website and your changes
+        will already be included without any effort for you.
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
     <para>
@@ -468,224 +468,224 @@
 
   <section id="ChIntroHelp">
     <title>Reporting problems and getting help</title>
-	<para>
+    <para>
       If you have problems, or need help with Wireshark, there are several
       places that may be of interest to you (well, besides this guide of
-	  course).
-	</para>
+      course).
+    </para>
 
-	<section id="ChIntroHomepage"><title>Website</title>
+    <section id="ChIntroHomepage"><title>Website</title>
     <para>
-	You will find lots of useful information on the Wireshark homepage at
-	<ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
-	</para>
-	</section>
+    You will find lots of useful information on the Wireshark homepage at
+    <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
+    </para>
+    </section>
 
-	<section id="ChIntroWiki"><title>Wiki</title>
-    <para>
-	The Wireshark Wiki at <ulink
-	url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink> provides a wide range
-	of information related to Wireshark and packet capturing in general.
-	You will find a lot of information not part of this user's guide. For
-	example, there is an explanation how to capture on a switched network,
-	an ongoing effort to build a protocol reference and a lot more.
-	</para>
-	<para>
-	And best of all, if you would like to contribute your knowledge on a
-	specific topic (maybe a network protocol you know well), you can edit the
-	wiki pages by simply using your web browser.
-	</para>
-	</section>
+    <section id="ChIntroWiki"><title>Wiki</title>
+    <para>
+    The Wireshark Wiki at <ulink
+    url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink> provides a wide range
+    of information related to Wireshark and packet capturing in general.
+    You will find a lot of information not part of this user's guide. For
+    example, there is an explanation how to capture on a switched network,
+    an ongoing effort to build a protocol reference and a lot more.
+    </para>
+    <para>
+    And best of all, if you would like to contribute your knowledge on a
+    specific topic (maybe a network protocol you know well), you can edit the
+    wiki pages by simply using your web browser.
+    </para>
+    </section>
 
-	<section id="ChIntroQA"><title>Q&amp;A Forum</title>
-	<para>
-	The Wireshark Q and A forum at
-	<ulink url="&WiresharkQASite;">&WiresharkQASite;</ulink> offers a resource
-	where questions and answers come together. You have the option to search
-	what questions were asked before and what answers were given by people who
-	knew about the issue. Answers are graded, so you can pick out the best ones
-	easily. If your issue isn't discussed before you can post one yourself.
-	</para>
-	</section>
+    <section id="ChIntroQA"><title>Q&amp;A Forum</title>
+    <para>
+    The Wireshark Q and A forum at
+    <ulink url="&WiresharkQASite;">&WiresharkQASite;</ulink> offers a resource
+    where questions and answers come together. You have the option to search
+    what questions were asked before and what answers were given by people who
+    knew about the issue. Answers are graded, so you can pick out the best ones
+    easily. If your issue isn't discussed before you can post one yourself.
+    </para>
+    </section>
 
-	<section id="ChIntroFAQ"><title>FAQ</title>
+    <section id="ChIntroFAQ"><title>FAQ</title>
+    <para>
+    The "Frequently Asked Questions" will list often asked questions and
+    the corresponding answers.
+    <note><title>Read the FAQ!</title>
     <para>
-	The "Frequently Asked Questions" will list often asked questions and
-	the corresponding answers.
-	<note><title>Read the FAQ!</title>
-	<para>
-	Before sending any mail to the mailing lists below, be sure to read the
-	FAQ, as it will often answer the question(s) you might have. This will save
-	yourself and others a lot of time (keep in mind that a lot of people are
-	subscribed to the mailing lists).
+    Before sending any mail to the mailing lists below, be sure to read the
+    FAQ, as it will often answer the question(s) you might have. This will save
+    yourself and others a lot of time (keep in mind that a lot of people are
+    subscribed to the mailing lists).
     </para>
     </note>
-	You will find the FAQ inside Wireshark by clicking the menu item
-	Help/Contents and selecting the FAQ page in the dialog shown.
+    You will find the FAQ inside Wireshark by clicking the menu item
+    Help/Contents and selecting the FAQ page in the dialog shown.
     </para>
     <para>
-	An online version is available at the Wireshark website:
-	<ulink url="&WiresharkFAQPage;">&WiresharkFAQPage;</ulink>. You might
-	prefer this online version, as it's typically more up to date and the HTML
-	format is easier to use.
+    An online version is available at the Wireshark website:
+    <ulink url="&WiresharkFAQPage;">&WiresharkFAQPage;</ulink>. You might
+    prefer this online version, as it's typically more up to date and the HTML
+    format is easier to use.
     </para>
-	</section>
+    </section>
 
-	<section id="ChIntroMailingLists"><title>Mailing Lists</title>
+    <section id="ChIntroMailingLists"><title>Mailing Lists</title>
     <para>
       There are several mailing lists of specific Wireshark topics available:
       <variablelist>
-	<varlistentry><term><command>wireshark-announce</command></term>
-	  <listitem>
-	    <para>
-	      This mailing list will inform you about new program
-		  releases, which usually appear about every 4-8 weeks.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>wireshark-users</command></term>
-	  <listitem>
-	    <para>
-	      This list is for users of Wireshark.  People post
-	      questions about building and using Wireshark, others (hopefully)
-		  provide answers.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>wireshark-dev</command></term>
-	  <listitem>
-	    <para>
-	      This list is for Wireshark developers. If you want to start
-	      developing a protocol dissector, join this list.
-	    </para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry><term><command>wireshark-announce</command></term>
+      <listitem>
+        <para>
+          This mailing list will inform you about new program
+          releases, which usually appear about every 4-8 weeks.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>wireshark-users</command></term>
+      <listitem>
+        <para>
+          This list is for users of Wireshark.  People post
+          questions about building and using Wireshark, others (hopefully)
+          provide answers.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>wireshark-dev</command></term>
+      <listitem>
+        <para>
+          This list is for Wireshark developers. If you want to start
+          developing a protocol dissector, join this list.
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
       You can subscribe to each of these lists from the Wireshark web site:
       <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.  Simply
       select the <command>mailing lists</command> link on the left hand
       side of the site. The lists are archived at the Wireshark web site
       as well.
-	<tip><title>Tip!</title>
-	<para>
-	You can search in the list archives to see if someone asked the same
-	question some time before and maybe already got an answer. That way you
-	don't have to wait until someone answers your question.
-	</para>
-	</tip>
-    </para>
-	</section>
+    <tip><title>Tip!</title>
+    <para>
+    You can search in the list archives to see if someone asked the same
+    question some time before and maybe already got an answer. That way you
+    don't have to wait until someone answers your question.
+    </para>
+    </tip>
+    </para>
+    </section>
 
-	<section><title>Reporting Problems</title>
-	<note><title>Note!</title>
-	<para>
-	Before reporting any problems, please make sure you have installed the
-	latest version of Wireshark.
-	</para>
-	</note>
+    <section><title>Reporting Problems</title>
+    <note><title>Note!</title>
+    <para>
+    Before reporting any problems, please make sure you have installed the
+    latest version of Wireshark.
+    </para>
+    </note>
     <para>
       When reporting problems with Wireshark, it is helpful if you supply the
       following information:
       <orderedlist>
-	<listitem>
-	  <para>
-	    The version number of Wireshark and the dependent libraries linked with
-	    it, e.g. GTK+, etc. You can obtain this from the about dialog box
-	    of Wireshark, or with the command <command>wireshark -v</command>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Information about the platform you run Wireshark on.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    A detailed description of your problem.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-		If you get an error/warning message, copy the text of that message
-		(and also a few lines before and after it, if there are some), so
-		others may find the place where things go wrong. Please don't
-		give something like: "I get a warning while doing x" as this won't
-		give a good idea where to look at.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        The version number of Wireshark and the dependent libraries linked with
+        it, e.g. GTK+, etc. You can obtain this from the about dialog box
+        of Wireshark, or with the command <command>wireshark -v</command>.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Information about the platform you run Wireshark on.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        A detailed description of your problem.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        If you get an error/warning message, copy the text of that message
+        (and also a few lines before and after it, if there are some), so
+        others may find the place where things go wrong. Please don't
+        give something like: "I get a warning while doing x" as this won't
+        give a good idea where to look at.
+      </para>
+    </listitem>
       </orderedlist>
     </para>
-	<note><title>Don't send large files!</title>
-	<para>
-	Do not send large files (>100KB) to the mailing lists, just place a note
-	that further data is available on request. Large files will only annoy a
-	lot of people on the list who are not interested in your specific problem.
-	If required, you will be asked for further data by the persons who really
-	can help you.
-	</para>
-	</note>
-	<warning><title>Don't send confidential information!</title>
-	<para>
-	If you send captured data to the mailing lists, be sure they don't contain
-	any sensitive or confidential information like passwords or such.
-	</para>
-	</warning>
+    <note><title>Don't send large files!</title>
+    <para>
+    Do not send large files (>100KB) to the mailing lists, just place a note
+    that further data is available on request. Large files will only annoy a
+    lot of people on the list who are not interested in your specific problem.
+    If required, you will be asked for further data by the persons who really
+    can help you.
+    </para>
+    </note>
+    <warning><title>Don't send confidential information!</title>
+    <para>
+    If you send captured data to the mailing lists, be sure they don't contain
+    any sensitive or confidential information like passwords or such.
+    </para>
+    </warning>
   </section>
 
-	<section><title>Reporting Crashes on UNIX/Linux platforms</title>
+    <section><title>Reporting Crashes on UNIX/Linux platforms</title>
     <para>
       When reporting crashes with Wireshark, it is helpful if you supply the
       traceback information (besides the information mentioned in "Reporting
-	  Problems").
+      Problems").
     </para>
-	  <para>
-	    You can obtain this traceback information with the following commands:
-	    <programlisting>
+      <para>
+        You can obtain this traceback information with the following commands:
+        <programlisting>
 <![CDATA[
 $ gdb `whereis wireshark | cut -f2 -d: | cut -d' ' -f2` core >& bt.txt
 backtrace
 ^D
 $
 ]]>
-		</programlisting>
-	    <note>
-	      <para>
-		Type the characters in the first line verbatim! Those are
-		back-tics there!
-	      </para>
-	    </note>
-	    <note>
-	      <para>
-		backtrace is a <command>gdb</command> command. You should
-		enter it verbatim after the first line shown above, but it will not be
-		echoed. The ^D
-		(Control-D, that is, press the Control key and the D key
-		together) will cause <command>gdb</command> to exit. This will
-		leave you with a file called
-		<filename>bt.txt</filename> in the current directory.
-		Include the file with your bug report.
-	      </para>
-	    </note>
-	    <note>
-	      <para>
-		If you do not have <command>gdb</command> available, you
-		will have to check out your operating system's debugger.
-	      </para>
-	    </note>
-	  </para>
-	  <para>
-	    You should mail the traceback to the
-		<ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>
-	    mailing list.
-	  </para>
+        </programlisting>
+        <note>
+          <para>
+        Type the characters in the first line verbatim! Those are
+        back-tics there!
+          </para>
+        </note>
+        <note>
+          <para>
+        backtrace is a <command>gdb</command> command. You should
+        enter it verbatim after the first line shown above, but it will not be
+        echoed. The ^D
+        (Control-D, that is, press the Control key and the D key
+        together) will cause <command>gdb</command> to exit. This will
+        leave you with a file called
+        <filename>bt.txt</filename> in the current directory.
+        Include the file with your bug report.
+          </para>
+        </note>
+        <note>
+          <para>
+        If you do not have <command>gdb</command> available, you
+        will have to check out your operating system's debugger.
+          </para>
+        </note>
+      </para>
+      <para>
+        You should mail the traceback to the
+        <ulink url="mailto:&WiresharkDevMailList;">&WiresharkDevMailList;</ulink>
+        mailing list.
+      </para>
   </section>
 
-	<section><title>Reporting Crashes on Windows platforms</title>
+    <section><title>Reporting Crashes on Windows platforms</title>
     <para>
-	The Windows distributions don't contain the symbol files (.pdb), because
-	they are very large. For this reason it's not possible to create
-	a meaningful backtrace file from it. You should report your crash just
-	like other problems, using the mechanism described above.
+    The Windows distributions don't contain the symbol files (.pdb), because
+    they are very large. For this reason it's not possible to create
+    a meaningful backtrace file from it. You should report your crash just
+    like other problems, using the mechanism described above.
     </para>
   </section>
   </section>
diff --git a/docbook/wsug_src/WSUG_chapter_io.xml b/docbook/wsug_src/WSUG_chapter_io.xml
index 4e1c71e77b..6778d7360c 100644
--- a/docbook/wsug_src/WSUG_chapter_io.xml
+++ b/docbook/wsug_src/WSUG_chapter_io.xml
@@ -6,28 +6,28 @@
 
   <section id="ChIOIntroductionSection"><title>Introduction</title>
     <para>
-	This chapter will describe input and output of capture data.
-	<itemizedlist>
-	<listitem>
-	  <para>
-	    Open/Import capture files in various capture file formats
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Save/Export capture files in various capture file formats
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	  Merge capture files together
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Print packets
-	  </para>
-	</listitem>
+    This chapter will describe input and output of capture data.
+    <itemizedlist>
+    <listitem>
+      <para>
+        Open/Import capture files in various capture file formats
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Save/Export capture files in various capture file formats
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+      Merge capture files together
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Print packets
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
   </section>
@@ -35,289 +35,289 @@
   <section id="ChIOOpenSection"><title>Open capture files</title>
     <para>
       Wireshark can read in previously saved capture files. 
-	  To read them, simply select the menu or toolbar item: "File/
-	  <inlinegraphic entityref="WiresharkToolbarOpen" format="PNG"/>
-	  <command>Open</command>".  
+      To read them, simply select the menu or toolbar item: "File/
+      <inlinegraphic entityref="WiresharkToolbarOpen" format="PNG"/>
+      <command>Open</command>".  
       Wireshark will then pop up the File 
       Open dialog box, which is discussed in more detail in 
       <xref linkend="ChIOOpen"/>. 
     </para>
-	<tip><title>It's convenient to use drag-and-drop!</title>
+    <tip><title>It's convenient to use drag-and-drop!</title>
     <para>
-	... to open a file, by simply dragging the desired file from your file 
-	manager and dropping it onto Wireshark's main window. 
-	However, drag-and-drop is not available/won't work in all desktop 
-	environments.
+    ... to open a file, by simply dragging the desired file from your file 
+    manager and dropping it onto Wireshark's main window. 
+    However, drag-and-drop is not available/won't work in all desktop 
+    environments.
     </para>
     </tip>
     <para>
-	  If you haven't previously saved the current capture file, you will be asked 
-	  to do so, to prevent data loss (this behaviour can be disabled in the 
-	  preferences).
+      If you haven't previously saved the current capture file, you will be asked 
+      to do so, to prevent data loss (this behaviour can be disabled in the 
+      preferences).
     </para>
     <para>
-	  In addition to its native file format (libpcap format, also used by 
-	  tcpdump/WinDump and other libpcap/WinPcap-based programs), Wireshark can 
-	  read capture files from a large number of other packet capture programs 
-	  as well. See <xref linkend="ChIOInputFormatsSection"/> for the list of 
-	  capture formats Wireshark understands.
+      In addition to its native file format (libpcap format, also used by 
+      tcpdump/WinDump and other libpcap/WinPcap-based programs), Wireshark can 
+      read capture files from a large number of other packet capture programs 
+      as well. See <xref linkend="ChIOInputFormatsSection"/> for the list of 
+      capture formats Wireshark understands.
     </para>
-	
+    
     <section id="ChIOOpen">
     <title>The "Open Capture File" dialog box</title>
       <para>
-	The "Open Capture File" dialog box allows you to search for a 
-	capture file containing previously captured packets for display in 
-	Wireshark.  <xref linkend="ChIOOpenFileTab"/> shows some examples 
-	  of the Wireshark Open File Dialog box.
+    The "Open Capture File" dialog box allows you to search for a 
+    capture file containing previously captured packets for display in 
+    Wireshark.  <xref linkend="ChIOOpenFileTab"/> shows some examples 
+      of the Wireshark Open File Dialog box.
       </para>
-	    <note>
-	      <title>The dialog appearance depends on your system!</title>
-	      <para>
-		  The appearance of this dialog depends on the system and/or GTK+ 
-		  toolkit version used. However, the functionality remains basically 
-		  the same on any particular system.
-	      </para>
-	    </note>
-		
-	<para>
-	<command>Common dialog behaviour</command> on all systems:
-	</para>
-	<itemizedlist>
-	  <listitem>
-	    <para>
-	      Select files and directories.
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Click the Open/Ok button to accept your selected file and open it. 
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Click the Cancel button to go back to Wireshark and not load a capture 
-	      file.
-	    </para>
-	  </listitem>
-	</itemizedlist>
+        <note>
+          <title>The dialog appearance depends on your system!</title>
+          <para>
+          The appearance of this dialog depends on the system and/or GTK+ 
+          toolkit version used. However, the functionality remains basically 
+          the same on any particular system.
+          </para>
+        </note>
+        
+    <para>
+    <command>Common dialog behaviour</command> on all systems:
+    </para>
+    <itemizedlist>
+      <listitem>
+        <para>
+          Select files and directories.
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Click the Open/Ok button to accept your selected file and open it. 
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Click the Cancel button to go back to Wireshark and not load a capture 
+          file.
+        </para>
+      </listitem>
+    </itemizedlist>
 
       <para>
-	<command>Wireshark extensions</command> to the standard behaviour of 
-	these dialogs:
+    <command>Wireshark extensions</command> to the standard behaviour of 
+    these dialogs:
       </para>
-	<itemizedlist>
-	  <listitem>
-	    <para>
-	      View file preview information (like the filesize, the number of 
-		  packets, ...), if you've selected a capture file.
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Specify a display filter with the "Filter:" button and filter 
-	      field. This filter will be used when opening the new file. 
-		  The text field background becomes green for a valid filter string 
-		  and red for an invalid one.
-		  Clicking on the Filter button causes Wireshark to pop up 
-	      the Filters dialog box (which is discussed further in 
-	      <xref linkend="ChWorkDisplayFilterSection"/>).
-	    </para>
-	    <para>
-		  XXX - we need a better description of these read filters
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Specify which type of name resolution is to be performed for all packets by 
-		  clicking on one of the "... name resolution" check buttons. 
-		  Details about name resolution can be found in 
-		  <xref linkend="ChAdvNameResolutionSection"/>.
-	    </para>
-	  </listitem>
-	</itemizedlist>
+    <itemizedlist>
+      <listitem>
+        <para>
+          View file preview information (like the filesize, the number of 
+          packets, ...), if you've selected a capture file.
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Specify a display filter with the "Filter:" button and filter 
+          field. This filter will be used when opening the new file. 
+          The text field background becomes green for a valid filter string 
+          and red for an invalid one.
+          Clicking on the Filter button causes Wireshark to pop up 
+          the Filters dialog box (which is discussed further in 
+          <xref linkend="ChWorkDisplayFilterSection"/>).
+        </para>
+        <para>
+          XXX - we need a better description of these read filters
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Specify which type of name resolution is to be performed for all packets by 
+          clicking on one of the "... name resolution" check buttons. 
+          Details about name resolution can be found in 
+          <xref linkend="ChAdvNameResolutionSection"/>.
+        </para>
+      </listitem>
+    </itemizedlist>
 
-	<tip><title>Save a lot of time loading huge capture files!</title>
+    <tip><title>Save a lot of time loading huge capture files!</title>
     <para>
-	You can change the display filter and name resolution settings later 
-	while viewing the packets. 
-	However, loading huge capture files can take a significant amount of 
-	extra time if these settings are changed later, so in such situations it can 
-	be a good idea to set at least the filter in advance here.
+    You can change the display filter and name resolution settings later 
+    while viewing the packets. 
+    However, loading huge capture files can take a significant amount of 
+    extra time if these settings are changed later, so in such situations it can 
+    be a good idea to set at least the filter in advance here.
     </para>
     </tip>
-	
-	<!-- frame="none" -->
+    
+    <!-- frame="none" -->
     <table id="ChIOOpenFileTab">
-	<title>The system specific "Open Capture File" dialog box</title>
+    <title>The system specific "Open Capture File" dialog box</title>
       <tgroup cols="2">
-	    <tbody>
-		<row>
-		<entry valign="top">
-		<para>
+        <tbody>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOOpenFileDialogWin32">
-	<title>"Open" on native Windows</title>
-	<graphic entityref="WiresharkOpenDialogWin32" format="PNG"/>
+    <title>"Open" on native Windows</title>
+    <graphic entityref="WiresharkOpenDialogWin32" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Microsoft Windows</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Microsoft Windows</command></para>
       <para>
-		This is the common Windows file open dialog - 
-		plus some Wireshark extensions.
+        This is the common Windows file open dialog - 
+        plus some Wireshark extensions.
       </para>
-	    <para>
-		Specific for this dialog:
+        <para>
+        Specific for this dialog:
       </para>
-	<itemizedlist>
-	<listitem>
-	    <para>
-	      If available, the "Help" button will lead you to this section of 
-		  this "User's Guide".
-	    </para>
-	</listitem>
-	<listitem>
-	    <note><para>
- 		  The "Filter:" button currently doesn't work on Windows!
-	    </para></note>
-	</listitem>
-	</itemizedlist>
-		</entry>
-	      </row>
-		<row>
-		<entry valign="top">
-		<para>
+    <itemizedlist>
+    <listitem>
+        <para>
+          If available, the "Help" button will lead you to this section of 
+          this "User's Guide".
+        </para>
+    </listitem>
+    <listitem>
+        <note><para>
+           The "Filter:" button currently doesn't work on Windows!
+        </para></note>
+    </listitem>
+    </itemizedlist>
+        </entry>
+          </row>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOOpenFileDialog">
-	<title>"Open" - new GTK version</title>
-	<graphic entityref="WiresharkOpenDialog24" format="PNG"/>
+    <title>"Open" - new GTK version</title>
+    <graphic entityref="WiresharkOpenDialog24" format="PNG"/>
       </figure>
-		</para>
-	  </entry>
-	  <entry valign="top">
+        </para>
+      </entry>
+      <entry valign="top">
       <para><command>Unix/Linux: GTK version >= 2.4</command></para>
       <para>
-		This is the common Gimp/GNOME file open dialog - 
-		plus some Wireshark extensions.
+        This is the common Gimp/GNOME file open dialog - 
+        plus some Wireshark extensions.
       </para>
-	    <para>
-		Specific for this dialog:
+        <para>
+        Specific for this dialog:
       </para>
-	<itemizedlist>
-	<listitem>
-	    <para>
-		The "+ Add" button allows you to add a directory, selected in the 
-		right-hand pane, to the favorites list on the left. Those changes 
-		are persistent.
-	    </para>
-	</listitem>
-	<listitem>
-	    <para>
-		The "- Remove" button allows you to remove a selected directory from 
-		that list again (the items like: "Home", "Desktop", and "Filesystem" 
-		cannot be removed).
-	    </para>
-	</listitem>
-	<listitem>
-	    <para>
-		  If Wireshark doesn't recognize the selected file as a capture file, 
-		  it will grey out the "Open" button.
-	    </para>
-	</listitem>
-	</itemizedlist>
-	  </entry>
-		</row>
-	      <row>
-		<entry valign="top">
-		<para>
+    <itemizedlist>
+    <listitem>
+        <para>
+        The "+ Add" button allows you to add a directory, selected in the 
+        right-hand pane, to the favorites list on the left. Those changes 
+        are persistent.
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+        The "- Remove" button allows you to remove a selected directory from 
+        that list again (the items like: "Home", "Desktop", and "Filesystem" 
+        cannot be removed).
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+          If Wireshark doesn't recognize the selected file as a capture file, 
+          it will grey out the "Open" button.
+        </para>
+    </listitem>
+    </itemizedlist>
+      </entry>
+        </row>
+          <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOOpenFileDialog1">
-	<title>"Open" - old GTK version</title>
-	<graphic entityref="WiresharkOpenDialog20" format="PNG"/>
+    <title>"Open" - old GTK version</title>
+    <graphic entityref="WiresharkOpenDialog20" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-	  <entry valign="top">
-	    <para>
-		<command>Unix/Linux: GTK version &lt; 2.4</command></para>
-		<para>
-		  This is the file open dialog of former Gimp/GNOME versions - 
-		  plus some Wireshark extensions.
-		</para>
-	    <para>
-		Specific for this dialog:
+        </para>
+        </entry>
+      <entry valign="top">
+        <para>
+        <command>Unix/Linux: GTK version &lt; 2.4</command></para>
+        <para>
+          This is the file open dialog of former Gimp/GNOME versions - 
+          plus some Wireshark extensions.
+        </para>
+        <para>
+        Specific for this dialog:
       </para>
-	<itemizedlist>
-	<listitem>
-	    <para>
-		  If Wireshark doesn't recognize the selected file as a capture file, 
-		  it will grey out the "Ok" button.
-	    </para>
-	</listitem>
-	</itemizedlist>
-		</entry>
-		</row>
-	    </tbody>
+    <itemizedlist>
+    <listitem>
+        <para>
+          If Wireshark doesn't recognize the selected file as a capture file, 
+          it will grey out the "Ok" button.
+        </para>
+    </listitem>
+    </itemizedlist>
+        </entry>
+        </row>
+        </tbody>
       </tgroup>
     </table>
-		
-		
+        
+        
     </section>
 
   <section id="ChIOInputFormatsSection">
     <title>Input File Formats</title>
     <para>
-	The following file formats from other capture tools can be opened by 
-	<application>Wireshark</application>:
-	<itemizedlist>
-	      <listitem><para>libpcap - captures from <emphasis>Wireshark</emphasis>/<emphasis>TShark</emphasis>/<emphasis>dumpcap</emphasis>, <emphasis>tcpdump</emphasis>, and various other tools using libpcap's/tcpdump's capture format</para></listitem>
-	      <listitem><para>pcap-ng - "next-generation" successor to libpcap format</para></listitem>
-	      <listitem><para>Sun snoop and atmsnoop</para></listitem>
-	      <listitem><para>Shomiti/Finisar <emphasis>Surveyor</emphasis> captures</para></listitem>
-	      <listitem><para>Novell <emphasis>LANalyzer</emphasis> captures</para></listitem>
-	      <listitem><para>Microsoft Network Monitor captures</para></listitem>
-	      <listitem><para>AIX's iptrace captures</para></listitem>
-	      <listitem><para>Cinco Networks NetXray captures</para></listitem>		  
-	      <listitem><para>Network Associates Windows-based Sniffer and Sniffer Pro captures</para></listitem>
-	      <listitem><para>Network General/Network Associates DOS-based Sniffer (compressed or uncompressed) captures</para></listitem>
-	      <listitem><para>AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek/EtherHelp/PacketGrabber captures</para></listitem>
-	      <listitem><para>RADCOM's WAN/LAN Analyzer captures</para></listitem>
-	      <listitem><para>Network Instruments Observer version 9 captures</para></listitem>
-	      <listitem><para>Lucent/Ascend router debug output</para></listitem>		  
-	      <listitem><para>HP-UX's nettl</para></listitem>
-	      <listitem><para>Toshiba's ISDN routers dump output</para></listitem>
-	      <listitem><para>ISDN4BSD <emphasis>i4btrace</emphasis> utility</para></listitem>
-	      <listitem><para>traces from the EyeSDN USB S0</para></listitem>
-	      <listitem><para>IPLog format from the Cisco Secure Intrusion Detection System</para></listitem>
-	      <listitem><para>pppd logs (pppdump format)</para></listitem>
-	      <listitem><para>the output from VMS's TCPIPtrace/TCPtrace/UCX$TRACE utilities</para></listitem>
-	      <listitem><para>the text output from the DBS Etherwatch VMS utility</para></listitem>
-	      <listitem><para>Visual Networks' Visual UpTime traffic capture</para></listitem>
-	      <listitem><para>the output from CoSine L2 debug</para></listitem>
-	      <listitem><para>the output from Accellent's 5Views LAN agents</para></listitem>
-	      <listitem><para>Endace Measurement Systems' ERF format captures</para></listitem>
-	      <listitem><para>Linux Bluez Bluetooth stack hcidump -w traces</para></listitem>
-	      <listitem><para>Catapult DCT2000 .out files</para></listitem>
-	      <listitem><para>Gammu generated text output from Nokia DCT3 phones in Netmonitor mode</para></listitem>
-	      <listitem><para>IBM Series (OS/400) Comm traces (ASCII &amp; UNICODE)</para></listitem>
-	      <listitem><para>Juniper Netscreen snoop captures</para></listitem>
-	      <listitem><para>Symbian OS btsnoop captures</para></listitem>
-	      <listitem><para>Tamosoft CommView captures</para></listitem>
-	      <listitem><para>Textronix K12xx 32bit .rf5 format captures</para></listitem>
-	      <listitem><para>Textronix K12 text file format captures</para></listitem>
-	      <listitem><para>Apple PacketLogger captures</para></listitem>
-	      <listitem><para>Captures from Aethra Telecommunications' PC108 software for their test instruments</para></listitem>
-	      <listitem><para>... new file formats are added from time to time</para></listitem>
-	</itemizedlist>
+    The following file formats from other capture tools can be opened by 
+    <application>Wireshark</application>:
+    <itemizedlist>
+          <listitem><para>libpcap - captures from <emphasis>Wireshark</emphasis>/<emphasis>TShark</emphasis>/<emphasis>dumpcap</emphasis>, <emphasis>tcpdump</emphasis>, and various other tools using libpcap's/tcpdump's capture format</para></listitem>
+          <listitem><para>pcap-ng - "next-generation" successor to libpcap format</para></listitem>
+          <listitem><para>Sun snoop and atmsnoop</para></listitem>
+          <listitem><para>Shomiti/Finisar <emphasis>Surveyor</emphasis> captures</para></listitem>
+          <listitem><para>Novell <emphasis>LANalyzer</emphasis> captures</para></listitem>
+          <listitem><para>Microsoft Network Monitor captures</para></listitem>
+          <listitem><para>AIX's iptrace captures</para></listitem>
+          <listitem><para>Cinco Networks NetXray captures</para></listitem>          
+          <listitem><para>Network Associates Windows-based Sniffer and Sniffer Pro captures</para></listitem>
+          <listitem><para>Network General/Network Associates DOS-based Sniffer (compressed or uncompressed) captures</para></listitem>
+          <listitem><para>AG Group/WildPackets EtherPeek/TokenPeek/AiroPeek/EtherHelp/PacketGrabber captures</para></listitem>
+          <listitem><para>RADCOM's WAN/LAN Analyzer captures</para></listitem>
+          <listitem><para>Network Instruments Observer version 9 captures</para></listitem>
+          <listitem><para>Lucent/Ascend router debug output</para></listitem>          
+          <listitem><para>HP-UX's nettl</para></listitem>
+          <listitem><para>Toshiba's ISDN routers dump output</para></listitem>
+          <listitem><para>ISDN4BSD <emphasis>i4btrace</emphasis> utility</para></listitem>
+          <listitem><para>traces from the EyeSDN USB S0</para></listitem>
+          <listitem><para>IPLog format from the Cisco Secure Intrusion Detection System</para></listitem>
+          <listitem><para>pppd logs (pppdump format)</para></listitem>
+          <listitem><para>the output from VMS's TCPIPtrace/TCPtrace/UCX$TRACE utilities</para></listitem>
+          <listitem><para>the text output from the DBS Etherwatch VMS utility</para></listitem>
+          <listitem><para>Visual Networks' Visual UpTime traffic capture</para></listitem>
+          <listitem><para>the output from CoSine L2 debug</para></listitem>
+          <listitem><para>the output from Accellent's 5Views LAN agents</para></listitem>
+          <listitem><para>Endace Measurement Systems' ERF format captures</para></listitem>
+          <listitem><para>Linux Bluez Bluetooth stack hcidump -w traces</para></listitem>
+          <listitem><para>Catapult DCT2000 .out files</para></listitem>
+          <listitem><para>Gammu generated text output from Nokia DCT3 phones in Netmonitor mode</para></listitem>
+          <listitem><para>IBM Series (OS/400) Comm traces (ASCII &amp; UNICODE)</para></listitem>
+          <listitem><para>Juniper Netscreen snoop captures</para></listitem>
+          <listitem><para>Symbian OS btsnoop captures</para></listitem>
+          <listitem><para>Tamosoft CommView captures</para></listitem>
+          <listitem><para>Textronix K12xx 32bit .rf5 format captures</para></listitem>
+          <listitem><para>Textronix K12 text file format captures</para></listitem>
+          <listitem><para>Apple PacketLogger captures</para></listitem>
+          <listitem><para>Captures from Aethra Telecommunications' PC108 software for their test instruments</para></listitem>
+          <listitem><para>... new file formats are added from time to time</para></listitem>
+    </itemizedlist>
     </para>
     <note><title>Opening a file may fail due to invalid packet types!</title>
-	<para>
-	It may not be possible to read some formats dependent on the packet types 
-	captured. Ethernet captures are usually supported for most file formats but
-	it may not be possible to read other packet types (e.g. token ring packets) 
-	from all file formats.
-	</para>
-	</note>
-	
+    <para>
+    It may not be possible to read some formats dependent on the packet types 
+    captured. Ethernet captures are usually supported for most file formats but
+    it may not be possible to read other packet types (e.g. token ring packets) 
+    from all file formats.
+    </para>
+    </note>
+    
   </section>
 
   </section>
@@ -328,360 +328,360 @@
       item from the File menu under Wireshark. You can choose which 
       packets to save and which file format to be used.
     </para>
-	<warning>
-	  <title>Saving may reduce the available information!</title>
-	  <para>
-	  Saving the captured packets will slightly reduce the amount of 
-	  information, e.g. the number of dropped packets will be lost;
-	  see <xref linkend="ChAppFilesCaptureFilesSection"/> for details.
-	  </para>
-	</warning>
+    <warning>
+      <title>Saving may reduce the available information!</title>
+      <para>
+      Saving the captured packets will slightly reduce the amount of 
+      information, e.g. the number of dropped packets will be lost;
+      see <xref linkend="ChAppFilesCaptureFilesSection"/> for details.
+      </para>
+    </warning>
     <section id="ChIOSaveAs">
       <title>The "Save Capture File As" dialog box</title>
       <para>
-	The "Save Capture File As" dialog box allows you to save 
-	the current capture to a file. 
-	<xref linkend="ChIOSaveFileTab"/> shows some examples of this 
-	  dialog box.
+    The "Save Capture File As" dialog box allows you to save 
+    the current capture to a file. 
+    <xref linkend="ChIOSaveFileTab"/> shows some examples of this 
+      dialog box.
       </para>
-	    <note>
-	      <title>The dialog appearance depends on your system!</title>
-	      <para>
-		  The appearance of this dialog depends on the system and GTK+ toolkit 
-		  version used. However, the functionality remains basically the same 
-		  on any particular system.
-	      </para>
-	    </note>
-		
+        <note>
+          <title>The dialog appearance depends on your system!</title>
+          <para>
+          The appearance of this dialog depends on the system and GTK+ toolkit 
+          version used. However, the functionality remains basically the same 
+          on any particular system.
+          </para>
+        </note>
+        
     <table id="ChIOSaveFileTab">
-	<title>The system specific "Save Capture File As" dialog box</title>
+    <title>The system specific "Save Capture File As" dialog box</title>
       <tgroup cols="2">
-	    <tbody>
-		<row>
-		<entry valign="top">
-		<para>
+        <tbody>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOSaveAsFileWin32">
-	<title>"Save" on native Windows</title>
-	<graphic entityref="WiresharkSaveAsDialogWin32" format="PNG"/>
+    <title>"Save" on native Windows</title>
+    <graphic entityref="WiresharkSaveAsDialogWin32" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Microsoft Windows</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Microsoft Windows</command></para>
       <para>
-		This is the common Windows file save dialog - 
-		plus some Wireshark extensions.
+        This is the common Windows file save dialog - 
+        plus some Wireshark extensions.
       </para>
-	    <para>
-		Specific for this dialog:
+        <para>
+        Specific for this dialog:
       </para>
-	<itemizedlist>
-	<listitem>
-	    <para>
-	      If available, the "Help" button will lead you to this section of 
-		  this "User's Guide".
-	    </para>
-	</listitem>
-	<listitem>
-	    <para>
-	      If you don't provide a file extension to the filename - e.g. .pcap, 
-		  Wireshark will append the standard file extension for that file 
-		  format.
-	    </para>
-	</listitem>
-	</itemizedlist>
-		</entry>
-		</row>
-		<row>
-		<entry valign="top">
-		<para>
+    <itemizedlist>
+    <listitem>
+        <para>
+          If available, the "Help" button will lead you to this section of 
+          this "User's Guide".
+        </para>
+    </listitem>
+    <listitem>
+        <para>
+          If you don't provide a file extension to the filename - e.g. .pcap, 
+          Wireshark will append the standard file extension for that file 
+          format.
+        </para>
+    </listitem>
+    </itemizedlist>
+        </entry>
+        </row>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOSaveAsFile2">
-	<title>"Save" - new GTK version</title>
-	<graphic entityref="WiresharkSaveAsDialog24" format="PNG"/>
+    <title>"Save" - new GTK version</title>
+    <graphic entityref="WiresharkSaveAsDialog24" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Unix/Linux: GTK version >= 2.4</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Unix/Linux: GTK version >= 2.4</command></para>
       <para>
-		This is the common Gimp/GNOME file save dialog - 
-		plus some Wireshark extensions.
+        This is the common Gimp/GNOME file save dialog - 
+        plus some Wireshark extensions.
       </para>
-	    <para>
-		Specific for this dialog:
+        <para>
+        Specific for this dialog:
       </para>
-	<itemizedlist>
-	<listitem>
-	    <para>
-		Clicking on the + at "Browse for other folders" will allow you 
-		to browse files and folders in your file system.
-	    </para>
-	</listitem>
-	</itemizedlist>
-		</entry>
-		</row>
-		<row>
-		<entry valign="top">
-		<para>
+    <itemizedlist>
+    <listitem>
+        <para>
+        Clicking on the + at "Browse for other folders" will allow you 
+        to browse files and folders in your file system.
+        </para>
+    </listitem>
+    </itemizedlist>
+        </entry>
+        </row>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOSaveAsFile1">
-	<title>"Save" - old GTK version</title>
-	<graphic entityref="WiresharkSaveAsDialog20" format="PNG"/>
+    <title>"Save" - old GTK version</title>
+    <graphic entityref="WiresharkSaveAsDialog20" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Unix/Linux: GTK version &lt; 2.4</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Unix/Linux: GTK version &lt; 2.4</command></para>
       <para>
-		This is the file save dialog of former Gimp/GNOME versions - 
-		plus some Wireshark extensions.
+        This is the file save dialog of former Gimp/GNOME versions - 
+        plus some Wireshark extensions.
       </para>
-		</entry>
-		</row>
+        </entry>
+        </row>
       </tbody>
       </tgroup>
     </table>
-		
+        
       <para>
-	With this dialog box, you can perform the following actions:
-	<orderedlist>
-	  <listitem>
-	    <para>
-	      Type in the name of the file you wish to save the captured 
-	      packets in, as a standard file name in your file system.
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-		Select the directory to save the file into.
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Select the range of the packets to be saved, see 
-		  <xref linkend="ChIOPacketRangeSection"/>
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Specify the format of the saved capture file by clicking on 
-	      the File type drop down box. You can choose from the 
-	      types, described in <xref linkend="ChIOOutputFormatsSection"/>.
-		</para>
-	    <note>
-	      <title>The selection of capture formats may be reduced!</title>
-	      <para>
-		Some capture formats may not be available, depending on the 
-		packet types captured.
-	      </para>
-	    </note>
-	    <tip>
-	      <title>File formats can be converted!</title>
-	      <para>
-		You can convert capture files from one format to another 
-		by reading in a capture file and writing it out using a 
-		different format.
-	      </para>
-	    </tip>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Click on the Save/Ok button to accept your selected file and save to 
-		  it. If Wireshark has a problem saving the captured packets to 
-	      the file you specified, it will display an error dialog box. 
-	      After clicking OK on that error dialog box, you can try again. 
-	    </para>
-	  </listitem>
-	  <listitem>
-	    <para>
-	      Click on the Cancel button to go back to Wireshark and not save the 
-	      captured packets.
-	    </para>
-	  </listitem>
-	</orderedlist>
+    With this dialog box, you can perform the following actions:
+    <orderedlist>
+      <listitem>
+        <para>
+          Type in the name of the file you wish to save the captured 
+          packets in, as a standard file name in your file system.
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+        Select the directory to save the file into.
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Select the range of the packets to be saved, see 
+          <xref linkend="ChIOPacketRangeSection"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Specify the format of the saved capture file by clicking on 
+          the File type drop down box. You can choose from the 
+          types, described in <xref linkend="ChIOOutputFormatsSection"/>.
+        </para>
+        <note>
+          <title>The selection of capture formats may be reduced!</title>
+          <para>
+        Some capture formats may not be available, depending on the 
+        packet types captured.
+          </para>
+        </note>
+        <tip>
+          <title>File formats can be converted!</title>
+          <para>
+        You can convert capture files from one format to another 
+        by reading in a capture file and writing it out using a 
+        different format.
+          </para>
+        </tip>
+      </listitem>
+      <listitem>
+        <para>
+          Click on the Save/Ok button to accept your selected file and save to 
+          it. If Wireshark has a problem saving the captured packets to 
+          the file you specified, it will display an error dialog box. 
+          After clicking OK on that error dialog box, you can try again. 
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Click on the Cancel button to go back to Wireshark and not save the 
+          captured packets.
+        </para>
+      </listitem>
+    </orderedlist>
       </para>
     </section>
   <section id="ChIOOutputFormatsSection">
     <title>Output File Formats</title>
     <para>
-	Wireshark can save the packet data in its "native" file format (libpcap) 
-	and in the file formats of some other protocol analyzers, so other tools 
-	can read the capture data.
+    Wireshark can save the packet data in its "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>File formats have different time stamp accuracies!</title>
-	<para>
-	Saving from the currently used file format to a different format may reduce the 
-	time stamp accuracy; see the <xref linkend="ChAdvTimestamps"/> for details.
-	</para>
-	</warning>
+    <warning><title>File formats have different time stamp accuracies!</title>
     <para>
-	The following file formats can be saved by <application>Wireshark</application> (with the known file extensions):
-	<itemizedlist>
-	      <listitem><para>libpcap, tcpdump and various other tools using tcpdump's capture format (*.pcap,*.cap,*.dmp)</para></listitem>
-	      <listitem><para>Accellent 5Views (*.5vw)</para></listitem>
-	      <listitem><para>HP-UX's nettl (*.TRC0,*.TRC1)</para></listitem>
-	      <listitem><para>Microsoft Network Monitor - NetMon (*.cap)</para></listitem>
-	      <listitem><para>Network Associates Sniffer - DOS (*.cap,*.enc,*.trc,*fdc,*.syc)</para></listitem>
-	      <listitem><para>Network Associates Sniffer - Windows (*.cap)</para></listitem>
-	      <listitem><para>Network Instruments Observer version 9 (*.bfr)</para></listitem>
-	      <listitem><para>Novell LANalyzer (*.tr1)</para></listitem>
-	      <listitem><para>Sun snoop (*.snoop,*.cap)</para></listitem>
-	      <listitem><para>Visual Networks Visual UpTime traffic (*.*)</para></listitem>
-	      <listitem><para>... new file formats are added from time to time</para></listitem>
-	</itemizedlist>
+    Saving from the currently used file format to a different format may reduce the 
+    time stamp accuracy; see the <xref linkend="ChAdvTimestamps"/> for details.
     </para>
+    </warning>
     <para>
-	If the above tools will be more helpful than Wireshark is a different question ;-)
+    The following file formats can be saved by <application>Wireshark</application> (with the known file extensions):
+    <itemizedlist>
+          <listitem><para>libpcap, tcpdump and various other tools using tcpdump's capture format (*.pcap,*.cap,*.dmp)</para></listitem>
+          <listitem><para>Accellent 5Views (*.5vw)</para></listitem>
+          <listitem><para>HP-UX's nettl (*.TRC0,*.TRC1)</para></listitem>
+          <listitem><para>Microsoft Network Monitor - NetMon (*.cap)</para></listitem>
+          <listitem><para>Network Associates Sniffer - DOS (*.cap,*.enc,*.trc,*fdc,*.syc)</para></listitem>
+          <listitem><para>Network Associates Sniffer - Windows (*.cap)</para></listitem>
+          <listitem><para>Network Instruments Observer version 9 (*.bfr)</para></listitem>
+          <listitem><para>Novell LANalyzer (*.tr1)</para></listitem>
+          <listitem><para>Sun snoop (*.snoop,*.cap)</para></listitem>
+          <listitem><para>Visual Networks Visual UpTime traffic (*.*)</para></listitem>
+          <listitem><para>... new file formats are added from time to time</para></listitem>
+    </itemizedlist>
     </para>
-	<note><title>Third party protocol analyzers may require specific file extensions!</title>
-	<para>
-	Other protocol analyzers than Wireshark may require that the file has a 
-	certain file extension in order to read the files you generate with Wireshark, e.g.:
-	</para>
-	<para>
-	".cap" for Network Associates Sniffer - Windows
-	</para>
-	</note>
-  </section>	
+    <para>
+    If the above tools will be more helpful than Wireshark is a different question ;-)
+    </para>
+    <note><title>Third party protocol analyzers may require specific file extensions!</title>
+    <para>
+    Other protocol analyzers than Wireshark may require that the file has a 
+    certain file extension in order to read the files you generate with Wireshark, e.g.:
+    </para>
+    <para>
+    ".cap" for Network Associates Sniffer - Windows
+    </para>
+    </note>
+  </section>    
   </section>
   
   <section id="ChIOMergeSection"><title>Merging capture files</title>
-	<para>
-	Sometimes you need to merge several capture files into one. For example 
-	this can be useful, if you have captured simultaneously from multiple 
-	interfaces at once (e.g. using multiple instances of Wireshark).
-	</para>
-	<para>
-	Merging capture files can be done in three ways:
-	<itemizedlist>
-		<listitem><para>
-		Use the <command>menu item "Merge"</command> from the "File" menu, 
-		to open the merge dialog, see <xref linkend="ChIOMergeDialog"/>.
-		This menu item will be disabled, until you have loaded a capture file.
-		</para></listitem>
-		<listitem><para>
-	  	Use <command>drag-and-drop</command> to drop multiple files on the 
-		main window. Wireshark will try to merge the packets in chronological 
-		order from the dropped files into a newly created temporary file. If 
-		you drop only a single file, it will simply replace a (maybe) existing
-		one.
-		</para></listitem>
-		<listitem><para>
-	  	Use the <command>mergecap</command> tool, which is a command 
-		line tool to merge capture files. This tool provides the most options 
-		to merge capture files, see <xref linkend="AppToolsmergecap"/>.
-		</para></listitem>
-	</itemizedlist>
-	</para>
-	<section id="ChIOMergeDialog">
-	<title>The "Merge with Capture File" dialog box</title>
-	<para>
-	
-	This dialog box let you select a file to be merged into the currently 
-	loaded file.
-	</para>
-	<note><title>You will be prompted for an unsaved file first!</title>
-	<para>If your current data wasn't saved before, you will be asked to save 
-	it first, before this dialog box is shown.</para>
-	</note>
-	
-	<para>
-	Most controls of this dialog will work the same way as described in the 
-	"Open Capture File" dialog box, see <xref linkend="ChIOOpen"/>.
-	</para>
-	<para>
-	Specific controls of this merge dialog are:
-	</para>
-	
-	<variablelist>
-	<varlistentry>
-	  <term><command>Prepend packets to existing file</command></term>
-	  <listitem>
-	    <para>
-		Prepend the packets from the selected file before the currently loaded 
-		packets.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>Merge packets chronologically</command></term>
-	  <listitem>
-	    <para>
-		Merge both the packets from the selected and currently loaded file in 
-		chronological order.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>Append packets to existing file</command></term>
-	  <listitem>
-	    <para>
-		Append the packets from the selected file after the currently loaded 
-		packets.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	</variablelist>
-	
+    <para>
+    Sometimes you need to merge several capture files into one. For example 
+    this can be useful, if you have captured simultaneously from multiple 
+    interfaces at once (e.g. using multiple instances of Wireshark).
+    </para>
+    <para>
+    Merging capture files can be done in three ways:
+    <itemizedlist>
+        <listitem><para>
+        Use the <command>menu item "Merge"</command> from the "File" menu, 
+        to open the merge dialog, see <xref linkend="ChIOMergeDialog"/>.
+        This menu item will be disabled, until you have loaded a capture file.
+        </para></listitem>
+        <listitem><para>
+          Use <command>drag-and-drop</command> to drop multiple files on the 
+        main window. Wireshark will try to merge the packets in chronological 
+        order from the dropped files into a newly created temporary file. If 
+        you drop only a single file, it will simply replace a (maybe) existing
+        one.
+        </para></listitem>
+        <listitem><para>
+          Use the <command>mergecap</command> tool, which is a command 
+        line tool to merge capture files. This tool provides the most options 
+        to merge capture files, see <xref linkend="AppToolsmergecap"/>.
+        </para></listitem>
+    </itemizedlist>
+    </para>
+    <section id="ChIOMergeDialog">
+    <title>The "Merge with Capture File" dialog box</title>
+    <para>
+    
+    This dialog box let you select a file to be merged into the currently 
+    loaded file.
+    </para>
+    <note><title>You will be prompted for an unsaved file first!</title>
+    <para>If your current data wasn't saved before, you will be asked to save 
+    it first, before this dialog box is shown.</para>
+    </note>
+    
+    <para>
+    Most controls of this dialog will work the same way as described in the 
+    "Open Capture File" dialog box, see <xref linkend="ChIOOpen"/>.
+    </para>
+    <para>
+    Specific controls of this merge dialog are:
+    </para>
+    
+    <variablelist>
+    <varlistentry>
+      <term><command>Prepend packets to existing file</command></term>
+      <listitem>
+        <para>
+        Prepend the packets from the selected file before the currently loaded 
+        packets.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>Merge packets chronologically</command></term>
+      <listitem>
+        <para>
+        Merge both the packets from the selected and currently loaded file in 
+        chronological order.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>Append packets to existing file</command></term>
+      <listitem>
+        <para>
+        Append the packets from the selected file after the currently loaded 
+        packets.
+        </para>
+      </listitem>
+    </varlistentry>
+    </variablelist>
+    
     <table id="ChIOMergeFileTab">
-	<title>The system specific "Merge Capture File As" dialog box</title>
+    <title>The system specific "Merge Capture File As" dialog box</title>
       <tgroup cols="2">
-	    <tbody>
-		<row>
-		<entry valign="top">
-		<para>
+        <tbody>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOMergeFileWin32">
-	<title>"Merge" on native Windows</title>
-	<graphic entityref="WiresharkMergeDialogWin32" format="PNG"/>
+    <title>"Merge" on native Windows</title>
+    <graphic entityref="WiresharkMergeDialogWin32" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Microsoft Windows</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Microsoft Windows</command></para>
       <para>
-		This is the common Windows file open dialog - 
-		plus some Wireshark extensions.
+        This is the common Windows file open dialog - 
+        plus some Wireshark extensions.
       </para>
-		</entry>
-		</row>
-		<row>
-		<entry valign="top">
-		<para>
+        </entry>
+        </row>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOMergeFile2">
-	<title>"Merge" - new GTK version</title>
-	<graphic entityref="WiresharkMergeDialog24" format="PNG"/>
+    <title>"Merge" - new GTK version</title>
+    <graphic entityref="WiresharkMergeDialog24" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Unix/Linux: GTK version >= 2.4</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Unix/Linux: GTK version >= 2.4</command></para>
       <para>
-		This is the common Gimp/GNOME file open dialog - 
-		plus some Wireshark extensions.
+        This is the common Gimp/GNOME file open dialog - 
+        plus some Wireshark extensions.
       </para>
-		</entry>
-		</row>
-		<row>
-		<entry valign="top">
-		<para>
+        </entry>
+        </row>
+        <row>
+        <entry valign="top">
+        <para>
       <figure id="ChIOMergeFile1">
-	<title>"Merge" - old GTK version</title>
-	<graphic entityref="WiresharkMergeDialog20" format="PNG"/>
+    <title>"Merge" - old GTK version</title>
+    <graphic entityref="WiresharkMergeDialog20" format="PNG"/>
       </figure>
-		</para>
-		</entry>
-		<entry valign="top">
-		<para><command>Unix/Linux: GTK version &lt; 2.4</command></para>
+        </para>
+        </entry>
+        <entry valign="top">
+        <para><command>Unix/Linux: GTK version &lt; 2.4</command></para>
       <para>
-		This is the file open dialog of former Gimp/GNOME versions - 
-		plus some Wireshark extensions.
+        This is the file open dialog of former Gimp/GNOME versions - 
+        plus some Wireshark extensions.
       </para>
-		</entry>
-		</row>
+        </entry>
+        </row>
       </tbody>
       </tgroup>
     </table>
 
-	</section>
+    </section>
   </section>
 
   <section id="ChIOImportSection"><title>Import text file</title>
@@ -742,12 +742,12 @@
     before each packet. This allows Wireshark or any other full-packet decoder to
     handle these dumps.
     </para>
-  	<section id="ChIOImportDialog">
-	  <title>The "File import" dialog box</title>
-	  <para>
-	  This dialog box lets you select a file to be imported and set import parameters.
-	  </para>
-	  <para>
+      <section id="ChIOImportDialog">
+      <title>The "File import" dialog box</title>
+      <para>
+      This dialog box lets you select a file to be imported and set import parameters.
+      </para>
+      <para>
     <figure id="ChIOFileImportDialog">
       <title>The "File Import" dialog</title>
       <graphic entityref="WiresharkFileImportDialog" format="PNG"/>
@@ -768,9 +768,9 @@
         </varlistentry>
         </variablelist>
     </para>
-	  <para>
-	  The input parameters are as follows:
-	  </para>
+      <para>
+      The input parameters are as follows:
+      </para>
     <variablelist>
     <varlistentry>
       <term><command>Filename / Browse</command></term>
@@ -813,9 +813,9 @@
       </listitem>
     </varlistentry>
     </variablelist>
-	  <para>
-	  The import parameters are as follows:
-	  </para>
+      <para>
+      The import parameters are as follows:
+      </para>
     <variablelist>
     <varlistentry>
       <term><command>Encapsulation type</command></term>
@@ -855,8 +855,8 @@
     to start the import.
     </para>
     <para>
-	  <note><title>You will be prompted for an unsaved file first!</title>
-	  <para>If your current data wasn't saved before, you will be asked to save 
+      <note><title>You will be prompted for an unsaved file first!</title>
+      <para>If your current data wasn't saved before, you will be asked to save 
     it first, before this dialog box is shown.</para>
     </note>
     </para>
@@ -870,374 +870,374 @@
   <section id="ChIOFileSetSection"><title>File Sets</title>
     <para>
       When using the "Multiple Files" option while doing a capture
-	  (see: <xref linkend="ChCapCaptureFiles"/>), 
-	  the capture data is spread over several capture files, called a file 
-	  set. 
+      (see: <xref linkend="ChCapCaptureFiles"/>), 
+      the capture data is spread over several capture files, called a file 
+      set. 
     </para>
     <para>
-	  As it can become tedious to work with a file set by hand, Wireshark 
-	  provides some features to handle these file sets in a convenient way.
+      As it can become tedious to work with a file set by hand, Wireshark 
+      provides some features to handle these file sets in a convenient way.
     </para>
     <sidebar><title>How does Wireshark detect the files of a file set?</title>
     <para>
-	  A filename in a file set uses the format Prefix_Number_DateTimeSuffix 
-	  which might look like this: "test_00001_20060420183910.pcap".
-	  All files of a file set share the same prefix (e.g. "test") and suffix 
-	  (e.g. ".pcap") and a varying middle part.
+      A filename in a file set uses the format Prefix_Number_DateTimeSuffix 
+      which might look like this: "test_00001_20060420183910.pcap".
+      All files of a file set share the same prefix (e.g. "test") and suffix 
+      (e.g. ".pcap") and a varying middle part.
     </para>
     <para>
-	  To find the files of a file set, Wireshark scans the directory where the 
-	  currently loaded file resides and checks for files matching the filename 
-	  pattern (prefix and suffix) of the currently loaded file. 
+      To find the files of a file set, Wireshark scans the directory where the 
+      currently loaded file resides and checks for files matching the filename 
+      pattern (prefix and suffix) of the currently loaded file. 
     </para>
     <para>
-	  This simple mechanism usually works well, but has its drawbacks. If several 
-	  file sets were captured with the same prefix and suffix, Wireshark will detect 
-	  them as a single file set. If files were renamed or spread over several 
-	  directories the mechanism will fail to find all files of a set.
+      This simple mechanism usually works well, but has its drawbacks. If several 
+      file sets were captured with the same prefix and suffix, Wireshark will detect 
+      them as a single file set. If files were renamed or spread over several 
+      directories the mechanism will fail to find all files of a set.
     </para>
-	</sidebar>
+    </sidebar>
     <para>
-	  The following features in the "File Set" submenu of the "File" menu are 
-	  available to work with file sets in a convenient way:
+      The following features in the "File Set" submenu of the "File" menu are 
+      available to work with file sets in a convenient way:
     </para>
-	<itemizedlist>
-		<listitem><para>
-		The <command>List Files</command> dialog box will list the files 
-		Wireshark has recognized as being part of the current file set.
-		</para></listitem>
-		<listitem><para>
-		<command>Next File</command> closes the current and opens the next 
-		file in the file set.
-		</para></listitem>
-		<listitem><para>
-		<command>Previous File</command> closes the current and opens the 
-		previous file in the file set.
-		</para></listitem>
-	</itemizedlist>
-	<section id="ChIOFileSetListDialog">
-	<title>The "List Files" dialog box</title>
+    <itemizedlist>
+        <listitem><para>
+        The <command>List Files</command> dialog box will list the files 
+        Wireshark has recognized as being part of the current file set.
+        </para></listitem>
+        <listitem><para>
+        <command>Next File</command> closes the current and opens the next 
+        file in the file set.
+        </para></listitem>
+        <listitem><para>
+        <command>Previous File</command> closes the current and opens the 
+        previous file in the file set.
+        </para></listitem>
+    </itemizedlist>
+    <section id="ChIOFileSetListDialog">
+    <title>The "List Files" dialog box</title>
     <figure>
       <title>The "List Files" dialog box</title>
       <graphic entityref="WiresharkFileSetDialog" format="PNG"/>
     </figure>
-	  <para>
-	  Each line contains information about a file of the file set:
-	<itemizedlist>
-		<listitem><para>
-		<command>Filename</command> the name of the file. If you click on 
-		the filename (or the radio button left to it), the current file will
-		be closed and the corresponding capture file will be opened. 
-		</para></listitem>
-		<listitem><para>
-		<command>Created</command> the creation time of the file
-		</para></listitem>
-		<listitem><para>
-		<command>Last Modified</command> the last time the file was modified
-		</para></listitem>
-		<listitem><para>
-		<command>Size</command> the size of the file
-		</para></listitem>
-	</itemizedlist>
-	  The last line will contain info about the currently used directory where
-	  all of the files in the file set can be found.
-	  </para>
-	  <para>
-	  The content of this dialog box is updated each time a capture file is 
-	  opened/closed.
-	  </para>
-	  <para>
-	  The Close button will, well, close the dialog box.
-	  </para>
-	</section>
+      <para>
+      Each line contains information about a file of the file set:
+    <itemizedlist>
+        <listitem><para>
+        <command>Filename</command> the name of the file. If you click on 
+        the filename (or the radio button left to it), the current file will
+        be closed and the corresponding capture file will be opened. 
+        </para></listitem>
+        <listitem><para>
+        <command>Created</command> the creation time of the file
+        </para></listitem>
+        <listitem><para>
+        <command>Last Modified</command> the last time the file was modified
+        </para></listitem>
+        <listitem><para>
+        <command>Size</command> the size of the file
+        </para></listitem>
+    </itemizedlist>
+      The last line will contain info about the currently used directory where
+      all of the files in the file set can be found.
+      </para>
+      <para>
+      The content of this dialog box is updated each time a capture file is 
+      opened/closed.
+      </para>
+      <para>
+      The Close button will, well, close the dialog box.
+      </para>
+    </section>
   </section>
   <section id="ChIOExportSection"><title>Exporting data</title>
     <para>
       Wireshark provides several ways and formats to export packet data. This 
-	  section describes general ways to export data from Wireshark.
+      section describes general ways to export data from Wireshark.
+    </para>
+    <note><title>Note!</title>
+    <para>
+      There are more specialized functions to export specific data, 
+      which will be described at the appropriate places. 
     </para>
-	<note><title>Note!</title>
-	<para>
-	  There are more specialized functions to export specific data, 
-	  which will be described at the appropriate places. 
-	</para>
-	</note>
+    </note>
     <para>
-	  XXX - add detailed descriptions of the output formats and some sample 
-	  output, too.
+      XXX - add detailed descriptions of the output formats and some sample 
+      output, too.
     </para>
-	<section id="ChIOExportPlainDialog">
-	<title>The "Export as Plain Text File" dialog box</title>
-	  <para id="ChIOExportPlain">
-	    Export packet data into a plain ASCII text file, much like the format 
-		used to print packets.
+    <section id="ChIOExportPlainDialog">
+    <title>The "Export as Plain Text File" dialog box</title>
+      <para id="ChIOExportPlain">
+        Export packet data into a plain ASCII text file, much like the format 
+        used to print packets.
     <figure>
       <title>The "Export as Plain Text File" dialog box</title>
       <graphic entityref="WiresharkExportPlainDialog" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Export to file:</command> frame chooses the file to export 
-		the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Range</command> frame is described in <xref 
-		linkend="ChIOPacketRangeSection"/>.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Details</command> frame is described in <xref 
-		linkend="ChIOPacketFormatSection"/>.
-		</para></listitem>
-	</itemizedlist>	
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Details</command> frame is described in <xref 
+        linkend="ChIOPacketFormatSection"/>.
+        </para></listitem>
+    </itemizedlist>    
+      </para>
     </section>
-	<section id="ChIOExportPSDialog">
-	<title>The "Export as PostScript File" dialog box</title>
-	  <para>
-	    Export packet data into PostScript, much like the format used 
-		to print packets.
-	<tip><title>Tip!</title>
-	<para>
-	You can easily convert PostScript files to PDF files using ghostscript.
-	For example: export to a file named foo.ps and then call: 
-	<command>ps2pdf foo.ps</command>
-	</para>
-	</tip>
+    <section id="ChIOExportPSDialog">
+    <title>The "Export as PostScript File" dialog box</title>
+      <para>
+        Export packet data into PostScript, much like the format used 
+        to print packets.
+    <tip><title>Tip!</title>
+    <para>
+    You can easily convert PostScript files to PDF files using ghostscript.
+    For example: export to a file named foo.ps and then call: 
+    <command>ps2pdf foo.ps</command>
+    </para>
+    </tip>
     <figure>
       <title>The "Export as PostScript File" dialog box</title>
       <graphic entityref="WiresharkExportPSDialog" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Export to file:</command> frame chooses the file to export 
-		the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Range</command> frame is described in <xref 
-		linkend="ChIOPacketRangeSection"/>.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Details</command> frame is described in <xref 
-		linkend="ChIOPacketFormatSection"/>.
-		</para></listitem>
-	</itemizedlist>	
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Details</command> frame is described in <xref 
+        linkend="ChIOPacketFormatSection"/>.
+        </para></listitem>
+    </itemizedlist>    
+      </para>
     </section>
-	<section id="ChIOExportCSVDialog">
-	<title>The "Export as CSV (Comma Separated Values) File" dialog box</title>
-	  <para>XXX - add screenshot</para>
-	  <para>
-	    Export packet summary into CSV, used e.g. by spreadsheet programs to 
-		im-/export data.
+    <section id="ChIOExportCSVDialog">
+    <title>The "Export as CSV (Comma Separated Values) File" dialog box</title>
+      <para>XXX - add screenshot</para>
+      <para>
+        Export packet summary into CSV, used e.g. by spreadsheet programs to 
+        im-/export data.
     <!--<figure>
       <title>The "Export as Comma Separated Values File" dialog box</title>
       <graphic entityref="WiresharkExportCSVDialog" format="PNG"/>
     </figure>-->
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Export to file:</command> frame chooses the file to export 
-		the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Range</command> frame is described in <xref 
-		linkend="ChIOPacketRangeSection"/>.
-		</para></listitem>
-	</itemizedlist>	
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+        </para></listitem>
+    </itemizedlist>    
+      </para>
     </section>
     <section id="ChIOExportCArraysDialog">
       <title>The "Export as C Arrays (packet bytes) file" dialog box</title>
       <para>XXX - add screenshot</para>
       <para>
-	Export packet bytes into C arrays so you can import the stream data
-	into your own C program.
-	<!--
-	    <figure>
-	    <title>The "Export as C Arrays (packet bytes) file" dialog box</title>
-	    <graphic entityref="WiresharkExportCArraysDialog" format="PNG"/>
-	    </figure>
-	-->
-	<itemizedlist>
-	  <listitem><para>
-	    <command>Export to file:</command> frame chooses the file to export 
-	    the packet data to.
-	  </para></listitem>
-	  <listitem><para>
-	    The <command>Packet Range</command> frame is described in <xref 
-	    linkend="ChIOPacketRangeSection"/>.
-	  </para></listitem>
-	</itemizedlist>	
+    Export packet bytes into C arrays so you can import the stream data
+    into your own C program.
+    <!--
+        <figure>
+        <title>The "Export as C Arrays (packet bytes) file" dialog box</title>
+        <graphic entityref="WiresharkExportCArraysDialog" format="PNG"/>
+        </figure>
+    -->
+    <itemizedlist>
+      <listitem><para>
+        <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+      </para></listitem>
+      <listitem><para>
+        The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+      </para></listitem>
+    </itemizedlist>    
       </para>
     </section>
-	<section id="ChIOExportPSMLDialog">
-	<title>The "Export as PSML File" dialog box</title>
-	  <para>
-	    Export packet data into PSML. This is an XML based format including 
-		only the packet summary. The PSML file specification is available at: 
-		<ulink url="http://www.nbee.org/doku.php?id=netpdl:psml_specification"/>.
+    <section id="ChIOExportPSMLDialog">
+    <title>The "Export as PSML File" dialog box</title>
+      <para>
+        Export packet data into PSML. This is an XML based format including 
+        only the packet summary. The PSML file specification is available at: 
+        <ulink url="http://www.nbee.org/doku.php?id=netpdl:psml_specification"/>.
     <figure>
       <title>The "Export as PSML File" dialog box</title>
       <graphic entityref="WiresharkExportPSMLDialog" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Export to file:</command> frame chooses the file to export 
-		the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Range</command> frame is described in <xref 
-		linkend="ChIOPacketRangeSection"/>.
-		</para></listitem>
-	</itemizedlist>	
-	There's no such thing as a packet details frame for PSML export, as the 
-	packet format is defined by the PSML specification.
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+        </para></listitem>
+    </itemizedlist>    
+    There's no such thing as a packet details frame for PSML export, as the 
+    packet format is defined by the PSML specification.
+      </para>
     </section>
-	<section id="ChIOExportPDMLDialog">
-	<title>The "Export as PDML File" dialog box</title>
-	  <para>
-	    Export packet data into PDML. This is an XML based format including 
-		the packet details. The PDML file specification is available at: 
-		<ulink url="http://www.nbee.org/doku.php?id=netpdl:pdml_specification"/>.
-		<note><title></title>
-		<para>
-		The PDML specification is not officially released and Wireshark's 
-		implementation of it is still in an early beta state, so please expect 
-		changes in future Wireshark versions.
-		</para>
-		</note>
+    <section id="ChIOExportPDMLDialog">
+    <title>The "Export as PDML File" dialog box</title>
+      <para>
+        Export packet data into PDML. This is an XML based format including 
+        the packet details. The PDML file specification is available at: 
+        <ulink url="http://www.nbee.org/doku.php?id=netpdl:pdml_specification"/>.
+        <note><title></title>
+        <para>
+        The PDML specification is not officially released and Wireshark's 
+        implementation of it is still in an early beta state, so please expect 
+        changes in future Wireshark versions.
+        </para>
+        </note>
     <figure>
       <title>The "Export as PDML File" dialog box</title>
       <graphic entityref="WiresharkExportPDMLDialog" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Export to file:</command> frame chooses the file to export 
-		the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Packet Range</command> frame is described in <xref 
-		linkend="ChIOPacketRangeSection"/>.
-		</para></listitem>
-	</itemizedlist>	
-	There's no such thing as a packet details frame for PDML export, as the 
-	packet format is defined by the PDML specification.
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Export to file:</command> frame chooses the file to export 
+        the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Packet Range</command> frame is described in <xref 
+        linkend="ChIOPacketRangeSection"/>.
+        </para></listitem>
+    </itemizedlist>    
+    There's no such thing as a packet details frame for PDML export, as the 
+    packet format is defined by the PDML specification.
+      </para>
   </section>
-	<section id="ChIOExportSelectedDialog">
-	<title>The "Export selected packet bytes" dialog box</title>
-	  <para>
-	    Export the bytes selected in the "Packet Bytes" pane into a raw 
-		binary file.
+    <section id="ChIOExportSelectedDialog">
+    <title>The "Export selected packet bytes" dialog box</title>
+      <para>
+        Export the bytes selected in the "Packet Bytes" pane into a raw 
+        binary file.
     <figure>
       <title>The "Export Selected Packet Bytes" dialog box</title>
       <graphic entityref="WiresharkExportSelectedDialog" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem><para>
-	  	<command>Name:</command> the filename to export the packet data to.
-		</para></listitem>
-		<listitem><para>
-	  	The <command>Save in folder:</command> field lets you select the 
-		folder to save to (from some predefined folders).
-		</para></listitem>
-		<listitem><para>
-	  	<command>Browse for other folders</command> provides a flexible 
-		way to choose a folder.
-		</para></listitem>
-	</itemizedlist>	
-	  </para>
+    <itemizedlist>
+        <listitem><para>
+          <command>Name:</command> the filename to export the packet data to.
+        </para></listitem>
+        <listitem><para>
+          The <command>Save in folder:</command> field lets you select the 
+        folder to save to (from some predefined folders).
+        </para></listitem>
+        <listitem><para>
+          <command>Browse for other folders</command> provides a flexible 
+        way to choose a folder.
+        </para></listitem>
+    </itemizedlist>    
+      </para>
   </section>
-	<section id="ChIOExportObjectsDialog">
-	<title>The "Export Objects" dialog box</title>
-	  <para>
-	    This feature scans through HTTP streams in the currently
-	    open capture file or running capture and takes reassembled
-	    objects such as HTML documents, image files, executables
-	    and anything else that can be transferred over HTTP and
-	    lets you save them to disk.  If you have a capture
-	    running, this list is automatically updated every few
-	    seconds with any new objects seen.  The saved objects can then be
-	    opened with the proper viewer or executed in the case of
-	    executables (if it is for the same platform you are
-	    running Wireshark on) without any further work on your
-	    part.  This feature is not available when using GTK2 versions 
-		below 2.4.
-	  </para>
+    <section id="ChIOExportObjectsDialog">
+    <title>The "Export Objects" dialog box</title>
+      <para>
+        This feature scans through HTTP streams in the currently
+        open capture file or running capture and takes reassembled
+        objects such as HTML documents, image files, executables
+        and anything else that can be transferred over HTTP and
+        lets you save them to disk.  If you have a capture
+        running, this list is automatically updated every few
+        seconds with any new objects seen.  The saved objects can then be
+        opened with the proper viewer or executed in the case of
+        executables (if it is for the same platform you are
+        running Wireshark on) without any further work on your
+        part.  This feature is not available when using GTK2 versions 
+        below 2.4.
+      </para>
     <figure>
       <title>The "Export Objects" dialog box</title>
       <graphic entityref="WiresharkExportObjectsDialog" format="PNG"/>
     </figure>
     
-	<itemizedlist>
-	  <para>Columns:</para>
-		<listitem><para>
-	  	<command>Packet num:</command> The packet number in
-	  	which this object was found.  In some cases, there can
-	  	be multiple objects in the same packet.
-		</para></listitem>
+    <itemizedlist>
+      <para>Columns:</para>
+        <listitem><para>
+          <command>Packet num:</command> The packet number in
+          which this object was found.  In some cases, there can
+          be multiple objects in the same packet.
+        </para></listitem>
 
-		<listitem><para>
-		<command>Hostname:</command> The hostname of the
-		server that sent the object as a response to an HTTP request.
-		</para></listitem>
+        <listitem><para>
+        <command>Hostname:</command> The hostname of the
+        server that sent the object as a response to an HTTP request.
+        </para></listitem>
 
-		<listitem><para>
-		<command>Content Type:</command> The HTTP content type
-		of this object.
-		</para></listitem>
+        <listitem><para>
+        <command>Content Type:</command> The HTTP content type
+        of this object.
+        </para></listitem>
 
-		<listitem><para>
-		<command>Bytes:</command> The size of this object in bytes.
-		</para></listitem>
+        <listitem><para>
+        <command>Bytes:</command> The size of this object in bytes.
+        </para></listitem>
 
-		<listitem><para>
-		<command>Filename:</command> The final part of the URI
-		(after the last slash).  This is typically a filename,
-		but may be a long complex looking string, which
-		typically indicates that the file was received in response to
-		a HTTP POST request.
-		</para></listitem>
-	</itemizedlist>	
+        <listitem><para>
+        <command>Filename:</command> The final part of the URI
+        (after the last slash).  This is typically a filename,
+        but may be a long complex looking string, which
+        typically indicates that the file was received in response to
+        a HTTP POST request.
+        </para></listitem>
+    </itemizedlist>    
 
-	<itemizedlist>
-	  <para>Buttons:</para>
-		<listitem><para>
-	  	<command>Help:</command> Opens this section in the
-	  	user's guide.
-		</para></listitem>
+    <itemizedlist>
+      <para>Buttons:</para>
+        <listitem><para>
+          <command>Help:</command> Opens this section in the
+          user's guide.
+        </para></listitem>
 
-		<listitem><para>
-	  	<command>Close:</command> Closes this dialog.
-		</para></listitem>
+        <listitem><para>
+          <command>Close:</command> Closes this dialog.
+        </para></listitem>
 
-		<listitem><para>
-	  	<command>Save As:</command> Saves the currently
-	  	selected object as a filename you specify.  The
-	  	default filename to save as is taken from the filename
-	  	column of the objects list.
-		</para></listitem>
+        <listitem><para>
+          <command>Save As:</command> Saves the currently
+          selected object as a filename you specify.  The
+          default filename to save as is taken from the filename
+          column of the objects list.
+        </para></listitem>
 
-		<listitem><para>
-	  	<command>Save All:</command> Saves all objects in the
-	  	list using the filename from the filename column.  You
-	  	will be asked what directory / folder to save them
-	  	in.  If	the filename is invalid for the operating system /
-	  	file system you are running Wireshark on, then an error
-	  	will appear and that object will not be saved (but all
-	  	of the others will be).
-		</para></listitem>
-	</itemizedlist>
-	</section>
+        <listitem><para>
+          <command>Save All:</command> Saves all objects in the
+          list using the filename from the filename column.  You
+          will be asked what directory / folder to save them
+          in.  If    the filename is invalid for the operating system /
+          file system you are running Wireshark on, then an error
+          will appear and that object will not be saved (but all
+          of the others will be).
+        </para></listitem>
+    </itemizedlist>
+    </section>
   </section>
 
   <section id="ChIOPrintSection"><title>Printing packets</title>
     <para>
-	    To print packets, select the "Print..." menu item from the File menu. 
-		When you do this, Wireshark pops up the Print dialog box as shown in 
-	    <xref linkend="ChIOPrintDialogBox"/>.
+        To print packets, select the "Print..." menu item from the File menu. 
+        When you do this, Wireshark pops up the Print dialog box as shown in 
+        <xref linkend="ChIOPrintDialogBox"/>.
     </para>
-	<section><title>The "Print" dialog box</title>
+    <section><title>The "Print" dialog box</title>
     <figure id="ChIOPrintDialogBox">
       <title>The "Print" dialog box</title>
       <graphic entityref="WiresharkPrint" format="PNG"/>
@@ -1245,199 +1245,199 @@
     <para>
       The following fields are available in the Print dialog box:
       <variablelist>
-	<varlistentry><term><command>Printer</command></term>
-	  <listitem>
-	    <para>
-	      This field contains a pair of mutually exclusive radio buttons:
-	      <itemizedlist>
-		<listitem>
-		  <para>
-		    <command>Plain Text</command> specifies that 
-		    the packet print should be in plain text.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>PostScript</command> specifies that 
-		    the packet print process should use PostScript to 
-		    generate a better print output on PostScript aware printers.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>Output to file:</command> specifies that printing 
-		    be done to a file, using the filename entered in the field or selected 
-			with the browse button.
-		  </para>
-	    <para>
-	      This field is where you enter the <command>file</command> to 
-	      print to if you have selected Print to a file, or you can click the 
-		  button to browse the filesystem. It is greyed out if Print to a file 
-		  is not selected.
-	    </para>
-		</listitem>
-		<listitem>
-		  <para>
-		    <command>Print command</command> specifies that a 
-		    command be used for printing. 
-		  </para>
-		<note><title>Note!</title>
-		<para>
-		These <command>Print command</command> fields are not available on 
-		windows platforms. 
-		</para>
-		</note>
-	    <para>
-	      This field specifies the command to use for printing. It 
-	      is typically <command>lpr</command>. You would change it 
-	      to specify a particular queue if you need to print to a 
-	      queue other than the default.  An example might be:
-	      <programlisting>
+    <varlistentry><term><command>Printer</command></term>
+      <listitem>
+        <para>
+          This field contains a pair of mutually exclusive radio buttons:
+          <itemizedlist>
+        <listitem>
+          <para>
+            <command>Plain Text</command> specifies that 
+            the packet print should be in plain text.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>PostScript</command> specifies that 
+            the packet print process should use PostScript to 
+            generate a better print output on PostScript aware printers.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>Output to file:</command> specifies that printing 
+            be done to a file, using the filename entered in the field or selected 
+            with the browse button.
+          </para>
+        <para>
+          This field is where you enter the <command>file</command> to 
+          print to if you have selected Print to a file, or you can click the 
+          button to browse the filesystem. It is greyed out if Print to a file 
+          is not selected.
+        </para>
+        </listitem>
+        <listitem>
+          <para>
+            <command>Print command</command> specifies that a 
+            command be used for printing. 
+          </para>
+        <note><title>Note!</title>
+        <para>
+        These <command>Print command</command> fields are not available on 
+        windows platforms. 
+        </para>
+        </note>
+        <para>
+          This field specifies the command to use for printing. It 
+          is typically <command>lpr</command>. You would change it 
+          to specify a particular queue if you need to print to a 
+          queue other than the default.  An example might be:
+          <programlisting>
 lpr -Pmypostscript
-	      </programlisting>
-	      This field is greyed out if <command>Output to file:</command> is 
-	      checked above.
-	    </para>
-		</listitem>
-	      </itemizedlist>
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>Packet Range</command></term>
-	  <listitem>
-	    <para>
-		  Select the packets to be printed, see <xref 
-		  linkend="ChIOPacketRangeSection"/>
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry>
-	  <term><command>Packet Format</command></term>
-	  <listitem>
-	    <para>
-		  Select the output format of the packets to be printed. You can 
-		  choose, how each packet is printed, see 
-		  <xref linkend="ChIOPacketFormatFrame"/>
-	    </para>
-	  </listitem>
-	</varlistentry>
+          </programlisting>
+          This field is greyed out if <command>Output to file:</command> is 
+          checked above.
+        </para>
+        </listitem>
+          </itemizedlist>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>Packet Range</command></term>
+      <listitem>
+        <para>
+          Select the packets to be printed, see <xref 
+          linkend="ChIOPacketRangeSection"/>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term><command>Packet Format</command></term>
+      <listitem>
+        <para>
+          Select the output format of the packets to be printed. You can 
+          choose, how each packet is printed, see 
+          <xref linkend="ChIOPacketFormatFrame"/>
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </para>
   </section>
   </section>
 
   <section id="ChIOPacketRangeSection"><title>The Packet Range frame</title>
-	<para>
-	The packet range frame is a part of various output related dialog boxes. 
-	It provides options to select which packets should be processed by the 
-	output function.
+    <para>
+    The packet range frame is a part of various output related dialog boxes. 
+    It provides options to select which packets should be processed by the 
+    output function.
     <figure id="ChIOPacketRangeFrame">
       <title>The "Packet Range" frame</title>
       <graphic entityref="WiresharkPacketRangeFrame" format="PNG"/>
     </figure>
-	</para>
-	<para>
-	If the <command>Captured</command> button is set (default), all packets 
-	from the selected rule will be processed. If the <command>Displayed
-	</command> button is set, only the currently displayed packets are taken 
-	into account to the selected rule.
-	</para>
-	<para>
-	<itemizedlist>
-		<listitem>
-		  <para>
-		  <command>All packets</command> will process all packets.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Selected packet only</command> process only the selected 
-		  packet.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Marked packets only</command> process only the marked 
-		  packets.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>From first to last marked packet</command> process the 
-		  packets from the first to the last marked one.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Specify a packet range</command> process a user specified 
-		  range of packets, e.g. specifying <command>5,10-15,20-</command> will 
-		  process the packet number five, the packets from packet number ten 
-		  to fifteen (inclusive) and every packet from number twenty to the 
-		  end of the capture.
-		  </para>
-		</listitem>
-	</itemizedlist>
-	</para>
+    </para>
+    <para>
+    If the <command>Captured</command> button is set (default), all packets 
+    from the selected rule will be processed. If the <command>Displayed
+    </command> button is set, only the currently displayed packets are taken 
+    into account to the selected rule.
+    </para>
+    <para>
+    <itemizedlist>
+        <listitem>
+          <para>
+          <command>All packets</command> will process all packets.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Selected packet only</command> process only the selected 
+          packet.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Marked packets only</command> process only the marked 
+          packets.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>From first to last marked packet</command> process the 
+          packets from the first to the last marked one.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Specify a packet range</command> process a user specified 
+          range of packets, e.g. specifying <command>5,10-15,20-</command> will 
+          process the packet number five, the packets from packet number ten 
+          to fifteen (inclusive) and every packet from number twenty to the 
+          end of the capture.
+          </para>
+        </listitem>
+    </itemizedlist>
+    </para>
   </section>
   
   <section id="ChIOPacketFormatSection"><title>The Packet Format frame</title>
-	<para>
-	The packet format frame is a part of various output related dialog boxes. 
-	It provides options to select which parts of a packet should be used for 
-	the output function.
+    <para>
+    The packet format frame is a part of various output related dialog boxes. 
+    It provides options to select which parts of a packet should be used for 
+    the output function.
     <figure id="ChIOPacketFormatFrame">
       <title>The "Packet Format" frame</title>
       <graphic entityref="WiresharkPacketFormatFrame" format="PNG"/>
     </figure>
-	<itemizedlist>
-		<listitem>
-		  <para>
-		  <command>Packet summary line</command> enable the output of the 
-		  summary line, just as in the "Packet List" pane.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Packet details</command> enable the output of the packet 
-		  details tree.
-		  </para>
-		<itemizedlist>
-		<listitem>
-		  <para>
-		  <command>All collapsed</command> the info from the "Packet Details" 
-		  pane in "all collapsed" state.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>As displayed</command> the info from the "Packet Details" 
-		  pane in the current state.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>All expanded</command> the info from the "Packet Details" 
-		  pane in "all expanded" state.
-		  </para>
-		</listitem>
-		</itemizedlist>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Packet bytes</command> enable the output of the packet 
-		  bytes, just as in the "Packet Bytes" pane.
-		  </para>
-		</listitem>
-		<listitem>
-		  <para>
-		  <command>Each packet on a new page</command> put each packet on a 
-		  separate page (e.g. when saving/printing to a text file, this will 
-		  put a form feed character between the packets).
-		  </para>
-		</listitem>
-	</itemizedlist>
-	</para>
+    <itemizedlist>
+        <listitem>
+          <para>
+          <command>Packet summary line</command> enable the output of the 
+          summary line, just as in the "Packet List" pane.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Packet details</command> enable the output of the packet 
+          details tree.
+          </para>
+        <itemizedlist>
+        <listitem>
+          <para>
+          <command>All collapsed</command> the info from the "Packet Details" 
+          pane in "all collapsed" state.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>As displayed</command> the info from the "Packet Details" 
+          pane in the current state.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>All expanded</command> the info from the "Packet Details" 
+          pane in "all expanded" state.
+          </para>
+        </listitem>
+        </itemizedlist>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Packet bytes</command> enable the output of the packet 
+          bytes, just as in the "Packet Bytes" pane.
+          </para>
+        </listitem>
+        <listitem>
+          <para>
+          <command>Each packet on a new page</command> put each packet on a 
+          separate page (e.g. when saving/printing to a text file, this will 
+          put a form feed character between the packets).
+          </para>
+        </listitem>
+    </itemizedlist>
+    </para>
   </section>
   
 </chapter>
diff --git a/docbook/wsug_src/WSUG_chapter_statistics.xml b/docbook/wsug_src/WSUG_chapter_statistics.xml
index 932be56e99..07aae1404d 100644
--- a/docbook/wsug_src/WSUG_chapter_statistics.xml
+++ b/docbook/wsug_src/WSUG_chapter_statistics.xml
@@ -10,182 +10,182 @@
     <command>Statistics</command> menu.
     </para>
     <para>
-	These statistics range from general information about the loaded capture file
-	(like the number of captured packets), to statistics about specific protocols
-	(e.g. statistics about the number of HTTP requests and responses captured).
-	<itemizedlist>
-	<listitem>
-	<para>
-	General statistics:
-	</para>
-	<itemizedlist>
-	<listitem>
-	<para><command>Summary</command> about the capture file.</para>
-	</listitem>
-	<listitem>
-	<para><command>Protocol Hierarchy</command> of the captured packets.</para>
-	</listitem>
-	<listitem>
-	<para><command>Conversations</command> e.g. traffic between specific IP
-	addresses.</para>
-	</listitem>
-	<listitem>
-	<para><command>Endpoints</command> e.g. traffic to and from an IP
-	addresses.</para>
-	</listitem>
-	<listitem>
-	<para><command>IO Graphs</command> visualizing the number of packets (or
-	similar) in time.</para>
-	</listitem>
-	</itemizedlist>
-	</listitem>
-	<listitem>
-	<para>
-	Protocol specific statistics:
-	</para>
-	<itemizedlist>
-	<listitem>
-	<para><command>Service Response Time</command> between request and response
-	of some protocols.</para>
-	</listitem>
-	<listitem>
-	<para><command>Various other</command> protocol specific statistics.</para>
-	</listitem>
-	</itemizedlist>
-	</listitem>
-	</itemizedlist>
-	<note><title>Note!</title>
-	<para>
-	The protocol specific statistics requires detailed knowledge about the
-	specific protocol. Unless you are familiar with that protocol, statistics
-	about it will be pretty hard to understand.
-	</para>
-	</note>
+    These statistics range from general information about the loaded capture file
+    (like the number of captured packets), to statistics about specific protocols
+    (e.g. statistics about the number of HTTP requests and responses captured).
+    <itemizedlist>
+    <listitem>
+    <para>
+    General statistics:
+    </para>
+    <itemizedlist>
+    <listitem>
+    <para><command>Summary</command> about the capture file.</para>
+    </listitem>
+    <listitem>
+    <para><command>Protocol Hierarchy</command> of the captured packets.</para>
+    </listitem>
+    <listitem>
+    <para><command>Conversations</command> e.g. traffic between specific IP
+    addresses.</para>
+    </listitem>
+    <listitem>
+    <para><command>Endpoints</command> e.g. traffic to and from an IP
+    addresses.</para>
+    </listitem>
+    <listitem>
+    <para><command>IO Graphs</command> visualizing the number of packets (or
+    similar) in time.</para>
+    </listitem>
+    </itemizedlist>
+    </listitem>
+    <listitem>
+    <para>
+    Protocol specific statistics:
+    </para>
+    <itemizedlist>
+    <listitem>
+    <para><command>Service Response Time</command> between request and response
+    of some protocols.</para>
+    </listitem>
+    <listitem>
+    <para><command>Various other</command> protocol specific statistics.</para>
+    </listitem>
+    </itemizedlist>
+    </listitem>
+    </itemizedlist>
+    <note><title>Note!</title>
+    <para>
+    The protocol specific statistics requires detailed knowledge about the
+    specific protocol. Unless you are familiar with that protocol, statistics
+    about it will be pretty hard to understand.
+    </para>
+    </note>
     </para>
   </section>
 
   <section id="ChStatSummary">
     <title>The "Summary" window</title>
     <para>
-	General statistics about the current capture file.
-    </para>
-	<figure><title>The "Summary" window</title>
-	  <graphic entityref="WiresharkStatsSummary" format="PNG"/>
-	</figure>
-	<itemizedlist>
-	<listitem>
-	<para><command>File</command>: general information about the capture file.
-	</para>
-	</listitem>
-	<listitem>
-	<para><command>Time</command>: the timestamps when the first and the
-	last packet were captured (and the time between them).</para>
-	</listitem>
-	<listitem>
-	<para><command>Capture</command>: information from the time when the
-	capture was done (only available if the packet data was captured from the
-	network and not loaded from a file).</para>
-	</listitem>
-	<listitem>
-	<para><command>Display</command>: some display related information.</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Traffic</command>: some statistics of the network traffic seen.
-	If a display filter is set, you will see values in the Captured column,
-	and if any packages are marked, you will see values in the Marked column.
-	The values in the <command>Captured</command> column will remain the same as
-	before, while the values in the <command>Displayed</command> column will
-	reflect the values corresponding to the packets shown in the display.
-	The values in the <command>Marked</command> column will reflect the values
-	corresponding to the marked packages.
-	</para>
-	</listitem>
-	</itemizedlist>
+    General statistics about the current capture file.
+    </para>
+    <figure><title>The "Summary" window</title>
+      <graphic entityref="WiresharkStatsSummary" format="PNG"/>
+    </figure>
+    <itemizedlist>
+    <listitem>
+    <para><command>File</command>: general information about the capture file.
+    </para>
+    </listitem>
+    <listitem>
+    <para><command>Time</command>: the timestamps when the first and the
+    last packet were captured (and the time between them).</para>
+    </listitem>
+    <listitem>
+    <para><command>Capture</command>: information from the time when the
+    capture was done (only available if the packet data was captured from the
+    network and not loaded from a file).</para>
+    </listitem>
+    <listitem>
+    <para><command>Display</command>: some display related information.</para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Traffic</command>: some statistics of the network traffic seen.
+    If a display filter is set, you will see values in the Captured column,
+    and if any packages are marked, you will see values in the Marked column.
+    The values in the <command>Captured</command> column will remain the same as
+    before, while the values in the <command>Displayed</command> column will
+    reflect the values corresponding to the packets shown in the display.
+    The values in the <command>Marked</command> column will reflect the values
+    corresponding to the marked packages.
+    </para>
+    </listitem>
+    </itemizedlist>
   </section>
 
   <section id="ChStatHierarchy">
     <title>The "Protocol Hierarchy" window</title>
     <para>
-	The protocol hierarchy of the captured packets.
-	<figure><title>The "Protocol Hierarchy" window</title>
-	  <graphic entityref="WiresharkStatsHierarchy" format="PNG"/>
-	</figure>
-	This is a tree of all the protocols in the capture. You can collapse or
-	expand subtrees, by clicking on the plus / minus icons. By default, all
-	trees are expanded.
-	</para>
-	<para>
-	Each row contains the statistical values of one protocol.
-	The <command>Display filter</command> will show the current display filter.
-	</para>
-	<para>
-	The following columns containing the statistical values are available:
-	<itemizedlist>
-	<listitem>
-	<para><command>Protocol</command>: this protocol's name</para>
-	</listitem>
-	<listitem>
-	<para><command>% Packets</command>: the percentage of protocol packets,
-	relative to all packets in the capture</para>
-	</listitem>
-	<listitem>
-	<para><command>Packets</command>: the absolute number of packets of this
-	protocol</para>
-	</listitem>
-	<listitem>
-	<para><command>Bytes</command>: the absolute number of bytes of this
-	protocol</para>
-	</listitem>
-	<listitem>
-	<para><command>MBit/s</command>: the bandwidth of this protocol, relative
-	to the capture time</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>End Packets</command>: the absolute number of packets of this
-	protocol (where this protocol was the highest protocol to decode)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>End Bytes</command>: the absolute number of bytes of this protocol
-	(where this protocol was the highest protocol to decode)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>End MBit/s</command>: the bandwidth of this protocol, relative to
-	the capture time (where this protocol was the highest protocol to decode)
-	</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	<note><title>Note!</title>
-	<para>
-	Packets will usually contain multiple protocols, so more than one protocol
-	will be counted for each packet.
-	Example: In the screenshot IP has 99,17% and TCP 85,83% (which is together
-	much more than 100%).
-	</para>
-	</note>
-	<note><title>Note!</title>
-	<para>
-	Protocol layers can consist of packets that won't contain any higher layer
-	protocol, so the sum of all higher layer packets may not sum up to the
-	protocols packet count.
-	Example: In the screenshot TCP has 85,83% but the sum of the subprotocols
-	(HTTP, ...) is much less. This may be caused by TCP protocol overhead,
-	e.g. TCP ACK packets won't be counted as packets of the higher layer).
-	</para>
-	</note>
-	<note><title>Note!</title>
-	<para>
-	A single packet can contain the same protocol more than once. In this case,
-	the protocol is counted more than once. For example: in some tunneling
-	configurations the IP layer can appear twice.
-	</para>
-	</note>
+    The protocol hierarchy of the captured packets.
+    <figure><title>The "Protocol Hierarchy" window</title>
+      <graphic entityref="WiresharkStatsHierarchy" format="PNG"/>
+    </figure>
+    This is a tree of all the protocols in the capture. You can collapse or
+    expand subtrees, by clicking on the plus / minus icons. By default, all
+    trees are expanded.
+    </para>
+    <para>
+    Each row contains the statistical values of one protocol.
+    The <command>Display filter</command> will show the current display filter.
+    </para>
+    <para>
+    The following columns containing the statistical values are available:
+    <itemizedlist>
+    <listitem>
+    <para><command>Protocol</command>: this protocol's name</para>
+    </listitem>
+    <listitem>
+    <para><command>% Packets</command>: the percentage of protocol packets,
+    relative to all packets in the capture</para>
+    </listitem>
+    <listitem>
+    <para><command>Packets</command>: the absolute number of packets of this
+    protocol</para>
+    </listitem>
+    <listitem>
+    <para><command>Bytes</command>: the absolute number of bytes of this
+    protocol</para>
+    </listitem>
+    <listitem>
+    <para><command>MBit/s</command>: the bandwidth of this protocol, relative
+    to the capture time</para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>End Packets</command>: the absolute number of packets of this
+    protocol (where this protocol was the highest protocol to decode)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>End Bytes</command>: the absolute number of bytes of this protocol
+    (where this protocol was the highest protocol to decode)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>End MBit/s</command>: the bandwidth of this protocol, relative to
+    the capture time (where this protocol was the highest protocol to decode)
+    </para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    <note><title>Note!</title>
+    <para>
+    Packets will usually contain multiple protocols, so more than one protocol
+    will be counted for each packet.
+    Example: In the screenshot IP has 99,17% and TCP 85,83% (which is together
+    much more than 100%).
+    </para>
+    </note>
+    <note><title>Note!</title>
+    <para>
+    Protocol layers can consist of packets that won't contain any higher layer
+    protocol, so the sum of all higher layer packets may not sum up to the
+    protocols packet count.
+    Example: In the screenshot TCP has 85,83% but the sum of the subprotocols
+    (HTTP, ...) is much less. This may be caused by TCP protocol overhead,
+    e.g. TCP ACK packets won't be counted as packets of the higher layer).
+    </para>
+    </note>
+    <note><title>Note!</title>
+    <para>
+    A single packet can contain the same protocol more than once. In this case,
+    the protocol is counted more than once. For example: in some tunneling
+    configurations the IP layer can appear twice.
+    </para>
+    </note>
   </section>
 
   <section id="ChStatConversations">
@@ -196,10 +196,10 @@
     <section>
       <title>What is a Conversation?</title>
       <para>
-	A network conversation is the traffic between two specific endpoints. For
-	example, an IP conversation is all the traffic between two IP addresses.
-	The description of the known endpoint types can be found in
-	<xref linkend="ChStatEndpointDefinition"/>.
+    A network conversation is the traffic between two specific endpoints. For
+    example, an IP conversation is all the traffic between two IP addresses.
+    The description of the known endpoint types can be found in
+    <xref linkend="ChStatEndpointDefinition"/>.
       </para>
     </section>
     <section id="ChStatConversationsWindow"><title>The "Conversations" window</title>
@@ -238,12 +238,12 @@
     <section id="ChStatConversationListWindow">
       <title>The protocol specific "Conversation List" windows</title>
       <para>
-	Before the combined window described above was available, each of its
-	pages was shown as a separate window. Even though the combined window is
-	much more convenient to use, these separate windows are still
-	available. The main reason is that they might process faster for
-	very large capture files. However, as the functionality is exactly the
-	same as in the combined window, they won't be discussed in detail here.
+    Before the combined window described above was available, each of its
+    pages was shown as a separate window. Even though the combined window is
+    much more convenient to use, these separate windows are still
+    available. The main reason is that they might process faster for
+    very large capture files. However, as the functionality is exactly the
+    same as in the combined window, they won't be discussed in detail here.
       </para>
     </section>
   </section>
@@ -254,9 +254,9 @@
       Statistics of the endpoints captured.
       <tip><title>Tip!</title>
       <para>
-	If you are looking for a feature other network tools call a <command>
-	hostlist</command>, here is the right place to look. The list of
-	Ethernet or IP endpoints is usually what you're looking for.
+    If you are looking for a feature other network tools call a <command>
+    hostlist</command>, here is the right place to look. The list of
+    Ethernet or IP endpoints is usually what you're looking for.
       </para>
       </tip>
     </para>
@@ -268,86 +268,86 @@
     </para>
     <itemizedlist>
       <listitem>
-	<para>
-	  <command>Ethernet</command>: an Ethernet endpoint is identical to the
-	  Ethernet's MAC address.
-	</para>
+    <para>
+      <command>Ethernet</command>: an Ethernet endpoint is identical to the
+      Ethernet's MAC address.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>Fibre Channel</command>: XXX - insert info here.
-	</para>
+    <para>
+      <command>Fibre Channel</command>: XXX - insert info here.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>FDDI</command>: a FDDI endpoint is identical to the FDDI MAC
-	  address.
-	</para>
+    <para>
+      <command>FDDI</command>: a FDDI endpoint is identical to the FDDI MAC
+      address.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>IPv4</command>: an IP endpoint is identical to its IP address.
-	</para>
+    <para>
+      <command>IPv4</command>: an IP endpoint is identical to its IP address.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>IPX</command>: an IPX endpoint is concatenation of a 32 bit
-	  network number and 48 bit node address, be default the Ethernets' MAC
-	  address.
-	</para>
+    <para>
+      <command>IPX</command>: an IPX endpoint is concatenation of a 32 bit
+      network number and 48 bit node address, be default the Ethernets' MAC
+      address.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>JXTA</command>: a JXTA endpoint is a 160 bit SHA-1 URN.
-	</para>
+    <para>
+      <command>JXTA</command>: a JXTA endpoint is a 160 bit SHA-1 URN.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>NCP</command>: XXX - insert info here.
-	</para>
+    <para>
+      <command>NCP</command>: XXX - insert info here.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>RSVP</command>: XXX - insert info here.
-	</para>
+    <para>
+      <command>RSVP</command>: XXX - insert info here.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>SCTP</command>: a SCTP endpoint is a combination of the host IP
-	  addresses (plural) and the SCTP port used. So different SCTP ports on the
-	  same IP address are different SCTP endpoints, but the same SCTP port on
-	  different IP addresses of the same host are still the same endpoint.
-	</para>
+    <para>
+      <command>SCTP</command>: a SCTP endpoint is a combination of the host IP
+      addresses (plural) and the SCTP port used. So different SCTP ports on the
+      same IP address are different SCTP endpoints, but the same SCTP port on
+      different IP addresses of the same host are still the same endpoint.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>TCP</command>: a TCP endpoint is a combination of the IP address
-	  and the TCP port used, so different TCP ports on the same IP address are
-	  different TCP endpoints.
-	</para>
+    <para>
+      <command>TCP</command>: a TCP endpoint is a combination of the IP address
+      and the TCP port used, so different TCP ports on the same IP address are
+      different TCP endpoints.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>Token Ring</command>: a Token Ring endpoint is identical to the
-	  Token Ring MAC address.
-	</para>
+    <para>
+      <command>Token Ring</command>: a Token Ring endpoint is identical to the
+      Token Ring MAC address.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>UDP</command>: a UDP endpoint is a combination of the IP address
-	  and the UDP port used, so different UDP ports on the same IP address are
-	  different UDP endpoints.
-	</para>
+    <para>
+      <command>UDP</command>: a UDP endpoint is a combination of the IP address
+      and the UDP port used, so different UDP ports on the same IP address are
+      different UDP endpoints.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>USB</command>: XXX - insert info here.
-	</para>
+    <para>
+      <command>USB</command>: XXX - insert info here.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>WLAN</command>: XXX - insert info here.
-	</para>
+    <para>
+      <command>WLAN</command>: XXX - insert info here.
+    </para>
       </listitem>
     </itemizedlist>
     <note><title>Broadcast / multicast endpoints</title>
@@ -362,55 +362,55 @@
     <section id="ChStatEndpointsWindow">
       <title>The "Endpoints" window</title>
       <para>
-	This window shows statistics about the endpoints captured.
+    This window shows statistics about the endpoints captured.
       </para>
       <figure><title>The "Endpoints" window</title>
       <graphic entityref="WiresharkStatsEndpoints" format="PNG"/>
       </figure>
       <para>
-	For each supported protocol, a tab is shown in this window.
-	Each tab label shows the number of endpoints captured (e.g. the
-	tab label "Ethernet: 5" tells you that five ethernet endpoints have been
-	captured). If no endpoints of a specific protocol were captured, the tab
-	label will be greyed out (although the related page can still be selected).
+    For each supported protocol, a tab is shown in this window.
+    Each tab label shows the number of endpoints captured (e.g. the
+    tab label "Ethernet: 5" tells you that five ethernet endpoints have been
+    captured). If no endpoints of a specific protocol were captured, the tab
+    label will be greyed out (although the related page can still be selected).
       </para>
       <para>
-	Each row in the list shows the statistical values for exactly one endpoint.
+    Each row in the list shows the statistical values for exactly one endpoint.
       </para>
       <para>
-	<command>Name resolution</command> will be done if selected in the window
-	and if it is active for the specific protocol layer (MAC layer for the
-	selected Ethernet endpoints page). As you might have noticed, the first
-	row has a name
-	resolution of the first three bytes "Netgear", the second row's address was
-	resolved to an IP address (using ARP) and the third was resolved
-	to a broadcast (unresolved this would still be: ff:ff:ff:ff:ff:ff); the last two
-	Ethernet addresses remain unresolved.
+    <command>Name resolution</command> will be done if selected in the window
+    and if it is active for the specific protocol layer (MAC layer for the
+    selected Ethernet endpoints page). As you might have noticed, the first
+    row has a name
+    resolution of the first three bytes "Netgear", the second row's address was
+    resolved to an IP address (using ARP) and the third was resolved
+    to a broadcast (unresolved this would still be: ff:ff:ff:ff:ff:ff); the last two
+    Ethernet addresses remain unresolved.
       </para>
       <para>
-	<command>Limit to display filter</command> will only show conversations matching
-	the current display filter.
+    <command>Limit to display filter</command> will only show conversations matching
+    the current display filter.
       </para>
       <para>
-	The <command>copy</command> button will copy the list values to the
-	clipboard in CSV (Comma Separated Values) format.
+    The <command>copy</command> button will copy the list values to the
+    clipboard in CSV (Comma Separated Values) format.
       </para>
       <tip><title>Tip!</title>
       <para>
-	This window will be updated frequently, so it will be useful, even if
-	you open it before (or while) you are doing a live capture.
+    This window will be updated frequently, so it will be useful, even if
+    you open it before (or while) you are doing a live capture.
       </para>
       </tip>
     </section>
     <section id="ChStatEndpointListWindow">
       <title>The protocol specific "Endpoint List" windows</title>
       <para>
-	Before the combined window described above was available, each of its
-	pages was shown as a separate window. Even though the combined window is
-	much more convenient to use, these separate windows are still
-	available. The main reason is that they might process faster for
-	very large capture files. However, as the functionality is exactly the
-	same as in the combined window, they won't be discussed in detail here.
+    Before the combined window described above was available, each of its
+    pages was shown as a separate window. Even though the combined window is
+    much more convenient to use, these separate windows are still
+    available. The main reason is that they might process faster for
+    very large capture files. However, as the functionality is exactly the
+    same as in the combined window, they won't be discussed in detail here.
       </para>
     </section>
   </section>
@@ -418,175 +418,175 @@
   <section id="ChStatIOGraphs">
     <title>The "IO Graphs" window</title>
     <para>
-	User configurable graph of the captured network packets.
+    User configurable graph of the captured network packets.
     </para>
     <para>
-	You can define up to five differently colored graphs.
+    You can define up to five differently colored graphs.
     </para>
 
-	<figure><title>The "IO Graphs" window</title>
-	  <graphic entityref="WiresharkStatsIOGraphs" format="PNG"/>
-	</figure>
+    <figure><title>The "IO Graphs" window</title>
+      <graphic entityref="WiresharkStatsIOGraphs" format="PNG"/>
+    </figure>
 
-	<para>
-	The user can configure the following things:
-	<itemizedlist>
-	<listitem>
-	<para><command>Graphs</command>
-	<itemizedlist>
-	<listitem>
-	<para>
-	<command>Graph 1-5</command>: enable the specific graph 1-5 (only graph 1 is enabled
-	by default)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Color</command>: the color of the graph (cannot be changed)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Filter</command>: a display filter for this graph (only the
-	packets that pass this filter will be taken into account for this graph)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Style</command>: the style of the graph (Line/Impulse/FBar/Dot)
-	</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	</listitem>
+    <para>
+    The user can configure the following things:
+    <itemizedlist>
+    <listitem>
+    <para><command>Graphs</command>
+    <itemizedlist>
+    <listitem>
+    <para>
+    <command>Graph 1-5</command>: enable the specific graph 1-5 (only graph 1 is enabled
+    by default)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Color</command>: the color of the graph (cannot be changed)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Filter</command>: a display filter for this graph (only the
+    packets that pass this filter will be taken into account for this graph)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Style</command>: the style of the graph (Line/Impulse/FBar/Dot)
+    </para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    </listitem>
 
-	<listitem>
-	<para><command>X Axis</command>
-	<itemizedlist>
-	<listitem>
-	<para>
-	<command>Tick interval</command>: an interval in x direction lasts
-	(10/1 minutes or 10/1/0.1/0.01/0.001 seconds)
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Pixels per tick</command>: use 10/5/2/1 pixels per tick interval
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>View as time of day</command>: option to view x direction labels
-	as time of day instead of seconds or minutes since beginning of capture
-	</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	</listitem>
+    <listitem>
+    <para><command>X Axis</command>
+    <itemizedlist>
+    <listitem>
+    <para>
+    <command>Tick interval</command>: an interval in x direction lasts
+    (10/1 minutes or 10/1/0.1/0.01/0.001 seconds)
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Pixels per tick</command>: use 10/5/2/1 pixels per tick interval
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>View as time of day</command>: option to view x direction labels
+    as time of day instead of seconds or minutes since beginning of capture
+    </para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    </listitem>
 
-	<listitem>
-	<para><command>Y Axis</command>
-	<itemizedlist>
-	<listitem>
-	<para>
-	<command>Unit</command>: the unit for the y direction (Packets/Tick,
-	Bytes/Tick, Bits/Tick, Advanced...) [XXX - describe the Advanced feature.]
-	</para>
-	</listitem>
-	<listitem>
-	<para>
-	<command>Scale</command>: the scale for the y unit
-	(Logarithmic,Auto,10,20,50,100,200,500,...)
-	</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	</listitem>
+    <listitem>
+    <para><command>Y Axis</command>
+    <itemizedlist>
+    <listitem>
+    <para>
+    <command>Unit</command>: the unit for the y direction (Packets/Tick,
+    Bytes/Tick, Bits/Tick, Advanced...) [XXX - describe the Advanced feature.]
+    </para>
+    </listitem>
+    <listitem>
+    <para>
+    <command>Scale</command>: the scale for the y unit
+    (Logarithmic,Auto,10,20,50,100,200,500,...)
+    </para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    </listitem>
 
-	</itemizedlist>
-	</para>
-	<para>
-	  The <command>save</command> button will save the currently displayed
-	  portion of the graph as one of various file formats.
-	</para>
-	<para>
-	  The <command>copy</command> button will copy values from selected
-	  graphs to the clipboard in CSV (Comma Separated Values) format.
-	</para>
-	<tip><title>Tip!</title>
-	<para>
-	  Click in the graph to select the first package in the selected interval.
-	</para>
-	</tip>
+    </itemizedlist>
+    </para>
+    <para>
+      The <command>save</command> button will save the currently displayed
+      portion of the graph as one of various file formats.
+    </para>
+    <para>
+      The <command>copy</command> button will copy values from selected
+      graphs to the clipboard in CSV (Comma Separated Values) format.
+    </para>
+    <tip><title>Tip!</title>
+    <para>
+      Click in the graph to select the first package in the selected interval.
+    </para>
+    </tip>
   </section>
 
   <section id="ChStatSRT">
     <title>Service Response Time</title>
     <para>
-	The service response time is the time between a request and the
-	corresponding response. This information is available for many protocols.
-    </para>
-    <para>
-	Service response time statistics are currently available for the following
-	protocols:
-	<itemizedlist>
-	<listitem>
-	<para><command>DCE-RPC</command></para>
-	</listitem>
-	<listitem>
-	<para><command>Fibre Channel</command></para>
-	</listitem>
-	<listitem>
-	<para><command>H.225 RAS</command></para>
-	</listitem>
-	<listitem>
-	<para><command>LDAP</command></para>
-	</listitem>
-	<listitem>
-	<para><command>LTE MAC</command></para>
-	</listitem>
-	<listitem>
-	<para><command>MGCP</command></para>
-	</listitem>
-	<listitem>
-	<para><command>ONC-RPC</command></para>
-	</listitem>
-	<listitem>
-	<para><command>SMB</command></para>
-	</listitem>
-	</itemizedlist>
-	As an example, the DCE-RPC service response time is described in more
-	detail.
-	<note><title>Note!</title>
-	<para>
-	The other Service Response Time windows will work the same way (or only
-	slightly different) compared to the following description.
-	</para>
-	</note>
+    The service response time is the time between a request and the
+    corresponding response. This information is available for many protocols.
+    </para>
+    <para>
+    Service response time statistics are currently available for the following
+    protocols:
+    <itemizedlist>
+    <listitem>
+    <para><command>DCE-RPC</command></para>
+    </listitem>
+    <listitem>
+    <para><command>Fibre Channel</command></para>
+    </listitem>
+    <listitem>
+    <para><command>H.225 RAS</command></para>
+    </listitem>
+    <listitem>
+    <para><command>LDAP</command></para>
+    </listitem>
+    <listitem>
+    <para><command>LTE MAC</command></para>
+    </listitem>
+    <listitem>
+    <para><command>MGCP</command></para>
+    </listitem>
+    <listitem>
+    <para><command>ONC-RPC</command></para>
+    </listitem>
+    <listitem>
+    <para><command>SMB</command></para>
+    </listitem>
+    </itemizedlist>
+    As an example, the DCE-RPC service response time is described in more
+    detail.
+    <note><title>Note!</title>
+    <para>
+    The other Service Response Time windows will work the same way (or only
+    slightly different) compared to the following description.
+    </para>
+    </note>
     </para>
   <section id="ChStatSRTDceRpc">
     <title>The "Service Response Time DCE-RPC" window</title>
     <para>
-	The service response time of DCE-RPC is the time between the request and
-	the corresponding response.
+    The service response time of DCE-RPC is the time between the request and
+    the corresponding response.
     </para>
     <para>
-	First of all, you have to select the DCE-RPC interface:
+    First of all, you have to select the DCE-RPC interface:
     </para>
-	<figure><title>The "Compute DCE-RPC statistics" window</title>
-	  <graphic entityref="WiresharkStatsSrtDcerpcFilter" format="PNG"/>
-	</figure>
+    <figure><title>The "Compute DCE-RPC statistics" window</title>
+      <graphic entityref="WiresharkStatsSrtDcerpcFilter" format="PNG"/>
+    </figure>
     <para>
-	You can optionally set a display filter, to reduce the amount of packets.
+    You can optionally set a display filter, to reduce the amount of packets.
     </para>
-	<figure><title>The "DCE-RPC Statistic for ..." window</title>
-	  <graphic entityref="WiresharkStatsSrtDcerpc" format="PNG"/>
-	</figure>
-	<para>
-	Each row corresponds to a method of the interface selected (so the EPM
-	interface in version 3 has 7 methods). For each
-	method the number of calls, and the statistics of the SRT time is
-	calculated.
+    <figure><title>The "DCE-RPC Statistic for ..." window</title>
+      <graphic entityref="WiresharkStatsSrtDcerpc" format="PNG"/>
+    </figure>
+    <para>
+    Each row corresponds to a method of the interface selected (so the EPM
+    interface in version 3 has 7 methods). For each
+    method the number of calls, and the statistics of the SRT time is
+    calculated.
     </para>
   </section>
   </section>
@@ -724,13 +724,13 @@
   <section id="ChStatXXX">
     <title>The protocol specific statistics windows</title>
     <para>
-	The protocol specific statistics windows display detailed information
-	of specific protocols and might be described in a later
-	version of this document.
+    The protocol specific statistics windows display detailed information
+    of specific protocols and might be described in a later
+    version of this document.
     </para>
     <para>
-	Some of these statistics are described at the
-	<ulink url="&WiresharkWikiPage;/Statistics"/> pages.
+    Some of these statistics are described at the
+    <ulink url="&WiresharkWikiPage;/Statistics"/> pages.
     </para>
   </section>
 
diff --git a/docbook/wsug_src/WSUG_chapter_telephony.xml b/docbook/wsug_src/WSUG_chapter_telephony.xml
index 31e8be7ed8..bdc55effad 100644
--- a/docbook/wsug_src/WSUG_chapter_telephony.xml
+++ b/docbook/wsug_src/WSUG_chapter_telephony.xml
@@ -6,51 +6,51 @@
   <section id="ChTelIntroduction">
   <title>Introduction</title>
     <para>
-	Wireshark provides a wide range of telephony related network statistics
-	which can be accessed via the <command>Telephony</command> menu.
+    Wireshark provides a wide range of telephony related network statistics
+    which can be accessed via the <command>Telephony</command> menu.
     </para>
     <para>
-	These statistics range from specific signaling protocols, to analysis of
-	signaling and media flows. If encoded in a compatible encoding the media
-	flow can even be played.
+    These statistics range from specific signaling protocols, to analysis of
+    signaling and media flows. If encoded in a compatible encoding the media
+    flow can even be played.
     </para>
   </section>
   
   <section id="ChTelRTPAnalysis">
     <title>RTP Analysis</title>
     <para>
-	The RTP analysis function takes the selected RTP stream (and the reverse
-	stream, if possible) and generates a list of statistics on it.
+    The RTP analysis function takes the selected RTP stream (and the reverse
+    stream, if possible) and generates a list of statistics on it.
     </para>
     <figure><title>The "RTP Stream Analysis" window</title>
     <graphic entityref="WiresharkTelRTPStreamAnalysis" format="PNG"/>
     </figure>
     <para>
-	Starting with basic data as packet number and sequence number, further
-	statistics are created based on arrival time, delay, jitter, packet size,
-	etc.
+    Starting with basic data as packet number and sequence number, further
+    statistics are created based on arrival time, delay, jitter, packet size,
+    etc.
     </para>
     <para>
-	Besides the per packet statistics, the lower pane shows the overall
-	statistics, with minimums and maximums for delta, jitter and clock skew.
-	Also an indication of lost packets is included.
+    Besides the per packet statistics, the lower pane shows the overall
+    statistics, with minimums and maximums for delta, jitter and clock skew.
+    Also an indication of lost packets is included.
     </para>
     <para>
-	The RTP Stream Analysis window further provides the option to save the RTP
-	payload (as raw data or, if in a PCM encoding, in an Audio file). Other
-	options a to export and plot various statistics on the RTP streams.
+    The RTP Stream Analysis window further provides the option to save the RTP
+    payload (as raw data or, if in a PCM encoding, in an Audio file). Other
+    options a to export and plot various statistics on the RTP streams.
     </para>
   </section>
 
   <section id="ChTelVoipCalls">
     <title>VoIP Calls</title>
     <para>
-	The VoIP Calls window shows a list of all detected VoIP calls in the
-	captured traffic. It finds calls by their signaling.
+    The VoIP Calls window shows a list of all detected VoIP calls in the
+    captured traffic. It finds calls by their signaling.
     </para>
     <para>
-	More details are described at the
-	<ulink url="&WiresharkWikiPage;/VoIP_calls"/> page.
+    More details are described at the
+    <ulink url="&WiresharkWikiPage;/VoIP_calls"/> page.
     </para>
   </section>
   
@@ -109,13 +109,13 @@
   <section id="ChTelXXX">
     <title>The protocol specific statistics windows</title>
     <para>
-	The protocol specific statistics windows display detailed information
-	of specific protocols and might be described in a later
-	version of this document.
+    The protocol specific statistics windows display detailed information
+    of specific protocols and might be described in a later
+    version of this document.
     </para>
     <para>
-	Some of these statistics are described at the
-	<ulink url="&WiresharkWikiPage;/Statistics"/> pages.
+    Some of these statistics are described at the
+    <ulink url="&WiresharkWikiPage;/Statistics"/> pages.
     </para>
   </section>
 
diff --git a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
index ecc0c5756c..ff6118ece5 100644
--- a/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
+++ b/docbook/wsug_src/WSUG_chapter_troubleshoot.xml
@@ -10,100 +10,100 @@
       contains a number of features that allow you to quickly focus on 
       problems in your network for several reasons:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    It allows you to focus in on specific packets and protocols, 
-	    as you can see a large amount of detail associated with 
-	    various protocols.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    It supports a large number of protocols, and the list of 
-	    protocols supported is growing as more people contribute 
-	    dissectors
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    By giving you a visual view of traffic in parts of your 
-	    network, and providing tools to filter and colorize that 
-	    information, you can get a better feel for your network 
-	    traffic, and can understand your network better.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        It allows you to focus in on specific packets and protocols, 
+        as you can see a large amount of detail associated with 
+        various protocols.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        It supports a large number of protocols, and the list of 
+        protocols supported is growing as more people contribute 
+        dissectors
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        By giving you a visual view of traffic in parts of your 
+        network, and providing tools to filter and colorize that 
+        information, you can get a better feel for your network 
+        traffic, and can understand your network better.
+      </para>
+    </listitem>
       </itemizedlist> 
     </para>
     <para>
       The following general approach is suggested:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    Determine that the problem looks like a networking problem.  
-	    There is no point in capturing packets if the problem is not 
-	    networking related.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Figure out where to capture packets.  You will have to 
-	    capture packets from a part of the network where you can 
-	    actually get network traffic related to the problem.  This is 
-	    especially important in the presence of switches and routers.  
-	    See <xref linkend="Ch04ROUSWI"/> for more details.
-	  </para>
-	  <para>
-	    Because Wireshark can read many capture file formats, you can 
-	    capture using any convenient tool. One useful approach is 
-	    to use <command>tcpdump</command> to capture on remote 
-	    systems and then copy the capture file to your system for 
-	    later analysis. For more details on capturing with 
-	    <command>tcpdump</command>, see <xref linkend="Ch05tcpdump"/>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Once you have captured packets that you think relate to 
-	    the problem, load them into Wireshark and look for your 
-	    problem. Using Wireshark's filtering and colorization 
-	    capabilities, you can quickly narrow down the capture to the 
-	    area of interest.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    Examine the appropriate fields within the packets where 
-	    the problem appears to be. These can often help to reveal 
-	    the problem. 
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Determine that the problem looks like a networking problem.  
+        There is no point in capturing packets if the problem is not 
+        networking related.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Figure out where to capture packets.  You will have to 
+        capture packets from a part of the network where you can 
+        actually get network traffic related to the problem.  This is 
+        especially important in the presence of switches and routers.  
+        See <xref linkend="Ch04ROUSWI"/> for more details.
+      </para>
+      <para>
+        Because Wireshark can read many capture file formats, you can 
+        capture using any convenient tool. One useful approach is 
+        to use <command>tcpdump</command> to capture on remote 
+        systems and then copy the capture file to your system for 
+        later analysis. For more details on capturing with 
+        <command>tcpdump</command>, see <xref linkend="Ch05tcpdump"/>.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Once you have captured packets that you think relate to 
+        the problem, load them into Wireshark and look for your 
+        problem. Using Wireshark's filtering and colorization 
+        capabilities, you can quickly narrow down the capture to the 
+        area of interest.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        Examine the appropriate fields within the packets where 
+        the problem appears to be. These can often help to reveal 
+        the problem. 
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
   </section>
   <section id="Ch04ROUSWI">
     <title>Capturing in the presence of switches and routers</title>
     <para>
-	In the old days of Ethernet, all network traffic was spread over one 
-	"yellow" cable through the whole network. Capturing data was easy,
-	as all packets from the network could be captured using the 
-	"promiscuous mode" at any place in the network. The only devices blocking 
-	network traffic, were routers. But as routers were extremely expensive, 
-	they were not widely used.
+    In the old days of Ethernet, all network traffic was spread over one 
+    "yellow" cable through the whole network. Capturing data was easy,
+    as all packets from the network could be captured using the 
+    "promiscuous mode" at any place in the network. The only devices blocking 
+    network traffic, were routers. But as routers were extremely expensive, 
+    they were not widely used.
     </para>
     <para>
-	Then Ethernet wiring using hubs become the state of the art. As the hubs 
-	still spaded the packets all over the network, things regarding 
-	capturing didn't changed.
+    Then Ethernet wiring using hubs become the state of the art. As the hubs 
+    still spaded the packets all over the network, things regarding 
+    capturing didn't changed.
     </para>
     <para>
-	At the next stage, Ethernet switches became widely available. This 
-	complicated things a lot. When capturing traffic on a computer connected 
-	to a switch, usually the switch will only forward packets to the computer, 
-	which are directed to it, or to all computers (broadcasts). It's much the 
-	same like deactivating the promiscuous mode of the capturing network card.
+    At the next stage, Ethernet switches became widely available. This 
+    complicated things a lot. When capturing traffic on a computer connected 
+    to a switch, usually the switch will only forward packets to the computer, 
+    which are directed to it, or to all computers (broadcasts). It's much the 
+    same like deactivating the promiscuous mode of the capturing network card.
     </para>
     <para>
-	There are some ways to circumvent this.
+    There are some ways to circumvent this.
     </para>
     <para>
       Many vendor's switches support a feature known as "port spanning" 
@@ -111,7 +111,7 @@
       are also sent out port B.  An excellent reference on the 
       "port spanning" feature of Cisco switches can be found at 
       <ulink url="http://www.cisco.com/warp/public/473/41.html">
-	Configuring the Catalyst Switched Port Analyzer (SPAN) Feature
+    Configuring the Catalyst Switched Port Analyzer (SPAN) Feature
       </ulink>
     </para>
   </section>
@@ -120,8 +120,8 @@
     <para>
       Troubleshooting often requires a reasonable knowledge of the 
       protocols in question. However, as Wireshark will often give you some 
-	  good hints, you might get an idea of what is going wrong simply by 
-	  looking in the packets being exchanged.
+      good hints, you might get an idea of what is going wrong simply by 
+      looking in the packets being exchanged.
     </para>
   </section>
 </chapter>
diff --git a/docbook/wsug_src/WSUG_chapter_use.xml b/docbook/wsug_src/WSUG_chapter_use.xml
index 7988738379..9737b5bbde 100644
--- a/docbook/wsug_src/WSUG_chapter_use.xml
+++ b/docbook/wsug_src/WSUG_chapter_use.xml
@@ -9,241 +9,241 @@
       are most likely keen to get started capturing your first packets.  In
       the next chapters we will explore:
       <itemizedlist>
-	<listitem>
-	  <para>
-	    How the Wireshark user interface works
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to capture packets in <application>Wireshark</application>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to view packets in <application>Wireshark</application>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    How to filter packets in <application>Wireshark</application>
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    ... and many other things!
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        How the Wireshark user interface works
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to capture packets in <application>Wireshark</application>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to view packets in <application>Wireshark</application>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        How to filter packets in <application>Wireshark</application>
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        ... and many other things!
+      </para>
+    </listitem>
       </itemizedlist>
     </para>
   </section>
 
   <section id="ChUseStartSection"><title>Start Wireshark</title>
     <para>
-	You can start Wireshark from your shell or window manager.
-	<tip><title>Tip!</title>
-	<para>
-	When starting Wireshark it's possible to specify optional settings using
-	the	command line. See <xref linkend="ChCustCommandLine"/> for details.
-	</para>
-	</tip>
-	<note><title>Note!</title>
-	<para>
-	In the following chapters, a lot of screenshots from Wireshark will be shown.
-	As Wireshark runs on many different platforms with many different window
-	managers, different styles applied and there are different versions of the
-	underlying GUI toolkit used, your screen might look different from the provided
-	screenshots. But as there are no real differences in functionality, these
-	screenshots should still be well understandable.
-	</para>
-	</note>
-	</para>
+    You can start Wireshark from your shell or window manager.
+    <tip><title>Tip!</title>
+    <para>
+    When starting Wireshark it's possible to specify optional settings using
+    the    command line. See <xref linkend="ChCustCommandLine"/> for details.
+    </para>
+    </tip>
+    <note><title>Note!</title>
+    <para>
+    In the following chapters, a lot of screenshots from Wireshark will be shown.
+    As Wireshark runs on many different platforms with many different window
+    managers, different styles applied and there are different versions of the
+    underlying GUI toolkit used, your screen might look different from the provided
+    screenshots. But as there are no real differences in functionality, these
+    screenshots should still be well understandable.
+    </para>
+    </note>
+    </para>
   </section>
 
   <section id="ChUseMainWindowSection"><title>The Main window</title>
-	<para>
+    <para>
       Let's look at Wireshark's user interface. <xref linkend="ChUseFig01"/> shows
-	Wireshark as you would usually see it after some packets are captured or loaded
-	(how to do this will be described later).
-	<figure id="ChUseFig01">
-	  <title>The Main window</title>
-	  <graphic scale="100" entityref="WiresharkThreePane1" format="PNG"/>
-	</figure>
+    Wireshark as you would usually see it after some packets are captured or loaded
+    (how to do this will be described later).
+    <figure id="ChUseFig01">
+      <title>The Main window</title>
+      <graphic scale="100" entityref="WiresharkThreePane1" format="PNG"/>
+    </figure>
     </para>
     <para>
       Wireshark's main window consists of parts that are commonly known from many
-	  other GUI programs.
+      other GUI programs.
       <orderedlist>
-	<listitem>
-	  <para>
-	    The <emphasis>menu</emphasis> (see <xref linkend="ChUseMenuSection"/>)
-		is used to start actions.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>main toolbar</emphasis> (see <xref linkend="ChUseMainToolbarSection"/>)
-		provides quick access to frequently used items from the menu.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>filter toolbar</emphasis> (see <xref linkend="ChUseFilterToolbarSection"/>)
-		provides a way to directly manipulate the currently used display filter
-		(see <xref linkend="ChWorkDisplayFilterSection"/>).
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>packet list pane</emphasis> (see <xref linkend="ChUsePacketListPaneSection"/>)
-		displays a summary of each packet captured.  By clicking on packets
-		in this pane you control what is displayed in the other two panes.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>packet details pane</emphasis> (see <xref linkend="ChUsePacketDetailsPaneSection"/>)
-		displays the packet selected in the packet list pane in more detail.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>packet bytes pane</emphasis> (see <xref linkend="ChUsePacketBytesPaneSection"/>)
-		displays the data from the packet selected in the packet list pane, and
-		highlights the field selected in the packet details pane.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    The <emphasis>statusbar</emphasis> (see <xref linkend="ChUseStatusbarSection"/>)
-		shows some detailed information about the current program state and
-		the captured data.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        The <emphasis>menu</emphasis> (see <xref linkend="ChUseMenuSection"/>)
+        is used to start actions.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>main toolbar</emphasis> (see <xref linkend="ChUseMainToolbarSection"/>)
+        provides quick access to frequently used items from the menu.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>filter toolbar</emphasis> (see <xref linkend="ChUseFilterToolbarSection"/>)
+        provides a way to directly manipulate the currently used display filter
+        (see <xref linkend="ChWorkDisplayFilterSection"/>).
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>packet list pane</emphasis> (see <xref linkend="ChUsePacketListPaneSection"/>)
+        displays a summary of each packet captured.  By clicking on packets
+        in this pane you control what is displayed in the other two panes.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>packet details pane</emphasis> (see <xref linkend="ChUsePacketDetailsPaneSection"/>)
+        displays the packet selected in the packet list pane in more detail.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>packet bytes pane</emphasis> (see <xref linkend="ChUsePacketBytesPaneSection"/>)
+        displays the data from the packet selected in the packet list pane, and
+        highlights the field selected in the packet details pane.
+      </para>
+    </listitem>
+    <listitem>
+      <para>
+        The <emphasis>statusbar</emphasis> (see <xref linkend="ChUseStatusbarSection"/>)
+        shows some detailed information about the current program state and
+        the captured data.
+      </para>
+    </listitem>
       </orderedlist>
-	  <tip><title>Tip!</title>
-	  <para>
-	  The layout of the main window can be customized by changing preference settings.
-	  See <xref linkend="ChCustPreferencesSection"/> for details!
-	  </para>
-	  </tip>
+      <tip><title>Tip!</title>
+      <para>
+      The layout of the main window can be customized by changing preference settings.
+      See <xref linkend="ChCustPreferencesSection"/> for details!
+      </para>
+      </tip>
     </para>
 
 
     <section id="ChUseMainWindowNavSection"><title>Main Window Navigation</title>
-	<para>
+    <para>
           Packet list and detail navigation can be done entirely from the
           keyboard.  <xref linkend="ChUseTabNav"/> shows a list of keystrokes
           that will let you quickly move around a capture file.  See
           <xref linkend="ChUseTabGo"/> for additional navigation keystrokes.
         </para>
-	<table id="ChUseTabNav" frame="none">
+    <table id="ChUseTabNav" frame="none">
 
-	<title>Keyboard Navigation</title>
-	  <tgroup cols="2">
-	    <colspec colnum="1" colwidth="72pt"/>
-	      <thead>
-		<row>
-		  <entry>Accelerator</entry>
-		  <entry>Description</entry>
-		</row>
-	      </thead>
-	      <tbody>
-		<row>
-		  <entry>Tab, Shift+Tab</entry>
-		  <entry><para>
-		      Move between screen elements, e.g. from the toolbars
+    <title>Keyboard Navigation</title>
+      <tgroup cols="2">
+        <colspec colnum="1" colwidth="72pt"/>
+          <thead>
+        <row>
+          <entry>Accelerator</entry>
+          <entry>Description</entry>
+        </row>
+          </thead>
+          <tbody>
+        <row>
+          <entry>Tab, Shift+Tab</entry>
+          <entry><para>
+              Move between screen elements, e.g. from the toolbars
                       to the packet list to the packet detail.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Down</entry>
-		  <entry><para>
-		      Move to the next packet or detail item.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Up</entry>
-		  <entry><para>
-		      Move to the previous packet or detail item.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+Down, F8</entry>
-		  <entry><para>
-		      Move to the next packet, even if the packet
+            </para></entry>
+        </row>
+        <row>
+          <entry>Down</entry>
+          <entry><para>
+              Move to the next packet or detail item.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Up</entry>
+          <entry><para>
+              Move to the previous packet or detail item.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+Down, F8</entry>
+          <entry><para>
+              Move to the next packet, even if the packet
                       list isn't focused.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+Up, F7</entry>
-		  <entry><para>
-		      Move to the previous packet, even if the packet
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+Up, F7</entry>
+          <entry><para>
+              Move to the previous packet, even if the packet
                       list isn't focused.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+.</entry>
-		  <entry><para>
-		      Move to the next packet of the conversation
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+.</entry>
+          <entry><para>
+              Move to the next packet of the conversation
                       (TCP, UDP or IP)
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+,</entry>
-		  <entry><para>
-		      Move to the previous packet of the conversation
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+,</entry>
+          <entry><para>
+              Move to the previous packet of the conversation
                       (TCP, UDP or IP)
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Left</entry>
-		  <entry><para>
-		      In the packet detail, closes the selected tree item.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Left</entry>
+          <entry><para>
+              In the packet detail, closes the selected tree item.
                       If it's already closed, jumps to the parent node.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Right</entry>
-		  <entry><para>
-		      In the packet detail, opens the selected tree item.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Shift+Right</entry>
-		  <entry><para>
-		      In the packet detail, opens the selected tree item
+            </para></entry>
+        </row>
+        <row>
+          <entry>Right</entry>
+          <entry><para>
+              In the packet detail, opens the selected tree item.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Shift+Right</entry>
+          <entry><para>
+              In the packet detail, opens the selected tree item
                       and all of its subtrees.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+Right</entry>
-		  <entry><para>
-		      In the packet detail, opens all tree items.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Ctrl+Left</entry>
-		  <entry><para>
-		      In the packet detail, closes all tree items.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Backspace</entry>
-		  <entry><para>
-		      In the packet detail, jumps to the parent node.
-		    </para></entry>
-		</row>
-		<row>
-		  <entry>Return, Enter</entry>
-		  <entry><para>
-		      In the packet detail, toggles the selected
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+Right</entry>
+          <entry><para>
+              In the packet detail, opens all tree items.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Ctrl+Left</entry>
+          <entry><para>
+              In the packet detail, closes all tree items.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Backspace</entry>
+          <entry><para>
+              In the packet detail, jumps to the parent node.
+            </para></entry>
+        </row>
+        <row>
+          <entry>Return, Enter</entry>
+          <entry><para>
+              In the packet detail, toggles the selected
                       tree item.
-		    </para></entry>
-		</row>
-	      </tbody>
-	  </tgroup>
-	</table>
+            </para></entry>
+        </row>
+          </tbody>
+      </tgroup>
+    </table>
         <para>
         Additionally, typing anywhere in the main window will start filling
         in a display filter.
@@ -256,133 +256,133 @@
       The Wireshark menu sits on top of the Wireshark window.
       An example is shown in <xref linkend="ChUseWiresharkMenu"/>.
     </para>
-	<note><title>Note!</title>
-	<para>
-	Menu items will be greyed out if the corresponding feature isn't
-	available. For example, you cannot save a capture file if you didn't
-	capture or load any data before.
-	</para>
-	</note>
+    <note><title>Note!</title>
     <para>
-	<figure id="ChUseWiresharkMenu"><title>The Menu</title>
-	  <graphic entityref="WiresharkMenuOnly" format="PNG"/>
-	</figure>
+    Menu items will be greyed out if the corresponding feature isn't
+    available. For example, you cannot save a capture file if you didn't
+    capture or load any data before.
+    </para>
+    </note>
+    <para>
+    <figure id="ChUseWiresharkMenu"><title>The Menu</title>
+      <graphic entityref="WiresharkMenuOnly" format="PNG"/>
+    </figure>
     </para>
     <para>
       It contains the following items:
       <variablelist>
-	<varlistentry><term><command>File</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items to open and merge capture files,
-		  save / print / export capture files in whole or in part,
-		  and to quit from Wireshark. See <xref linkend="ChUseFileMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Edit</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items to find a packet, time reference or mark one
-		  or more packets, handle configuration profiles, and set your preferences;
-	      (cut, copy, and paste are not presently implemented).
-		  See <xref linkend="ChUseEditMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>View</command></term>
-	  <listitem>
-	    <para>This menu controls the display of the captured data,
-		including colorization of packets, zooming the font,
-		showing a packet in a separate window, expanding and collapsing trees in packet details, ....
-		See <xref linkend="ChUseViewMenuSection"/>.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Go</command></term>
-	  <listitem>
-	    <para>This menu contains items to go to a specific packet.
-		See <xref linkend="ChUseGoMenuSection"/>.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Capture</command></term>
-	  <listitem>
-	    <para>This menu allows you to start and stop captures and to edit capture filters.
-		See <xref linkend="ChUseCaptureMenuSection"/>.
-		</para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Analyze</command></term>
-	  <listitem>
-	    <para>
-		  This menu contains items to manipulate display filters, enable or
-		  disable the dissection of protocols, configure user specified decodes
-		  and follow a TCP stream.
-		  See <xref linkend="ChUseAnalyzeMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Statistics</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items to display various statistic windows,
-		  including a summary of the packets that have been captured,
-		  display protocol hierarchy statistics and much more.
-		  See <xref linkend="ChUseStatisticsMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Telephony</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items to display various telephony related
-		  statistic windows, including a media analysis, flow diagrams,
-		  display protocol hierarchy statistics and much more.
-		  See <xref linkend="ChUseTelephonyMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Tools</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains various tools available in Wireshark, such as
-	          creating Firewall ACL Rules.
-		  See <xref linkend="ChUseToolsMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Internals</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items that show information about the internals
-	      of Wireshark.
-		  See <xref linkend="ChUseInternalsMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Help</command></term>
-	  <listitem>
-	    <para>
-	      This menu contains items to help the user, e.g. access to some basic
-		  help, manual pages of the various command line tools, online access
-		  to some of the webpages, and the usual about dialog.
-		  See <xref linkend="ChUseHelpMenuSection"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	</variablelist>
+    <varlistentry><term><command>File</command></term>
+      <listitem>
+        <para>
+          This menu contains items to open and merge capture files,
+          save / print / export capture files in whole or in part,
+          and to quit from Wireshark. See <xref linkend="ChUseFileMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Edit</command></term>
+      <listitem>
+        <para>
+          This menu contains items to find a packet, time reference or mark one
+          or more packets, handle configuration profiles, and set your preferences;
+          (cut, copy, and paste are not presently implemented).
+          See <xref linkend="ChUseEditMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>View</command></term>
+      <listitem>
+        <para>This menu controls the display of the captured data,
+        including colorization of packets, zooming the font,
+        showing a packet in a separate window, expanding and collapsing trees in packet details, ....
+        See <xref linkend="ChUseViewMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Go</command></term>
+      <listitem>
+        <para>This menu contains items to go to a specific packet.
+        See <xref linkend="ChUseGoMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Capture</command></term>
+      <listitem>
+        <para>This menu allows you to start and stop captures and to edit capture filters.
+        See <xref linkend="ChUseCaptureMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Analyze</command></term>
+      <listitem>
+        <para>
+          This menu contains items to manipulate display filters, enable or
+          disable the dissection of protocols, configure user specified decodes
+          and follow a TCP stream.
+          See <xref linkend="ChUseAnalyzeMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Statistics</command></term>
+      <listitem>
+        <para>
+          This menu contains items to display various statistic windows,
+          including a summary of the packets that have been captured,
+          display protocol hierarchy statistics and much more.
+          See <xref linkend="ChUseStatisticsMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Telephony</command></term>
+      <listitem>
+        <para>
+          This menu contains items to display various telephony related
+          statistic windows, including a media analysis, flow diagrams,
+          display protocol hierarchy statistics and much more.
+          See <xref linkend="ChUseTelephonyMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Tools</command></term>
+      <listitem>
+        <para>
+          This menu contains various tools available in Wireshark, such as
+              creating Firewall ACL Rules.
+          See <xref linkend="ChUseToolsMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Internals</command></term>
+      <listitem>
+        <para>
+          This menu contains items that show information about the internals
+          of Wireshark.
+          See <xref linkend="ChUseInternalsMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Help</command></term>
+      <listitem>
+        <para>
+          This menu contains items to help the user, e.g. access to some basic
+          help, manual pages of the various command line tools, online access
+          to some of the webpages, and the usual about dialog.
+          See <xref linkend="ChUseHelpMenuSection"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    </variablelist>
       Each of these menu items is described in more detail in the sections
-	  that follow.
+      that follow.
     </para>
-	<tip><title>Tip!</title>
-	<para>
-	You can access menu items directly or by pressing the corresponding
-	accelerator keys which are shown at the right side of the
-	menu. For example, you can press the Control (or Strg in German) and the K
-	keys together to open the capture dialog.
-	</para>
-	</tip>
+    <tip><title>Tip!</title>
+    <para>
+    You can access menu items directly or by pressing the corresponding
+    accelerator keys which are shown at the right side of the
+    menu. For example, you can press the Control (or Strg in German) and the K
+    keys together to open the capture dialog.
+    </para>
+    </tip>
   </section>
 
   <section id="ChUseFileMenuSection"><title>The "File" menu</title>
@@ -396,214 +396,214 @@
     </figure>
     <table id="ChUseTabFile" frame="none"><title>File menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Open...</command></entry>
-		<entry>Ctrl+O</entry>
-		<entry><para>
-		    This menu item brings up the file open dialog box that
-		    allows you to load a capture file for viewing. It is
-		    discussed in more detail in <xref linkend="ChIOOpen"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Open Recent</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item shows a submenu containing the recently opened
-			capture files. Clicking on one of the submenu items will open the
-			corresponding capture file directly.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Merge...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up the merge file dialog box that
-		    allows you to merge a capture file into the currently loaded one.
-			It is discussed in more detail in <xref linkend="ChIOMergeSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Import...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up the import file dialog box that
-		    allows you to import a text file into a new temporary capture.
-			It is discussed in more detail in <xref linkend="ChIOImportSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Close</command></entry>
-		<entry>Ctrl+W</entry>
-		<entry><para>
-		    This menu item closes the current capture. If you
-		    haven't saved the capture, you will be asked to do so first
-			 (this can be disabled by a preference setting).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Save</command></entry>
-		<entry>Ctrl+S</entry>
-		<entry><para>
-		    This menu item saves the current capture. If you
-		    have not set a default capture file name (perhaps with
-		    the -w &lt;capfile&gt; option), Wireshark pops up the
-		    Save Capture File As dialog box (which is discussed
-		    further in <xref linkend="ChIOSaveAs"/>).
-		  </para><note>
-		    <title>Note!</title>
-		    <para>
-		      If you have already saved the current capture, this
-		      menu item will be greyed out.
-		    </para>
-		  </note><note>
-		    <title>Note!</title>
-		    <para>
-		      You cannot save a live capture while the capture is in
-		      progress.  You must stop the capture in order to
-		      save.
-		    </para>
-		  </note></entry>
-	      </row>
-	      <row>
-		<entry><command>Save As...</command></entry>
-		<entry>Shift+Ctrl+S</entry>
-		<entry><para>
-		    This menu item allows you to save the current capture
-		    file to whatever file you would like. It pops up the
-		    Save Capture File As dialog box (which is discussed
-		    further in <xref linkend="ChIOSaveAs"/>).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>File Set > List Files</command></entry>
-		<entry></entry>
-		<entry><para>
-			This menu item allows you to show a list of files in a file set.
-			It pops up the Wireshark List File Set dialog box (which is
-			discussed further in <xref linkend="ChIOFileSetSection"/>).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>File Set > Next File</command></entry>
-		<entry></entry>
-		<entry><para>
-			If the currently loaded file is part of a file set, jump to the
-			next file in the set. If it isn't part of a file set or just the
-			last file in that set, this item is greyed out.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>File Set > Previous File</command></entry>
-		<entry></entry>
-		<entry><para>
-			If the currently loaded file is part of a file set, jump to the
-			previous file in the set. If it isn't part of a file set or just
-			the first file in that set, this item is greyed out.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Export > File...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows you to export all (or some) of the packets in
-		    the capture file to file.
-		    It pops up the Wireshark Export dialog box (which is discussed further in
-		    <xref linkend="ChIOExportSection"/>).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Export > Selected Packet Bytes...</command></entry>
-		<entry>Ctrl+H</entry>
-		<entry><para>
-		    This menu item allows you to export the currently selected bytes
-			in the packet bytes pane to a binary file. It pops up the
-			Wireshark Export dialog box (which is discussed further in
-		    <xref linkend="ChIOExportSelectedDialog"/>)
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Export > Objects > HTTP</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows you to export all or some of the captured HTTP objects
-		    into local files. It pops up the Wireshark HTTP object list (which is discussed
-		    further in <xref linkend="ChIOExportObjectsDialog"/>)
-		</para></entry>
-	      </row>
-	      <row>
-		<entry><command>Export > Objects > DICOM</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows you to export all or some of the captured DICOM objects
-		    into local files. It pops up the Wireshark DICOM object list (which is discussed
-		    further in <xref linkend="ChIOExportObjectsDialog"/>)
-		</para></entry>
-	      </row>
-	      <row>
-		<entry><command>Export > Objects > SMB</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows you to export all or some of the captured SMB objects
-		    into local files. It pops up the Wireshark SMB object list (which is discussed
-		    further in <xref linkend="ChIOExportObjectsDialog"/>)
-		</para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Print...</command></entry>
-		<entry>Ctrl+P</entry>
-		<entry><para>
-		    This menu item allows you to print all (or some) of the packets in
-		    the capture file. It pops up the Wireshark Print dialog
-		    box (which is discussed further in
-		    <xref linkend="ChIOPrintSection"/>).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Quit</command></entry>
-		<entry>Ctrl+Q</entry>
-		<entry><para>
-		    This menu item allows you to quit from Wireshark.
-			Wireshark will ask to save your capture file if you haven't previously saved
-			it (this can be disabled by a preference setting).
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Open...</command></entry>
+        <entry>Ctrl+O</entry>
+        <entry><para>
+            This menu item brings up the file open dialog box that
+            allows you to load a capture file for viewing. It is
+            discussed in more detail in <xref linkend="ChIOOpen"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Open Recent</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item shows a submenu containing the recently opened
+            capture files. Clicking on one of the submenu items will open the
+            corresponding capture file directly.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Merge...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up the merge file dialog box that
+            allows you to merge a capture file into the currently loaded one.
+            It is discussed in more detail in <xref linkend="ChIOMergeSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Import...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up the import file dialog box that
+            allows you to import a text file into a new temporary capture.
+            It is discussed in more detail in <xref linkend="ChIOImportSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Close</command></entry>
+        <entry>Ctrl+W</entry>
+        <entry><para>
+            This menu item closes the current capture. If you
+            haven't saved the capture, you will be asked to do so first
+             (this can be disabled by a preference setting).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Save</command></entry>
+        <entry>Ctrl+S</entry>
+        <entry><para>
+            This menu item saves the current capture. If you
+            have not set a default capture file name (perhaps with
+            the -w &lt;capfile&gt; option), Wireshark pops up the
+            Save Capture File As dialog box (which is discussed
+            further in <xref linkend="ChIOSaveAs"/>).
+          </para><note>
+            <title>Note!</title>
+            <para>
+              If you have already saved the current capture, this
+              menu item will be greyed out.
+            </para>
+          </note><note>
+            <title>Note!</title>
+            <para>
+              You cannot save a live capture while the capture is in
+              progress.  You must stop the capture in order to
+              save.
+            </para>
+          </note></entry>
+          </row>
+          <row>
+        <entry><command>Save As...</command></entry>
+        <entry>Shift+Ctrl+S</entry>
+        <entry><para>
+            This menu item allows you to save the current capture
+            file to whatever file you would like. It pops up the
+            Save Capture File As dialog box (which is discussed
+            further in <xref linkend="ChIOSaveAs"/>).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>File Set > List Files</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows you to show a list of files in a file set.
+            It pops up the Wireshark List File Set dialog box (which is
+            discussed further in <xref linkend="ChIOFileSetSection"/>).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>File Set > Next File</command></entry>
+        <entry></entry>
+        <entry><para>
+            If the currently loaded file is part of a file set, jump to the
+            next file in the set. If it isn't part of a file set or just the
+            last file in that set, this item is greyed out.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>File Set > Previous File</command></entry>
+        <entry></entry>
+        <entry><para>
+            If the currently loaded file is part of a file set, jump to the
+            previous file in the set. If it isn't part of a file set or just
+            the first file in that set, this item is greyed out.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Export > File...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows you to export all (or some) of the packets in
+            the capture file to file.
+            It pops up the Wireshark Export dialog box (which is discussed further in
+            <xref linkend="ChIOExportSection"/>).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Export > Selected Packet Bytes...</command></entry>
+        <entry>Ctrl+H</entry>
+        <entry><para>
+            This menu item allows you to export the currently selected bytes
+            in the packet bytes pane to a binary file. It pops up the
+            Wireshark Export dialog box (which is discussed further in
+            <xref linkend="ChIOExportSelectedDialog"/>)
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Export > Objects > HTTP</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows you to export all or some of the captured HTTP objects
+            into local files. It pops up the Wireshark HTTP object list (which is discussed
+            further in <xref linkend="ChIOExportObjectsDialog"/>)
+        </para></entry>
+          </row>
+          <row>
+        <entry><command>Export > Objects > DICOM</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows you to export all or some of the captured DICOM objects
+            into local files. It pops up the Wireshark DICOM object list (which is discussed
+            further in <xref linkend="ChIOExportObjectsDialog"/>)
+        </para></entry>
+          </row>
+          <row>
+        <entry><command>Export > Objects > SMB</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows you to export all or some of the captured SMB objects
+            into local files. It pops up the Wireshark SMB object list (which is discussed
+            further in <xref linkend="ChIOExportObjectsDialog"/>)
+        </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Print...</command></entry>
+        <entry>Ctrl+P</entry>
+        <entry><para>
+            This menu item allows you to print all (or some) of the packets in
+            the capture file. It pops up the Wireshark Print dialog
+            box (which is discussed further in
+            <xref linkend="ChIOPrintSection"/>).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Quit</command></entry>
+        <entry>Ctrl+Q</entry>
+        <entry><para>
+            This menu item allows you to quit from Wireshark.
+            Wireshark will ask to save your capture file if you haven't previously saved
+            it (this can be disabled by a preference setting).
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -620,216 +620,216 @@
     <table id="ChUseTabEdit" frame="none">
       <title>Edit menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Copy > Description</command></entry>
-		<entry>Shift+Ctrl+D</entry>
-		<entry><para>
-			This menu item will copy the description of the selected item
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Copy > Description</command></entry>
+        <entry>Shift+Ctrl+D</entry>
+        <entry><para>
+            This menu item will copy the description of the selected item
                         in the detail view to the clipboard.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Copy > Fieldname</command></entry>
-		<entry>Shift+Ctrl+F</entry>
-		<entry><para>
-			This menu item will copy the fieldname of the selected item
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Copy > Fieldname</command></entry>
+        <entry>Shift+Ctrl+F</entry>
+        <entry><para>
+            This menu item will copy the fieldname of the selected item
                         in the detail view to the clipboard.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Copy > Value</command></entry>
-		<entry>Shift+Ctrl+V</entry>
-		<entry><para>
-			This menu item will copy the value of the selected item
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Copy > Value</command></entry>
+        <entry>Shift+Ctrl+V</entry>
+        <entry><para>
+            This menu item will copy the value of the selected item
                         in the detail view to the clipboard.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Copy > As Filter</command></entry>
-		<entry>Shift+Ctrl+C</entry>
-		<entry><para>
-			This menu item will use the selected item in the detail view to
-			create a display filter. This display filter is then copied to
-			the clipboard.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Packet...</command></entry>
-		<entry>Ctrl+F</entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows you
-		    to find a packet by many criteria.
-		    There is further information on finding packets in
-		    <xref linkend="ChWorkFindPacketSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Next</command></entry>
-		<entry>Ctrl+N</entry>
-		<entry><para>
-		    This menu item tries to find the next packet matching the
-			settings from "Find Packet...".
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Previous</command></entry>
-		<entry>Ctrl+B</entry>
-		<entry><para>
-		    This menu item tries to find the previous packet matching the
-			settings from "Find Packet...".
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Mark Packet (toggle)</command></entry>
-		<entry>Ctrl+M</entry>
-		<entry><para>
-		    This menu item "marks" the currently selected packet. See
-			<xref linkend="ChWorkMarkPacketSection"/> for details.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Toggle Marking Of All Displayed Packets</command></entry>
-		<entry>Shift+Ctrl+Alt+M</entry>
-		<entry><para>
-		    This menu item toggles the mark on all displayed packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Mark All Displayed Packets</command></entry>
-		<entry>Shift+Ctrl+M</entry>
-		<entry><para>
-		    This menu item "marks" all displayed packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Unmark All Displayed Packets</command></entry>
-		<entry>Ctrl+Alt+M</entry>
-		<entry><para>
-		    This menu item "unmarks" all displayed packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Next Mark</command></entry>
-		<entry>Shift+Ctrl+N</entry>
-		<entry><para>
-		    Find the next marked packet.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Previous Mark</command></entry>
-		<entry>Shift+Ctrl+B</entry>
-		<entry><para>
-		    Find the previous marked packet.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Ignore Packet (toggle)</command></entry>
-		<entry>Ctrl+D</entry>
-		<entry><para>
-		    This menu item marks the currently selected packet as ignored.
-		    See <xref linkend="ChWorkIgnorePacketSection"/> for details.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Ignore All Displayed Packets (toggle)</command></entry>
-		<entry>Shift+Ctrl+D</entry>
-		<entry><para>
-		    This menu item marks all displayed packets as ignored.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Un-Ignore All Packets</command></entry>
-		<entry>Ctrl+Alt+D</entry>
-		<entry><para>
-		    This menu item unmarks all ignored packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Set Time Reference (toggle)</command></entry>
-		<entry>Ctrl+T</entry>
-		<entry><para>
-		    This menu item set a time reference on the currently selected
-			packet. See <xref linkend="ChWorkTimeReferencePacketSection"/> for more information
-		      about the time referenced packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Un-Time Reference All Packets</command></entry>
-		<entry>Ctrl+Alt+T</entry>
-		<entry><para>
-		    This menu item removes all time references on the packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Next Time Reference</command></entry>
-		<entry>Ctrl+Alt+N</entry>
-		<entry><para>
-		    This menu item tries to find the next time referenced packet.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Find Previous Time Reference</command></entry>
-		<entry>Ctrl+Alt+B</entry>
-		<entry><para>
-		    This menu item tries to find the previous time referenced packet.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Configuration Profiles...</command></entry>
-		<entry>Shift+Ctrl+A</entry>
-		<entry><para>
-		    This menu item brings up a dialog box for handling configuration
-		    profiles.  More detail is provided in
-		    <xref linkend="ChCustConfigProfilesSection"/>.
-		</para></entry>
-	      </row>
-	      <row>
-		<entry><command>Preferences...</command></entry>
-		<entry>Shift+Ctrl+P</entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows
-		    you to set preferences for many parameters that control
-		    Wireshark.  You can also save your preferences so Wireshark
-		    will use them the next time you start it. More detail
-		    is provided in <xref linkend="ChCustPreferencesSection"/>.
-		  </para></entry>
-	      </row>
-	    </tbody>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Copy > As Filter</command></entry>
+        <entry>Shift+Ctrl+C</entry>
+        <entry><para>
+            This menu item will use the selected item in the detail view to
+            create a display filter. This display filter is then copied to
+            the clipboard.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Find Packet...</command></entry>
+        <entry>Ctrl+F</entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows you
+            to find a packet by many criteria.
+            There is further information on finding packets in
+            <xref linkend="ChWorkFindPacketSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Next</command></entry>
+        <entry>Ctrl+N</entry>
+        <entry><para>
+            This menu item tries to find the next packet matching the
+            settings from "Find Packet...".
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Previous</command></entry>
+        <entry>Ctrl+B</entry>
+        <entry><para>
+            This menu item tries to find the previous packet matching the
+            settings from "Find Packet...".
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Mark Packet (toggle)</command></entry>
+        <entry>Ctrl+M</entry>
+        <entry><para>
+            This menu item "marks" the currently selected packet. See
+            <xref linkend="ChWorkMarkPacketSection"/> for details.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Toggle Marking Of All Displayed Packets</command></entry>
+        <entry>Shift+Ctrl+Alt+M</entry>
+        <entry><para>
+            This menu item toggles the mark on all displayed packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Mark All Displayed Packets</command></entry>
+        <entry>Shift+Ctrl+M</entry>
+        <entry><para>
+            This menu item "marks" all displayed packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Unmark All Displayed Packets</command></entry>
+        <entry>Ctrl+Alt+M</entry>
+        <entry><para>
+            This menu item "unmarks" all displayed packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Next Mark</command></entry>
+        <entry>Shift+Ctrl+N</entry>
+        <entry><para>
+            Find the next marked packet.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Previous Mark</command></entry>
+        <entry>Shift+Ctrl+B</entry>
+        <entry><para>
+            Find the previous marked packet.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Ignore Packet (toggle)</command></entry>
+        <entry>Ctrl+D</entry>
+        <entry><para>
+            This menu item marks the currently selected packet as ignored.
+            See <xref linkend="ChWorkIgnorePacketSection"/> for details.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Ignore All Displayed Packets (toggle)</command></entry>
+        <entry>Shift+Ctrl+D</entry>
+        <entry><para>
+            This menu item marks all displayed packets as ignored.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Un-Ignore All Packets</command></entry>
+        <entry>Ctrl+Alt+D</entry>
+        <entry><para>
+            This menu item unmarks all ignored packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Set Time Reference (toggle)</command></entry>
+        <entry>Ctrl+T</entry>
+        <entry><para>
+            This menu item set a time reference on the currently selected
+            packet. See <xref linkend="ChWorkTimeReferencePacketSection"/> for more information
+              about the time referenced packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Un-Time Reference All Packets</command></entry>
+        <entry>Ctrl+Alt+T</entry>
+        <entry><para>
+            This menu item removes all time references on the packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Next Time Reference</command></entry>
+        <entry>Ctrl+Alt+N</entry>
+        <entry><para>
+            This menu item tries to find the next time referenced packet.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Find Previous Time Reference</command></entry>
+        <entry>Ctrl+Alt+B</entry>
+        <entry><para>
+            This menu item tries to find the previous time referenced packet.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Configuration Profiles...</command></entry>
+        <entry>Shift+Ctrl+A</entry>
+        <entry><para>
+            This menu item brings up a dialog box for handling configuration
+            profiles.  More detail is provided in
+            <xref linkend="ChCustConfigProfilesSection"/>.
+        </para></entry>
+          </row>
+          <row>
+        <entry><command>Preferences...</command></entry>
+        <entry>Shift+Ctrl+P</entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows
+            you to set preferences for many parameters that control
+            Wireshark.  You can also save your preferences so Wireshark
+            will use them the next time you start it. More detail
+            is provided in <xref linkend="ChCustPreferencesSection"/>.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -846,400 +846,400 @@
     <table id="ChUseTabView" frame="none">
       <title>View menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Main Toolbar</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the main toolbar, see
-		  <xref linkend="ChUseMainToolbarSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Filter Toolbar</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the filter toolbar, see
-		  <xref linkend="ChUseFilterToolbarSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Wireless Toolbar (Windows only)</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the wireless toolbar. See
-		    the AirPcap documentation for more information.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Statusbar</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the statusbar, see
-		  <xref linkend="ChUseStatusbarSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Packet List</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the packet list pane, see
-		  <xref linkend="ChUsePacketListPaneSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Packet Details</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the packet details pane, see
-		  <xref linkend="ChUsePacketDetailsPaneSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Packet Bytes</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item hides or shows the packet bytes pane, see
-		  <xref linkend="ChUsePacketBytesPaneSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Date and Time of Day:  1970-01-01 01:02:03.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display the
-	      time stamps in date and time of day format, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  <note><title>Note!</title>
-		  <para>
-		  The fields "Time of Day", "Date and Time of
-	      Day", "Seconds Since Beginning of Capture", "Seconds Since
-	      Previous Captured Packet" and "Seconds Since Previous
-	      Displayed Packet" are mutually exclusive.
-		  </para>
-		  </note>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Time of Day:  01:02:03.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time
-	      stamps in time of day format, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Seconds Since Epoch (1970-01-01):  1234567890.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps in
-	      seconds since 1970-01-01 00:00:00, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Seconds Since Beginning of Capture:  123.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time
-	      stamps in seconds since beginning of capture format, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Seconds Since Previous Captured Packet:  1.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps in
-	      seconds since previous captured packet format, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Seconds Since Previous Displayed Packet:  1.123456</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps in
-	      seconds since previous displayed packet format, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > ------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Automatic (File Format Precision)</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps with the
-		  precision given by the capture file format used, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  <note><title>Note!</title>
-		  <para>
-		  The fields "Automatic", "Seconds" and "...seconds" are mutually exclusive.
-		  </para>
-		  </note>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Seconds:  0</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps with a precision of one second, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > ...seconds:  0....</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps with a precision of one second,
-	      decisecond, centisecond, millisecond, microsecond or nanosecond, see
-		  <xref linkend="ChWorkTimeFormatsSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Time Display Format > Display Seconds with hours and minutes</command></entry>
-		<entry></entry>
-		<entry><para>
-	      Selecting this tells Wireshark to display time stamps in seconds,
-	      with hours and minutes.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Name Resolution > Resolve Name</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to trigger a name resolve of the current packet
-		only, see <xref linkend="ChAdvNameResolutionSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Name Resolution > Enable for MAC Layer</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to control whether or not
-		Wireshark translates MAC addresses into names, see
-		  <xref linkend="ChAdvNameResolutionSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Name Resolution > Enable for Network Layer</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to control whether or not
-		Wireshark translates network addresses into names, see
-		  <xref linkend="ChAdvNameResolutionSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Name Resolution > Enable for Transport Layer</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to control whether or not
-		Wireshark translates transport addresses into names, see
-		  <xref linkend="ChAdvNameResolutionSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Packet List</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to control whether or not Wireshark should colorize
-		the packet list.</para>
-		<note><title>Note!</title><para>
-		Enabling colorization will slow down the display
-		of new packets while capturing / loading capture files.
-		  </para></note></entry>
-	      </row>
-	      <row>
-		<entry><command>Auto Scroll in Live Capture</command></entry>
-		<entry></entry>
-		<entry><para>
-		This item allows you to specify that Wireshark
-		should scroll the packet list pane as new packets come
-		in, so you are always looking at the last packet.  If you
-		do not specify this, Wireshark simply adds new packets onto
-		the end of the list, but does not scroll the packet list
-		pane.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Zoom In</command></entry>
-		<entry>Ctrl++</entry>
-		<entry><para>
-		  Zoom into the packet data (increase the font size).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Zoom Out</command></entry>
-		<entry>Ctrl+-</entry>
-		<entry><para>
-		  Zoom out of the packet data (decrease the font size).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Normal Size</command></entry>
-		<entry>Ctrl+=</entry>
-		<entry><para>
-		  Set zoom level back to 100% (set font size back to normal).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Resize All Columns</command></entry>
-		<entry>Shift+Ctrl+R</entry>
-		<entry><para>
-		  Resize all column widths so the content will fit into it.
-		  </para>
-		  <note><title>Note!</title><para>
-		  Resizing may take a significant amount of time, especially if a
-		  large capture file is loaded.
-		  </para></note>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><command>Displayed Columns</command></entry>
-		<entry></entry>
-		<entry><para>
-		  This menu items folds out with a list of all configured columns.
-		  These columns can now be shown or hidden in the packet list.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Expand Subtrees</command></entry>
-		<entry>Shift+Right</entry>
-		<entry><para>
-		    This menu item expands the currently selected subtree in the
-		    packet details tree.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Expand All</command></entry>
-		<entry>Ctrl+Right</entry>
-		<entry><para>
-		    Wireshark keeps a list of all the protocol subtrees
-		    that are expanded, and uses it to ensure that the
-		    correct subtrees are expanded when you display a packet.
-		    This menu item expands all subtrees in all packets in
-		    the capture.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Collapse All</command></entry>
-		<entry>Ctrl+Left</entry>
-		<entry><para>
-		    This menu item collapses the tree view of all packets
-		    in the capture list.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Conversation</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a submenu that allows you
-		    to color packets in the packet list pane based
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Main Toolbar</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the main toolbar, see
+          <xref linkend="ChUseMainToolbarSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Filter Toolbar</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the filter toolbar, see
+          <xref linkend="ChUseFilterToolbarSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Wireless Toolbar (Windows only)</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the wireless toolbar. See
+            the AirPcap documentation for more information.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Statusbar</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the statusbar, see
+          <xref linkend="ChUseStatusbarSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Packet List</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the packet list pane, see
+          <xref linkend="ChUsePacketListPaneSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Packet Details</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the packet details pane, see
+          <xref linkend="ChUsePacketDetailsPaneSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Packet Bytes</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item hides or shows the packet bytes pane, see
+          <xref linkend="ChUsePacketBytesPaneSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Date and Time of Day:  1970-01-01 01:02:03.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display the
+          time stamps in date and time of day format, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          <note><title>Note!</title>
+          <para>
+          The fields "Time of Day", "Date and Time of
+          Day", "Seconds Since Beginning of Capture", "Seconds Since
+          Previous Captured Packet" and "Seconds Since Previous
+          Displayed Packet" are mutually exclusive.
+          </para>
+          </note>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Time of Day:  01:02:03.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time
+          stamps in time of day format, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Seconds Since Epoch (1970-01-01):  1234567890.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps in
+          seconds since 1970-01-01 00:00:00, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Seconds Since Beginning of Capture:  123.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time
+          stamps in seconds since beginning of capture format, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Seconds Since Previous Captured Packet:  1.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps in
+          seconds since previous captured packet format, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Seconds Since Previous Displayed Packet:  1.123456</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps in
+          seconds since previous displayed packet format, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > ------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Automatic (File Format Precision)</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps with the
+          precision given by the capture file format used, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          <note><title>Note!</title>
+          <para>
+          The fields "Automatic", "Seconds" and "...seconds" are mutually exclusive.
+          </para>
+          </note>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Seconds:  0</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps with a precision of one second, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > ...seconds:  0....</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps with a precision of one second,
+          decisecond, centisecond, millisecond, microsecond or nanosecond, see
+          <xref linkend="ChWorkTimeFormatsSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Time Display Format > Display Seconds with hours and minutes</command></entry>
+        <entry></entry>
+        <entry><para>
+          Selecting this tells Wireshark to display time stamps in seconds,
+          with hours and minutes.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Name Resolution > Resolve Name</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to trigger a name resolve of the current packet
+        only, see <xref linkend="ChAdvNameResolutionSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Name Resolution > Enable for MAC Layer</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to control whether or not
+        Wireshark translates MAC addresses into names, see
+          <xref linkend="ChAdvNameResolutionSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Name Resolution > Enable for Network Layer</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to control whether or not
+        Wireshark translates network addresses into names, see
+          <xref linkend="ChAdvNameResolutionSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Name Resolution > Enable for Transport Layer</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to control whether or not
+        Wireshark translates transport addresses into names, see
+          <xref linkend="ChAdvNameResolutionSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Colorize Packet List</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to control whether or not Wireshark should colorize
+        the packet list.</para>
+        <note><title>Note!</title><para>
+        Enabling colorization will slow down the display
+        of new packets while capturing / loading capture files.
+          </para></note></entry>
+          </row>
+          <row>
+        <entry><command>Auto Scroll in Live Capture</command></entry>
+        <entry></entry>
+        <entry><para>
+        This item allows you to specify that Wireshark
+        should scroll the packet list pane as new packets come
+        in, so you are always looking at the last packet.  If you
+        do not specify this, Wireshark simply adds new packets onto
+        the end of the list, but does not scroll the packet list
+        pane.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Zoom In</command></entry>
+        <entry>Ctrl++</entry>
+        <entry><para>
+          Zoom into the packet data (increase the font size).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Zoom Out</command></entry>
+        <entry>Ctrl+-</entry>
+        <entry><para>
+          Zoom out of the packet data (decrease the font size).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Normal Size</command></entry>
+        <entry>Ctrl+=</entry>
+        <entry><para>
+          Set zoom level back to 100% (set font size back to normal).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Resize All Columns</command></entry>
+        <entry>Shift+Ctrl+R</entry>
+        <entry><para>
+          Resize all column widths so the content will fit into it.
+          </para>
+          <note><title>Note!</title><para>
+          Resizing may take a significant amount of time, especially if a
+          large capture file is loaded.
+          </para></note>
+          </entry>
+          </row>
+          <row>
+        <entry><command>Displayed Columns</command></entry>
+        <entry></entry>
+        <entry><para>
+          This menu items folds out with a list of all configured columns.
+          These columns can now be shown or hidden in the packet list.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Expand Subtrees</command></entry>
+        <entry>Shift+Right</entry>
+        <entry><para>
+            This menu item expands the currently selected subtree in the
+            packet details tree.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Expand All</command></entry>
+        <entry>Ctrl+Right</entry>
+        <entry><para>
+            Wireshark keeps a list of all the protocol subtrees
+            that are expanded, and uses it to ensure that the
+            correct subtrees are expanded when you display a packet.
+            This menu item expands all subtrees in all packets in
+            the capture.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Collapse All</command></entry>
+        <entry>Ctrl+Left</entry>
+        <entry><para>
+            This menu item collapses the tree view of all packets
+            in the capture list.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Colorize Conversation</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a submenu that allows you
+            to color packets in the packet list pane based
                     on the addresses of the currently selected packet.
                     This makes it easy to distinguish packets
                     belonging to different conversations.
-		  <xref linkend="ChCustColorizationSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Conversation > Color 1-10</command></entry>
-		<entry></entry>
-		<entry><para>
-		    These menu items enable one of the ten temporary color
+          <xref linkend="ChCustColorizationSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Colorize Conversation > Color 1-10</command></entry>
+        <entry></entry>
+        <entry><para>
+            These menu items enable one of the ten temporary color
                     filters based on the currently selected conversation.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Conversation > Reset coloring</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item clears all temporary coloring rules.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Conversation > New Coloring Rule...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item opens a dialog window in which a new
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Colorize Conversation > Reset coloring</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item clears all temporary coloring rules.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Colorize Conversation > New Coloring Rule...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item opens a dialog window in which a new
                     permanent coloring rule can be created based on the
                     currently selected conversation.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Coloring Rules...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows you
-		    to color packets in the packet list pane according to
-		    filter expressions you choose. It can be very useful
-		    for spotting certain types of packets, see
-		  <xref linkend="ChCustColorizationSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Show Packet in New Window</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up the selected packet in a
-		    separate window. The separate window shows only the
-		    tree view and byte view panes.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Reload</command></entry>
-		<entry>Ctrl+R</entry>
-		<entry><para>
-		    This menu item allows you to reload the current
-		    capture file.
-		  </para></entry>
-	      </row>
-	    </tbody>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Coloring Rules...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows you
+            to color packets in the packet list pane according to
+            filter expressions you choose. It can be very useful
+            for spotting certain types of packets, see
+          <xref linkend="ChCustColorizationSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Show Packet in New Window</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up the selected packet in a
+            separate window. The separate window shows only the
+            tree view and byte view panes.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Reload</command></entry>
+        <entry>Ctrl+R</entry>
+        <entry><para>
+            This menu item allows you to reload the current
+            capture file.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1256,106 +1256,106 @@
     <table id="ChUseTabGo" frame="none">
       <title>Go menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Back</command></entry>
-		<entry>Alt+Left</entry>
-		<entry><para>
-		    Jump to the recently visited packet in the packet
-			history, much like the page history in a web browser.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Forward</command></entry>
-		<entry>Alt+Right</entry>
-		<entry><para>
-		    Jump to the next visited packet in the packet
-			history, much like the page history in a web browser.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Go to Packet...</command></entry>
-		<entry>Ctrl+G</entry>
-		<entry><para>
-		    Bring up a dialog box that allows you
-		    to specify a packet number, and then goes to that packet. See
-			<xref linkend="ChWorkGoToPacketSection"/> for details.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Go to Corresponding Packet</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Go to the corresponding packet of the currently
-			selected protocol field. If the selected field doesn't correspond
-			to a packet, this item is greyed out.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Previous Packet</command></entry>
-		<entry>Ctrl+Up</entry>
-		<entry><para>
-		    Move to the previous packet in the list.  This can be
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Back</command></entry>
+        <entry>Alt+Left</entry>
+        <entry><para>
+            Jump to the recently visited packet in the packet
+            history, much like the page history in a web browser.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Forward</command></entry>
+        <entry>Alt+Right</entry>
+        <entry><para>
+            Jump to the next visited packet in the packet
+            history, much like the page history in a web browser.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Go to Packet...</command></entry>
+        <entry>Ctrl+G</entry>
+        <entry><para>
+            Bring up a dialog box that allows you
+            to specify a packet number, and then goes to that packet. See
+            <xref linkend="ChWorkGoToPacketSection"/> for details.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Go to Corresponding Packet</command></entry>
+        <entry></entry>
+        <entry><para>
+            Go to the corresponding packet of the currently
+            selected protocol field. If the selected field doesn't correspond
+            to a packet, this item is greyed out.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Previous Packet</command></entry>
+        <entry>Ctrl+Up</entry>
+        <entry><para>
+            Move to the previous packet in the list.  This can be
                     used to move to the previous packet even if the packet
                     list doesn't have keyboard focus.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Next Packet</command></entry>
-		<entry>Ctrl+Down</entry>
-		<entry><para>
-		    Move to the next packet in the list.  This can be
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Next Packet</command></entry>
+        <entry>Ctrl+Down</entry>
+        <entry><para>
+            Move to the next packet in the list.  This can be
                     used to move to the previous packet even if the packet
                     list doesn't have keyboard focus.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>First Packet</command></entry>
-		<entry>Ctrl+Home</entry>
-		<entry><para>
-		    Jump to the first packet of the capture file.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Last Packet</command></entry>
-		<entry>Ctrl+End</entry>
-		<entry><para>
-		    Jump to the last packet of the capture file.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Previous Packet In Conversation</command></entry>
-		<entry>Ctrl+,</entry>
-		<entry><para>
-		    Move to the previous packet in the current conversation.  This can be
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>First Packet</command></entry>
+        <entry>Ctrl+Home</entry>
+        <entry><para>
+            Jump to the first packet of the capture file.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Last Packet</command></entry>
+        <entry>Ctrl+End</entry>
+        <entry><para>
+            Jump to the last packet of the capture file.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Previous Packet In Conversation</command></entry>
+        <entry>Ctrl+,</entry>
+        <entry><para>
+            Move to the previous packet in the current conversation.  This can be
                     used to move to the previous packet even if the packet
                     list doesn't have keyboard focus.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Next Packet In Conversation</command></entry>
-		<entry>Ctrl+.</entry>
-		<entry><para>
-		    Move to the next packet in the current conversation.  This can be
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Next Packet In Conversation</command></entry>
+        <entry>Ctrl+.</entry>
+        <entry><para>
+            Move to the next packet in the current conversation.  This can be
                     used to move to the previous packet even if the packet
                     list doesn't have keyboard focus.
-		  </para></entry>
-	      </row>
-	    </tbody>
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1372,71 +1372,71 @@
     <table id="ChUseTabCap" frame="none">
       <title>Capture menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Interfaces...</command></entry>
-		<entry>Ctrl+I</entry>
-		<entry><para>
-		    This menu item brings up a dialog box that shows what's going on
-			at the network interfaces Wireshark knows of, see
-			<xref linkend="ChCapInterfaceSection"/>) .
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Options...</command></entry>
-		<entry>Ctrl+K</entry>
-		<entry><para>
-		    This menu item brings up the Capture Options
-		    dialog box (discussed further in
-		    <xref linkend="ChCapCaptureOptions"/>) and allows you to
-		      start capturing packets.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Start</command></entry>
-		<entry>Ctrl+E</entry>
-		<entry><para>
-		    Immediately start capturing packets with the same settings than
-			the last time.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Stop</command></entry>
-		<entry>Ctrl+E</entry>
-		<entry><para>
-		    This menu item stops the currently running capture, see
-			<xref linkend="ChCapStopSection"/>) .
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Restart</command></entry>
-		<entry>Ctrl+R</entry>
-		<entry><para>
-		    This menu item stops the currently running capture and starts
-			again with the same options, this is just for convenience.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Capture Filters...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows you to
-		    create and edit capture filters. You can name filters,
-		    and you can save them for future use. More detail on
-		    this subject is provided in
-		    <xref linkend="ChWorkDefineFilterSection"/>
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Interfaces...</command></entry>
+        <entry>Ctrl+I</entry>
+        <entry><para>
+            This menu item brings up a dialog box that shows what's going on
+            at the network interfaces Wireshark knows of, see
+            <xref linkend="ChCapInterfaceSection"/>) .
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Options...</command></entry>
+        <entry>Ctrl+K</entry>
+        <entry><para>
+            This menu item brings up the Capture Options
+            dialog box (discussed further in
+            <xref linkend="ChCapCaptureOptions"/>) and allows you to
+              start capturing packets.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Start</command></entry>
+        <entry>Ctrl+E</entry>
+        <entry><para>
+            Immediately start capturing packets with the same settings than
+            the last time.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Stop</command></entry>
+        <entry>Ctrl+E</entry>
+        <entry><para>
+            This menu item stops the currently running capture, see
+            <xref linkend="ChCapStopSection"/>) .
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Restart</command></entry>
+        <entry>Ctrl+R</entry>
+        <entry><para>
+            This menu item stops the currently running capture and starts
+            again with the same options, this is just for convenience.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Capture Filters...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows you to
+            create and edit capture filters. You can name filters,
+            and you can save them for future use. More detail on
+            this subject is provided in
+            <xref linkend="ChWorkDefineFilterSection"/>
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1452,151 +1452,151 @@
     </figure>
     <table id="ChUseAnalyze" frame="none"><title>Analyze menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Display Filters...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows you
-		    to create and edit display filters. You can name
-		    filters, and you can save them for future use. More
-		    detail on this subject is provided in
-		    <xref linkend="ChWorkDefineFilterSection"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Display Filter Macros...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box that allows you
-		    to create and edit display filter macros. You can name
-		    filter macros, and you can save them for future use. More
-		    detail on this subject is provided in
-		    <xref linkend="ChWorkDefineFilterMacrosSection"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Apply as Column</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item adds the selected protocol item in the packet details
-		    pane as a column to the packet list.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Apply as Filter > ...</command></entry>
-		<entry></entry>
-		<entry><para>
-			These menu items will change the current display filter and apply
-			the changed filter immediately. Depending on the chosen menu item,
-			the current display filter string will be replaced or appended to
-			by the selected protocol field in the packet details pane.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Prepare a Filter > ...</command></entry>
-		<entry></entry>
-		<entry><para>
-			These menu items will change the current display filter but won't
-			apply the changed filter. Depending on the chosen menu item,
-			the current display filter string will be replaced or appended to
-			by the selected protocol field in the packet details pane.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-  	      <row>
-		<entry><command>Enabled Protocols...</command></entry>
-		<entry>Shift+Ctrl+E</entry>
-		<entry><para>
-			This menu item allows the user to enable/disable protocol
-			dissectors, see <xref linkend="ChAdvEnabledProtocols"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Decode As...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows the user to force Wireshark to
-		    decode certain packets as a particular protocol, see
-			<xref linkend="ChAdvDecodeAs"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>User Specified Decodes...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item allows the user to force Wireshark to
-		    decode certain packets as a particular protocol, see
-			<xref linkend="ChAdvDecodeAsShow"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Follow TCP Stream</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a separate window and displays
-		    all the TCP segments captured that are on the same TCP
-		    connection as a selected packet, see
-		    <xref linkend="ChAdvFollowTCPSection"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Follow UDP Stream</command></entry>
-		<entry></entry>
-		<entry><para>
-			Same functionality as "Follow TCP Stream" but
-			for UDP streams.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Follow SSL Stream</command></entry>
-		<entry></entry>
-		<entry><para>
-			Same functionality as "Follow TCP Stream" but for SSL streams.
-			XXX - how to provide the SSL keys?
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Expert Info</command></entry>
-		<entry></entry>
-		<entry><para>
-			Open a dialog showing some expert information about the captured
-			packets. The amount of information will depend on the protocol and varies
-			from  very detailed to non-existent. XXX - add a new section about this and link from here
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Conversation Filter > ...</command></entry>
-		<entry></entry>
-		<entry><para>
-			In this menu you will find conversation filter for various
-			protocols.
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Display Filters...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows you
+            to create and edit display filters. You can name
+            filters, and you can save them for future use. More
+            detail on this subject is provided in
+            <xref linkend="ChWorkDefineFilterSection"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Display Filter Macros...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box that allows you
+            to create and edit display filter macros. You can name
+            filter macros, and you can save them for future use. More
+            detail on this subject is provided in
+            <xref linkend="ChWorkDefineFilterMacrosSection"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Apply as Column</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item adds the selected protocol item in the packet details
+            pane as a column to the packet list.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Apply as Filter > ...</command></entry>
+        <entry></entry>
+        <entry><para>
+            These menu items will change the current display filter and apply
+            the changed filter immediately. Depending on the chosen menu item,
+            the current display filter string will be replaced or appended to
+            by the selected protocol field in the packet details pane.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Prepare a Filter > ...</command></entry>
+        <entry></entry>
+        <entry><para>
+            These menu items will change the current display filter but won't
+            apply the changed filter. Depending on the chosen menu item,
+            the current display filter string will be replaced or appended to
+            by the selected protocol field in the packet details pane.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+            <row>
+        <entry><command>Enabled Protocols...</command></entry>
+        <entry>Shift+Ctrl+E</entry>
+        <entry><para>
+            This menu item allows the user to enable/disable protocol
+            dissectors, see <xref linkend="ChAdvEnabledProtocols"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Decode As...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows the user to force Wireshark to
+            decode certain packets as a particular protocol, see
+            <xref linkend="ChAdvDecodeAs"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>User Specified Decodes...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item allows the user to force Wireshark to
+            decode certain packets as a particular protocol, see
+            <xref linkend="ChAdvDecodeAsShow"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Follow TCP Stream</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a separate window and displays
+            all the TCP segments captured that are on the same TCP
+            connection as a selected packet, see
+            <xref linkend="ChAdvFollowTCPSection"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Follow UDP Stream</command></entry>
+        <entry></entry>
+        <entry><para>
+            Same functionality as "Follow TCP Stream" but
+            for UDP streams.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Follow SSL Stream</command></entry>
+        <entry></entry>
+        <entry><para>
+            Same functionality as "Follow TCP Stream" but for SSL streams.
+            XXX - how to provide the SSL keys?
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Expert Info</command></entry>
+        <entry></entry>
+        <entry><para>
+            Open a dialog showing some expert information about the captured
+            packets. The amount of information will depend on the protocol and varies
+            from  very detailed to non-existent. XXX - add a new section about this and link from here
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Conversation Filter > ...</command></entry>
+        <entry></entry>
+        <entry><para>
+            In this menu you will find conversation filter for various
+            protocols.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1611,174 +1611,174 @@
       <graphic entityref="WiresharkStatisticsMenu" format="PNG"/>
     </figure>
     <para>
-	All menu items will bring up a new window showing specific statistical
-	information.
+    All menu items will bring up a new window showing specific statistical
+    information.
     </para>
     <table id="ChUseStatistics" frame="none">
       <title>Statistics menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Summary</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Show information about the data captured, see <xref
-			linkend="ChStatSummary"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Protocol Hierarchy</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display a hierarchical tree of protocol statistics, see <xref
-			linkend="ChStatHierarchy"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Conversations</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display a list of conversations (traffic between two endpoints),
-			see <xref linkend="ChStatConversationsWindow"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Endpoints</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display a list of endpoints (traffic to/from an address), see
-			<xref linkend="ChStatEndpointsWindow"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Packet Lengths...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>IO Graphs</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display user specified graphs (e.g. the number of packets in the
-			course of time), see <xref linkend="ChStatIOGraphs"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Conversation List</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display a list of conversations, obsoleted by the combined window
-			of Conversations above, see
-			<xref linkend="ChStatConversationListWindow"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Endpoint List</command></entry>
-		<entry></entry>
-		<entry><para>
-		    Display a list of endpoints, obsoleted by the combined window
-			of Endpoints above, see
-			<xref linkend="ChStatEndpointListWindow"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Service Response Time</command></entry>
-		<entry></entry>
-		<entry><para>
-			Display the time between a request and the corresponding response, see
-			<xref linkend="ChStatSRT"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>ANCP...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>BOOTP-DHCP...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>Colledtd...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>Compare...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>Flow Graph...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>HTTP</command></entry>
-		<entry></entry>
-		<entry><para>HTTP request/response statistics, see <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>IP Addresses...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>IP Destinations...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>IP Protocol Types...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>ONC-RPC Programs</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>Sametime</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>TCP Stream Graph</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>UDP Multicast Streams</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>WLAN Traffic</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChStatWLANTraffic"/></para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Summary</command></entry>
+        <entry></entry>
+        <entry><para>
+            Show information about the data captured, see <xref
+            linkend="ChStatSummary"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Protocol Hierarchy</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display a hierarchical tree of protocol statistics, see <xref
+            linkend="ChStatHierarchy"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Conversations</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display a list of conversations (traffic between two endpoints),
+            see <xref linkend="ChStatConversationsWindow"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Endpoints</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display a list of endpoints (traffic to/from an address), see
+            <xref linkend="ChStatEndpointsWindow"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Packet Lengths...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>IO Graphs</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display user specified graphs (e.g. the number of packets in the
+            course of time), see <xref linkend="ChStatIOGraphs"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Conversation List</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display a list of conversations, obsoleted by the combined window
+            of Conversations above, see
+            <xref linkend="ChStatConversationListWindow"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Endpoint List</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display a list of endpoints, obsoleted by the combined window
+            of Endpoints above, see
+            <xref linkend="ChStatEndpointListWindow"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Service Response Time</command></entry>
+        <entry></entry>
+        <entry><para>
+            Display the time between a request and the corresponding response, see
+            <xref linkend="ChStatSRT"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>ANCP...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>BOOTP-DHCP...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>Colledtd...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>Compare...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>Flow Graph...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>HTTP</command></entry>
+        <entry></entry>
+        <entry><para>HTTP request/response statistics, see <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>IP Addresses...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>IP Destinations...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>IP Protocol Types...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>ONC-RPC Programs</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>Sametime</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>TCP Stream Graph</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>UDP Multicast Streams</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>WLAN Traffic</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChStatWLANTraffic"/></para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1793,93 +1793,93 @@
       <graphic entityref="WiresharkTelephonyMenu" format="PNG"/>
     </figure>
     <para>
-	All menu items will bring up a new window showing specific telephony
-	related statistical information.
+    All menu items will bring up a new window showing specific telephony
+    related statistical information.
     </para>
     <table id="ChUseTelephony" frame="none">
       <title>Telephony menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>IAX2</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>SMPP Operations...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>SCTP</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>ANSI</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>GSM</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>H.225...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>ISUP Messages...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>LTE</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelLTEMACTraffic"/></para></entry>
-	      </row>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>IAX2</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>SMPP Operations...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>SCTP</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>ANSI</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>GSM</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>H.225...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>ISUP Messages...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>LTE</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelLTEMACTraffic"/></para></entry>
+          </row>
         <row>
-		<entry><command>MTP3</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>RTP</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelRTPAnalysis"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>SIP...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>UCP Messages...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>VoIP Calls...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelVoipCalls"/></para></entry>
-	      </row>
-	      <row>
-		<entry><command>WAP-WSP...</command></entry>
-		<entry></entry>
-		<entry><para>See <xref linkend="ChTelXXX"/></para></entry>
-	      </row>
-	    </tbody>
+        <entry><command>MTP3</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>RTP</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelRTPAnalysis"/></para></entry>
+          </row>
+          <row>
+        <entry><command>SIP...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>UCP Messages...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+          <row>
+        <entry><command>VoIP Calls...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelVoipCalls"/></para></entry>
+          </row>
+          <row>
+        <entry><command>WAP-WSP...</command></entry>
+        <entry></entry>
+        <entry><para>See <xref linkend="ChTelXXX"/></para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1896,38 +1896,38 @@
     <table id="ChUseTools" frame="none">
       <title>Tools menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Firewall ACL Rules</command></entry>
-		<entry></entry>
-		<entry><para>
-		  This allows you to create command-line ACL rules for many different
-			firewall products, including Cisco IOS, Linux Netfilter (iptables),
-			OpenBSD pf and Windows Firewall (via netsh).  Rules for MAC addresses,
-			IPv4 addresses, TCP and UDP ports, and IPv4+port combinations are
-			supported.
-			</para><para>
-			It is assumed that the rules will be applied to an outside interface.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Lua</command></entry>
-		<entry></entry>
-		<entry><para>
-		    These options allow you to work with the Lua interpreter optionally
-		    build into Wireshark, see <xref linkend="wsluarm_intro"/>.
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Firewall ACL Rules</command></entry>
+        <entry></entry>
+        <entry><para>
+          This allows you to create command-line ACL rules for many different
+            firewall products, including Cisco IOS, Linux Netfilter (iptables),
+            OpenBSD pf and Windows Firewall (via netsh).  Rules for MAC addresses,
+            IPv4 addresses, TCP and UDP ports, and IPv4+port combinations are
+            supported.
+            </para><para>
+            It is assumed that the rules will be applied to an outside interface.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Lua</command></entry>
+        <entry></entry>
+        <entry><para>
+            These options allow you to work with the Lua interpreter optionally
+            build into Wireshark, see <xref linkend="wsluarm_intro"/>.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1944,33 +1944,33 @@
     <table id="ChUseInternals" frame="none">
       <title>Help menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Dissector tables</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box showing the tables 
-		    with subdissector relationships.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Supported Protocols (slow!)</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up a dialog box showing the supported
-			protocols and protocol fields.
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Dissector tables</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box showing the tables 
+            with subdissector relationships.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Supported Protocols (slow!)</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up a dialog box showing the supported
+            protocols and protocol fields.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -1987,127 +1987,127 @@
     <table id="ChUseHelp" frame="none">
       <title>Help menu items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="72pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Menu Item</entry>
-		<entry>Accelerator</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Contents</command></entry>
-		<entry>F1</entry>
-		<entry><para>
-		    This menu item brings up a basic help system.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Manual Pages > ...</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing one of the locally
-			installed html manual pages.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Website</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing the 
-			webpage from:
-			<ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>FAQ's</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing various FAQ's.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Downloads</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing the 
-			downloads from:
-			<ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Wiki</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing the 
-			front page from:
-			<ulink url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>Sample Captures</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item starts a Web browser showing the 
-			sample captures from:
-			<ulink url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>About Wireshark</command></entry>
-		<entry></entry>
-		<entry><para>
-		    This menu item brings up an information window that
-		    provides various detailed information items on Wireshark, 
-		    such as how it's build, the plugins loaded, the used folders, ...
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="72pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Menu Item</entry>
+        <entry>Accelerator</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Contents</command></entry>
+        <entry>F1</entry>
+        <entry><para>
+            This menu item brings up a basic help system.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Manual Pages > ...</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing one of the locally
+            installed html manual pages.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Website</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing the 
+            webpage from:
+            <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>FAQ's</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing various FAQ's.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Downloads</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing the 
+            downloads from:
+            <ulink url="&WiresharkWebSite;">&WiresharkWebSite;</ulink>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Wiki</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing the 
+            front page from:
+            <ulink url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>Sample Captures</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item starts a Web browser showing the 
+            sample captures from:
+            <ulink url="&WiresharkWikiPage;">&WiresharkWikiPage;</ulink>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>About Wireshark</command></entry>
+        <entry></entry>
+        <entry><para>
+            This menu item brings up an information window that
+            provides various detailed information items on Wireshark, 
+            such as how it's build, the plugins loaded, the used folders, ...
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
-	<note><title>Note!</title>
-	<para>
-	Calling a Web browser might be unsupported in your version of Wireshark.
-	If this is the case, the corresponding menu items will be hidden.
-	</para>
-	</note>
-	<note><title>Note!</title>
-	<para>
-	If calling a Web browser fails on your machine, maybe because just nothing
-	happens or the browser is started but no page is shown, have a look at the
-	web browser setting in the preferences dialog.
-	</para>
-	</note>
+    <note><title>Note!</title>
+    <para>
+    Calling a Web browser might be unsupported in your version of Wireshark.
+    If this is the case, the corresponding menu items will be hidden.
+    </para>
+    </note>
+    <note><title>Note!</title>
+    <para>
+    If calling a Web browser fails on your machine, maybe because just nothing
+    happens or the browser is started but no page is shown, have a look at the
+    web browser setting in the preferences dialog.
+    </para>
+    </note>
   </section>
 
   <section id="ChUseMainToolbarSection"><title>The "Main" toolbar</title>
     <para>
       The main toolbar provides quick access to frequently used items from the
-	  menu. This toolbar cannot be customized by the user, but it can be hidden
-	  using the View menu, if the space on the screen is needed to show even
-	  more packet data.
+      menu. This toolbar cannot be customized by the user, but it can be hidden
+      using the View menu, if the space on the screen is needed to show even
+      more packet data.
     </para>
     <para>
-	As in the menu, only the items useful in the current program state will
-	be available. The others will be greyed out (e.g. you cannot save a capture
-	file if you haven't loaded one).
+    As in the menu, only the items useful in the current program state will
+    be available. The others will be greyed out (e.g. you cannot save a capture
+    file if you haven't loaded one).
     <figure id="ChUseWiresharkMainToolbar">
       <title>The "Main" toolbar</title>
       <graphic entityref="WiresharkMainToolbar" format="PNG"/>
@@ -2116,313 +2116,313 @@
     <table id="ChUseMainToolbar" frame="none">
       <title>Main toolbar items</title>
       <tgroup cols="4">
-	<colspec colnum="1" colwidth="40pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	  <colspec colnum="3" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Toolbar Icon</entry>
-		<entry>Toolbar Item</entry>
-		<entry>Corresponding Menu Item</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/></entry>
-		<entry><command>Interfaces...</command></entry>
-		<entry>Capture/Interfaces...</entry>
-		<entry><para>
-		    This item brings up the Capture Interfaces List
-		    dialog box (discussed further in
-		    <xref linkend="ChCapCapturingSection"/>).
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/></entry>
-		<entry><command>Options...</command></entry>
-		<entry>Capture/Options...</entry>
-		<entry><para>
-		    This item brings up the Capture Options
-		    dialog box (discussed further in
-		    <xref linkend="ChCapCapturingSection"/>) and allows you to
-		      start capturing packets.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureStart" format="PNG"/></entry>
-		<entry><command>Start</command></entry>
-		<entry>Capture/Start</entry>
-		<entry><para>
-		    This item starts capturing packets with the options form
-			the last time.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureStop" format="PNG"/></entry>
-		<entry><command>Stop</command></entry>
-		<entry>Capture/Stop</entry>
-		<entry><para>
-		    This item stops the currently running live capture process
-			<xref linkend="ChCapCapturingSection"/>).
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/></entry>
-		<entry><command>Restart</command></entry>
-		<entry>Capture/Restart</entry>
-		<entry><para>
-		    This item stops the currently running live capture process
-			and restarts it again, for convenience.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarOpen" format="PNG"/></entry>
-		<entry><command>Open...</command></entry>
-		<entry>File/Open...</entry>
-		<entry><para>
-		    This item brings up the file open dialog box that
-		    allows you to load a capture file for viewing. It is
-		    discussed in more detail in <xref linkend="ChIOOpen"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarSaveAs" format="PNG"/></entry>
-		<entry><command>Save As...</command></entry>
-		<entry>File/Save As...</entry>
-		<entry><para>
-		    This item allows you to save the current capture file to whatever
-			file you would like. It pops up the Save Capture File As dialog
-			box (which is discussed further in <xref linkend="ChIOSaveAs"/>).
-			</para>
-			<note><title>Note!</title>
-			<para>
-			If you currently have a temporary capture file, the Save icon
-			<inlinegraphic entityref="WiresharkToolbarSave" format="PNG"/> will be
-			shown instead.
-		  </para></note>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarClose" format="PNG"/></entry>
-		<entry><command>Close</command></entry>
-		<entry>File/Close</entry>
-		<entry><para>
-		    This item closes the current capture. If you
-		    have not saved the capture, you will be asked to save it first.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarReload" format="PNG"/></entry>
-		<entry><command>Reload</command></entry>
-		<entry>View/Reload</entry>
-		<entry><para>
-		    This item allows you to reload the current capture file.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarPrint" format="PNG"/></entry>
-		<entry><command>Print...</command></entry>
-		<entry>File/Print...</entry>
-		<entry><para>
-		    This item allows you to print all (or some of) the packets in
-		    the capture file. It pops up the Wireshark Print dialog
-		    box (which is discussed further in
-		    <xref linkend="ChIOPrintSection"/>).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarFind" format="PNG"/></entry>
-		<entry><command>Find Packet...</command></entry>
-		<entry>Edit/Find Packet...</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows you
-		    to find a packet. There is further information on finding packets
-			in <xref linkend="ChWorkFindPacketSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarGoBack" format="PNG"/></entry>
-		<entry><command>Go Back</command></entry>
-		<entry>Go/Go Back</entry>
-		<entry><para>
-		    This item jumps back in the packet history.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarGoForward" format="PNG"/></entry>
-		<entry><command>Go Forward</command></entry>
-		<entry>Go/Go Forward</entry>
-		<entry><para>
-		    This item jumps forward in the packet history.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarGoTo" format="PNG"/></entry>
-		<entry><command>Go to Packet...</command></entry>
-		<entry>Go/Go to Packet...</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows you
-		    to specify a packet number to go to that packet.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarGoFirst" format="PNG"/></entry>
-		<entry><command>Go To First Packet</command></entry>
-		<entry>Go/First Packet</entry>
-		<entry><para>
-		    This item jumps to the first packet of the capture file.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarGoLast" format="PNG"/></entry>
-		<entry><command>Go To Last Packet</command></entry>
-		<entry>Go/Last Packet</entry>
-		<entry><para>
-		    This item jumps to the last packet of the capture file.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarColorize" format="PNG"/></entry>
-		<entry><command>Colorize</command></entry>
-		<entry>View/Colorize</entry>
-		<entry><para>
-		  Colorize the packet list (or not).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarAutoScroll" format="PNG"/></entry>
-		<entry><command>Auto Scroll in Live Capture</command></entry>
-		<entry>View/Auto Scroll in Live Capture</entry>
-		<entry><para>
-		  Auto scroll packet list while doing a live capture (or not).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarZoomIn" format="PNG"/></entry>
-		<entry><command>Zoom In</command></entry>
-		<entry>View/Zoom In</entry>
-		<entry><para>
-		  Zoom into the packet data (increase the font size).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarZoomOut" format="PNG"/></entry>
-		<entry><command>Zoom Out</command></entry>
-		<entry>View/Zoom Out</entry>
-		<entry><para>
-		  Zoom out of the packet data (decrease the font size).
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarZoom100" format="PNG"/></entry>
-		<entry><command>Normal Size</command></entry>
-		<entry>View/Normal Size</entry>
-		<entry><para>
-		  Set zoom level back to 100%.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarResizeColumns" format="PNG"/></entry>
-		<entry><command>Resize Columns</command></entry>
-		<entry>View/Resize Columns</entry>
-		<entry><para>
-		  Resize columns, so the content fits into them.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarCaptureFilters" format="PNG"/></entry>
-		<entry><command>Capture Filters...</command></entry>
-		<entry>Capture/Capture Filters...</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows you to
-		    create and edit capture filters. You can name filters,
-		    and you can save them for future use. More detail on
-		    this subject is provided in
-		    <xref linkend="ChWorkDefineFilterSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarDisplayFilters" format="PNG"/></entry>
-		<entry><command>Display Filters...</command></entry>
-		<entry>Analyze/Display Filters...</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows you
-		    to create and edit display filters. You can name
-		    filters, and you can save them for future use. More
-		    detail on this subject is provided in
-		    <xref linkend="ChWorkDefineFilterSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarColoringRules" format="PNG"/></entry>
-		<entry><command>Coloring Rules...</command></entry>
-		<entry>View/Coloring Rules...</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows you
-		    color packets in the packet list pane according to
-		    filter expressions you choose. It can be very useful
-		    for spotting certain types of packets. More
-		    detail on this subject is provided in
-		    <xref linkend="ChCustColorizationSection"/>.
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarPreferences" format="PNG"/></entry>
-		<entry><command>Preferences...</command></entry>
-		<entry>Edit/Preferences</entry>
-		<entry><para>
-		    This item brings up a dialog box that allows
-		    you to set preferences for many parameters that control
-		    Wireshark.  You can also save your preferences so Wireshark
-		    will use them the next time you start it. More detail
-		    is provided in <xref linkend="ChCustPreferencesSection"/>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry><command>------</command></entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarHelp" format="PNG"/></entry>
-		<entry><command>Help</command></entry>
-		<entry>Help/Contents</entry>
-		<entry><para>
-		    This item brings up help dialog box.
-		  </para></entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="40pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+      <colspec colnum="3" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Toolbar Icon</entry>
+        <entry>Toolbar Item</entry>
+        <entry>Corresponding Menu Item</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureInterfaces" format="PNG"/></entry>
+        <entry><command>Interfaces...</command></entry>
+        <entry>Capture/Interfaces...</entry>
+        <entry><para>
+            This item brings up the Capture Interfaces List
+            dialog box (discussed further in
+            <xref linkend="ChCapCapturingSection"/>).
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureOptions" format="PNG"/></entry>
+        <entry><command>Options...</command></entry>
+        <entry>Capture/Options...</entry>
+        <entry><para>
+            This item brings up the Capture Options
+            dialog box (discussed further in
+            <xref linkend="ChCapCapturingSection"/>) and allows you to
+              start capturing packets.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureStart" format="PNG"/></entry>
+        <entry><command>Start</command></entry>
+        <entry>Capture/Start</entry>
+        <entry><para>
+            This item starts capturing packets with the options form
+            the last time.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureStop" format="PNG"/></entry>
+        <entry><command>Stop</command></entry>
+        <entry>Capture/Stop</entry>
+        <entry><para>
+            This item stops the currently running live capture process
+            <xref linkend="ChCapCapturingSection"/>).
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureRestart" format="PNG"/></entry>
+        <entry><command>Restart</command></entry>
+        <entry>Capture/Restart</entry>
+        <entry><para>
+            This item stops the currently running live capture process
+            and restarts it again, for convenience.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarOpen" format="PNG"/></entry>
+        <entry><command>Open...</command></entry>
+        <entry>File/Open...</entry>
+        <entry><para>
+            This item brings up the file open dialog box that
+            allows you to load a capture file for viewing. It is
+            discussed in more detail in <xref linkend="ChIOOpen"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarSaveAs" format="PNG"/></entry>
+        <entry><command>Save As...</command></entry>
+        <entry>File/Save As...</entry>
+        <entry><para>
+            This item allows you to save the current capture file to whatever
+            file you would like. It pops up the Save Capture File As dialog
+            box (which is discussed further in <xref linkend="ChIOSaveAs"/>).
+            </para>
+            <note><title>Note!</title>
+            <para>
+            If you currently have a temporary capture file, the Save icon
+            <inlinegraphic entityref="WiresharkToolbarSave" format="PNG"/> will be
+            shown instead.
+          </para></note>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarClose" format="PNG"/></entry>
+        <entry><command>Close</command></entry>
+        <entry>File/Close</entry>
+        <entry><para>
+            This item closes the current capture. If you
+            have not saved the capture, you will be asked to save it first.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarReload" format="PNG"/></entry>
+        <entry><command>Reload</command></entry>
+        <entry>View/Reload</entry>
+        <entry><para>
+            This item allows you to reload the current capture file.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarPrint" format="PNG"/></entry>
+        <entry><command>Print...</command></entry>
+        <entry>File/Print...</entry>
+        <entry><para>
+            This item allows you to print all (or some of) the packets in
+            the capture file. It pops up the Wireshark Print dialog
+            box (which is discussed further in
+            <xref linkend="ChIOPrintSection"/>).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarFind" format="PNG"/></entry>
+        <entry><command>Find Packet...</command></entry>
+        <entry>Edit/Find Packet...</entry>
+        <entry><para>
+            This item brings up a dialog box that allows you
+            to find a packet. There is further information on finding packets
+            in <xref linkend="ChWorkFindPacketSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarGoBack" format="PNG"/></entry>
+        <entry><command>Go Back</command></entry>
+        <entry>Go/Go Back</entry>
+        <entry><para>
+            This item jumps back in the packet history.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarGoForward" format="PNG"/></entry>
+        <entry><command>Go Forward</command></entry>
+        <entry>Go/Go Forward</entry>
+        <entry><para>
+            This item jumps forward in the packet history.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarGoTo" format="PNG"/></entry>
+        <entry><command>Go to Packet...</command></entry>
+        <entry>Go/Go to Packet...</entry>
+        <entry><para>
+            This item brings up a dialog box that allows you
+            to specify a packet number to go to that packet.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarGoFirst" format="PNG"/></entry>
+        <entry><command>Go To First Packet</command></entry>
+        <entry>Go/First Packet</entry>
+        <entry><para>
+            This item jumps to the first packet of the capture file.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarGoLast" format="PNG"/></entry>
+        <entry><command>Go To Last Packet</command></entry>
+        <entry>Go/Last Packet</entry>
+        <entry><para>
+            This item jumps to the last packet of the capture file.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarColorize" format="PNG"/></entry>
+        <entry><command>Colorize</command></entry>
+        <entry>View/Colorize</entry>
+        <entry><para>
+          Colorize the packet list (or not).
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarAutoScroll" format="PNG"/></entry>
+        <entry><command>Auto Scroll in Live Capture</command></entry>
+        <entry>View/Auto Scroll in Live Capture</entry>
+        <entry><para>
+          Auto scroll packet list while doing a live capture (or not).
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarZoomIn" format="PNG"/></entry>
+        <entry><command>Zoom In</command></entry>
+        <entry>View/Zoom In</entry>
+        <entry><para>
+          Zoom into the packet data (increase the font size).
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarZoomOut" format="PNG"/></entry>
+        <entry><command>Zoom Out</command></entry>
+        <entry>View/Zoom Out</entry>
+        <entry><para>
+          Zoom out of the packet data (decrease the font size).
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarZoom100" format="PNG"/></entry>
+        <entry><command>Normal Size</command></entry>
+        <entry>View/Normal Size</entry>
+        <entry><para>
+          Set zoom level back to 100%.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarResizeColumns" format="PNG"/></entry>
+        <entry><command>Resize Columns</command></entry>
+        <entry>View/Resize Columns</entry>
+        <entry><para>
+          Resize columns, so the content fits into them.
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarCaptureFilters" format="PNG"/></entry>
+        <entry><command>Capture Filters...</command></entry>
+        <entry>Capture/Capture Filters...</entry>
+        <entry><para>
+            This item brings up a dialog box that allows you to
+            create and edit capture filters. You can name filters,
+            and you can save them for future use. More detail on
+            this subject is provided in
+            <xref linkend="ChWorkDefineFilterSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarDisplayFilters" format="PNG"/></entry>
+        <entry><command>Display Filters...</command></entry>
+        <entry>Analyze/Display Filters...</entry>
+        <entry><para>
+            This item brings up a dialog box that allows you
+            to create and edit display filters. You can name
+            filters, and you can save them for future use. More
+            detail on this subject is provided in
+            <xref linkend="ChWorkDefineFilterSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarColoringRules" format="PNG"/></entry>
+        <entry><command>Coloring Rules...</command></entry>
+        <entry>View/Coloring Rules...</entry>
+        <entry><para>
+            This item brings up a dialog box that allows you
+            color packets in the packet list pane according to
+            filter expressions you choose. It can be very useful
+            for spotting certain types of packets. More
+            detail on this subject is provided in
+            <xref linkend="ChCustColorizationSection"/>.
+          </para></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarPreferences" format="PNG"/></entry>
+        <entry><command>Preferences...</command></entry>
+        <entry>Edit/Preferences</entry>
+        <entry><para>
+            This item brings up a dialog box that allows
+            you to set preferences for many parameters that control
+            Wireshark.  You can also save your preferences so Wireshark
+            will use them the next time you start it. More detail
+            is provided in <xref linkend="ChCustPreferencesSection"/>
+          </para></entry>
+          </row>
+          <row>
+        <entry><command>------</command></entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarHelp" format="PNG"/></entry>
+        <entry><command>Help</command></entry>
+        <entry>Help/Contents</entry>
+        <entry><para>
+            This item brings up help dialog box.
+          </para></entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
   </section>
@@ -2430,7 +2430,7 @@
   <section id="ChUseFilterToolbarSection"><title>The "Filter" toolbar</title>
     <para>
       The filter toolbar lets you quickly edit and apply display filters. More information on
-	    display filters is available in <xref linkend="ChWorkDisplayFilterSection"/>.
+        display filters is available in <xref linkend="ChWorkDisplayFilterSection"/>.
     <figure id="ChUseWiresharkFilterToolbar">
       <title>The "Filter" toolbar</title>
       <graphic entityref="WiresharkFilterToolbar" format="PNG"/>
@@ -2438,84 +2438,84 @@
     <table id="ChUseFilterToolbar" frame="none">
       <title>Filter toolbar items</title>
       <tgroup cols="3">
-	<colspec colnum="1" colwidth="40pt"/>
-	  <colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Toolbar Icon</entry>
-		<entry>Toolbar Item</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarDisplayFilters" format="PNG"/></entry>
-		<entry><command>Filter:</command></entry>
-		<entry><para>
-	    Brings up the filter construction dialog, described in <xref linkend="FiltersDialog"/>.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry></entry>
-		<entry>Filter input</entry>
-		<entry>
-	  <para>
-	    The area to enter or edit a display filter string,
-		see <xref linkend="ChWorkBuildDisplayFilterSection"/>
-		. A syntax check of your filter string is done while you are typing.
-		The background will turn red if you enter an incomplete or invalid
-		string, and will become green when you enter a valid string. You can
-		click on the pull down arrow to select a previously-entered filter
-		string from a list. The entries in the pull down list will remain
-		available even after a program restart.
-	  </para>
-	  <note><title>Note!</title>
-	  <para>
-	  	After you've changed something in this field, don't forget to press
-		the Apply button (or the Enter/Return key), to apply this filter
-		string to the display.
-	  </para>
-	  </note>
-	  <note><title>Note!</title>
-	  <para>
-		This field is also where the current filter in effect is displayed.
-	  </para>
-	  </note>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarAdd" format="PNG"/></entry>
-		<entry><command>Expression...</command></entry>
-		<entry><para>
-	    The middle button labeled "Add Expression..." opens a dialog box that lets
-		you edit a display filter from a list of protocol fields, described in
-		 <xref linkend="ChWorkFilterAddExpressionSection"/>
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarClear" format="PNG"/></entry>
-		<entry><command>Clear</command></entry>
-		<entry><para>
-	    Reset the current display filter and clears the edit area.
-		  </para>
-		  </entry>
-	      </row>
-	      <row>
-		<entry><graphic entityref="WiresharkToolbarApply" format="PNG"/></entry>
-		<entry><command>Apply</command></entry>
-		<entry><para>
-	    Apply the current value in the edit area as the new display filter.
-		  <note><title>Note!</title>
-		  <para>
-			Applying a display filter on large capture files might take quite a long time!
-		  </para>
-		  </note>
-		  </para>
-		  </entry>
-	      </row>
-	    </tbody>
+    <colspec colnum="1" colwidth="40pt"/>
+      <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Toolbar Icon</entry>
+        <entry>Toolbar Item</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarDisplayFilters" format="PNG"/></entry>
+        <entry><command>Filter:</command></entry>
+        <entry><para>
+        Brings up the filter construction dialog, described in <xref linkend="FiltersDialog"/>.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry></entry>
+        <entry>Filter input</entry>
+        <entry>
+      <para>
+        The area to enter or edit a display filter string,
+        see <xref linkend="ChWorkBuildDisplayFilterSection"/>
+        . A syntax check of your filter string is done while you are typing.
+        The background will turn red if you enter an incomplete or invalid
+        string, and will become green when you enter a valid string. You can
+        click on the pull down arrow to select a previously-entered filter
+        string from a list. The entries in the pull down list will remain
+        available even after a program restart.
+      </para>
+      <note><title>Note!</title>
+      <para>
+          After you've changed something in this field, don't forget to press
+        the Apply button (or the Enter/Return key), to apply this filter
+        string to the display.
+      </para>
+      </note>
+      <note><title>Note!</title>
+      <para>
+        This field is also where the current filter in effect is displayed.
+      </para>
+      </note>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarAdd" format="PNG"/></entry>
+        <entry><command>Expression...</command></entry>
+        <entry><para>
+        The middle button labeled "Add Expression..." opens a dialog box that lets
+        you edit a display filter from a list of protocol fields, described in
+         <xref linkend="ChWorkFilterAddExpressionSection"/>
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarClear" format="PNG"/></entry>
+        <entry><command>Clear</command></entry>
+        <entry><para>
+        Reset the current display filter and clears the edit area.
+          </para>
+          </entry>
+          </row>
+          <row>
+        <entry><graphic entityref="WiresharkToolbarApply" format="PNG"/></entry>
+        <entry><command>Apply</command></entry>
+        <entry><para>
+        Apply the current value in the edit area as the new display filter.
+          <note><title>Note!</title>
+          <para>
+            Applying a display filter on large capture files might take quite a long time!
+          </para>
+          </note>
+          </para>
+          </entry>
+          </row>
+        </tbody>
       </tgroup>
     </table>
     </para>
@@ -2524,154 +2524,154 @@
   <section id="ChUsePacketListPaneSection"><title>The "Packet List" pane</title>
     <para>
       The packet list pane displays all the packets in the current capture
-	  file.
+      file.
     <figure id="ChUseWiresharkListPane">
       <title>The "Packet List" pane</title>
       <graphic entityref="WiresharkListPane" format="PNG"/>
     </figure>
-	Each line in the packet list corresponds to one packet in the capture
-	file. If you select a line in this pane, more details will be displayed in
-	the "Packet Details" and "Packet Bytes" panes.
+    Each line in the packet list corresponds to one packet in the capture
+    file. If you select a line in this pane, more details will be displayed in
+    the "Packet Details" and "Packet Bytes" panes.
     </para>
     <para>
-	While dissecting a packet, Wireshark will place information from the
-	protocol dissectors into the columns. As higher level protocols might
-	overwrite information from lower levels, you will typically see the
-	information from the highest possible level only.
+    While dissecting a packet, Wireshark will place information from the
+    protocol dissectors into the columns. As higher level protocols might
+    overwrite information from lower levels, you will typically see the
+    information from the highest possible level only.
     </para>
     <para>
-	For example, let's look at a packet containing TCP inside IP inside
-	an Ethernet packet. The Ethernet dissector will write its data (such as
-	the Ethernet addresses), the IP dissector will overwrite this by its own
-	(such as the IP addresses), the TCP dissector will overwrite the IP
-	information, and so on.
+    For example, let's look at a packet containing TCP inside IP inside
+    an Ethernet packet. The Ethernet dissector will write its data (such as
+    the Ethernet addresses), the IP dissector will overwrite this by its own
+    (such as the IP addresses), the TCP dissector will overwrite the IP
+    information, and so on.
     </para>
     <para>
-	There are a lot of different columns available. Which columns are
-	displayed can be selected by preference settings, see
-	<xref linkend="ChCustPreferencesSection"/>.
+    There are a lot of different columns available. Which columns are
+    displayed can be selected by preference settings, see
+    <xref linkend="ChCustPreferencesSection"/>.
     </para>
     <para>
-	The default columns will show:
-	<itemizedlist>
-	<listitem>
-	  <para><command>No.</command>
-	  The number of the packet in the capture file. This number won't change,
-	  even if a display filter is used.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Time</command>
-	  The timestamp of the packet. The presentation format of this timestamp
-	  can be changed, see <xref linkend="ChWorkTimeFormatsSection"/>.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Source</command>
-	  The address where this packet is coming from.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Destination</command>
-	  The address where this packet is going to.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Protocol</command>
-	  The protocol name in a short (perhaps abbreviated) version.
-	  </para>
-	</listitem>
-	<listitem>
-	  <para><command>Info</command>
-	  Additional information about the packet content.
-	  </para>
-	</listitem>
-	</itemizedlist>
+    The default columns will show:
+    <itemizedlist>
+    <listitem>
+      <para><command>No.</command>
+      The number of the packet in the capture file. This number won't change,
+      even if a display filter is used.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Time</command>
+      The timestamp of the packet. The presentation format of this timestamp
+      can be changed, see <xref linkend="ChWorkTimeFormatsSection"/>.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Source</command>
+      The address where this packet is coming from.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Destination</command>
+      The address where this packet is going to.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Protocol</command>
+      The protocol name in a short (perhaps abbreviated) version.
+      </para>
+    </listitem>
+    <listitem>
+      <para><command>Info</command>
+      Additional information about the packet content.
+      </para>
+    </listitem>
+    </itemizedlist>
     </para>
     <para>
-	There is a context menu (right mouse click) available, see details in
-	<xref linkend="ChWorkPacketListPanePopUpMenu"/>.
+    There is a context menu (right mouse click) available, see details in
+    <xref linkend="ChWorkPacketListPanePopUpMenu"/>.
     </para>
   </section>
 
   <section id="ChUsePacketDetailsPaneSection"><title>The "Packet Details" pane</title>
     <para>
       The packet details pane shows the current packet (selected in the "Packet List"
-	  pane) in a more detailed form.
+      pane) in a more detailed form.
     <figure id="ChUseWiresharkDetailsPane">
       <title>The "Packet Details" pane</title>
       <graphic entityref="WiresharkDetailsPane" format="PNG"/>
     </figure>
     </para>
     <para>
-	This pane shows the protocols and protocol fields of the packet selected
-	in the "Packet List" pane. The protocols and fields of the packet are
-	displayed using a tree, which can be expanded and collapsed.
+    This pane shows the protocols and protocol fields of the packet selected
+    in the "Packet List" pane. The protocols and fields of the packet are
+    displayed using a tree, which can be expanded and collapsed.
     </para>
     <para>
-	There is a context menu (right mouse click) available, see details in
-	<xref linkend="ChWorkPacketDetailsPanePopUpMenu"/>.
+    There is a context menu (right mouse click) available, see details in
+    <xref linkend="ChWorkPacketDetailsPanePopUpMenu"/>.
     </para>
     <para>
-	Some protocol fields are specially displayed.
+    Some protocol fields are specially displayed.
     </para>
-	<itemizedlist>
-	<listitem>
+    <itemizedlist>
+    <listitem>
     <para>
-	<command>Generated fields</command>
-	Wireshark itself will generate additional protocol fields which are
-	surrounded by brackets. The information in these fields is derived from the
-	known context to other packets in the capture file. For example, Wireshark
-	is doing a sequence/acknowledge analysis of each TCP stream,
-	which is displayed in the [SEQ/ACK analysis] fields of the TCP protocol.
+    <command>Generated fields</command>
+    Wireshark itself will generate additional protocol fields which are
+    surrounded by brackets. The information in these fields is derived from the
+    known context to other packets in the capture file. For example, Wireshark
+    is doing a sequence/acknowledge analysis of each TCP stream,
+    which is displayed in the [SEQ/ACK analysis] fields of the TCP protocol.
     </para>
-	</listitem>
-	<listitem>
+    </listitem>
+    <listitem>
     <para>
-	<command>Links</command>
-	If Wireshark detected a relationship to another packet in the capture file,
-	it will generate a link to that packet. Links are underlined and displayed
-	in blue. If double-clicked, Wireshark jumps to the corresponding packet.
+    <command>Links</command>
+    If Wireshark detected a relationship to another packet in the capture file,
+    it will generate a link to that packet. Links are underlined and displayed
+    in blue. If double-clicked, Wireshark jumps to the corresponding packet.
     </para>
-	</listitem>
-	</itemizedlist>
+    </listitem>
+    </itemizedlist>
   </section>
 
   <section id="ChUsePacketBytesPaneSection"><title>The "Packet Bytes" pane</title>
     <para>
       The packet bytes pane shows the data of the current packet (selected in the "Packet List"
-	  pane) in a hexdump style.
+      pane) in a hexdump style.
     <figure id="ChUseWiresharkBytesPane">
       <title>The "Packet Bytes" pane</title>
       <graphic entityref="WiresharkBytesPane" format="PNG"/>
     </figure>
     </para>
     <para>
-	As usual for a hexdump, the left side shows the offset in the packet data,
-	in the middle the packet data is shown in a hexadecimal representation and
-	on the right the corresponding ASCII characters (or . if not appropriate)
-	are displayed.
+    As usual for a hexdump, the left side shows the offset in the packet data,
+    in the middle the packet data is shown in a hexadecimal representation and
+    on the right the corresponding ASCII characters (or . if not appropriate)
+    are displayed.
     </para>
     <para>
-	Depending on the packet data, sometimes more than one page is available,
-	e.g. when Wireshark has reassembled some packets into a single chunk of
-	data, see <xref linkend="ChAdvReassemblySection"/>. In this case there are
-	some additional tabs shown at the bottom of the pane to let you select
-	the page you want to see.
+    Depending on the packet data, sometimes more than one page is available,
+    e.g. when Wireshark has reassembled some packets into a single chunk of
+    data, see <xref linkend="ChAdvReassemblySection"/>. In this case there are
+    some additional tabs shown at the bottom of the pane to let you select
+    the page you want to see.
     <figure id="ChUseWiresharkBytesPaneTabs">
       <title>The "Packet Bytes" pane with tabs</title>
       <graphic entityref="WiresharkBytesPaneTabs" format="PNG"/>
     </figure>
     </para>
-	<note><title>Note!</title>
-	<para>
-	The additional pages might contain data picked from multiple packets.
-	</para>
-	</note>
+    <note><title>Note!</title>
     <para>
-	The context menu (right mouse click) of the tab labels will show a list of
-	all available pages. This can be helpful if the size in the pane is too
-	small for all the tab labels.
+    The additional pages might contain data picked from multiple packets.
+    </para>
+    </note>
+    <para>
+    The context menu (right mouse click) of the tab labels will show a list of
+    all available pages. This can be helpful if the size in the pane is too
+    small for all the tab labels.
     </para>
   </section>
 
@@ -2687,80 +2687,80 @@
     </para>
     <para>
       <figure id="ChUseWiresharkStatusbarEmpty">
-	<title>The initial Statusbar</title>
-	<graphic entityref="WiresharkStatusbarEmpty" format="PNG"/>
+    <title>The initial Statusbar</title>
+    <graphic entityref="WiresharkStatusbarEmpty" format="PNG"/>
       </figure>
       This statusbar is shown while no capture file is loaded, e.g. when
       Wireshark is started.
     </para>
     <para>
       <figure id="ChUseWiresharkStatusbarLoaded">
-	<title>The Statusbar with a loaded capture file</title>
-	<graphic entityref="WiresharkStatusbarLoaded" format="PNG"/>
+    <title>The Statusbar with a loaded capture file</title>
+    <graphic entityref="WiresharkStatusbarLoaded" format="PNG"/>
       </figure>
     </para>
     <itemizedlist>
       <listitem>
-	<para>
-	  <command>The colorized bullet</command> on the left shows the highest expert
-	  info level found in the currently loaded capture file.  Hovering the mouse
-	  over this icon will show a textual description of the expert info level, 
-	  and clicking the icon will bring up the Expert Infos dialog box. 
-	  For a detailed description of expert info, see <xref linkend="ChAdvExpert"/>.
-	</para>
+    <para>
+      <command>The colorized bullet</command> on the left shows the highest expert
+      info level found in the currently loaded capture file.  Hovering the mouse
+      over this icon will show a textual description of the expert info level, 
+      and clicking the icon will bring up the Expert Infos dialog box. 
+      For a detailed description of expert info, see <xref linkend="ChAdvExpert"/>.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>The left side</command> shows information about the capture file, its
-	  name, its size and the elapsed time while it was being captured.
-	</para>
+    <para>
+      <command>The left side</command> shows information about the capture file, its
+      name, its size and the elapsed time while it was being captured.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>The middle part</command> shows the current number of packets in the capture file. 
-	  The following values are displayed:
-	  <itemizedlist mark="bullet">
-	    <listitem>
-	      <para><emphasis>Packets:</emphasis> the number of captured packets</para>
-	    </listitem>
-	    <listitem>
-	      <para><emphasis>Displayed:</emphasis> the number of packets currently being
-	      displayed</para>
-	    </listitem>
-	    <listitem>
-	      <para><emphasis>Marked:</emphasis> the number of marked packets</para>
-	    </listitem>
-	    <listitem>
-	      <para><emphasis>Dropped:</emphasis> the number of dropped packets (only displayed
-	      if Wireshark was unable to capture all packets)</para>
-	    </listitem>
-	    <listitem>
-	      <para><emphasis>Ignored:</emphasis> the number of ignored packets (only displayed
-	      if packets are ignored)</para>
-	    </listitem>
-	  </itemizedlist>
-	</para>
+    <para>
+      <command>The middle part</command> shows the current number of packets in the capture file. 
+      The following values are displayed:
+      <itemizedlist mark="bullet">
+        <listitem>
+          <para><emphasis>Packets:</emphasis> the number of captured packets</para>
+        </listitem>
+        <listitem>
+          <para><emphasis>Displayed:</emphasis> the number of packets currently being
+          displayed</para>
+        </listitem>
+        <listitem>
+          <para><emphasis>Marked:</emphasis> the number of marked packets</para>
+        </listitem>
+        <listitem>
+          <para><emphasis>Dropped:</emphasis> the number of dropped packets (only displayed
+          if Wireshark was unable to capture all packets)</para>
+        </listitem>
+        <listitem>
+          <para><emphasis>Ignored:</emphasis> the number of ignored packets (only displayed
+          if packets are ignored)</para>
+        </listitem>
+      </itemizedlist>
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  <command>The right side</command> shows the selected configuration profile.  
-	  Clicking in this part of the statusbar will bring up a menu with all available
-	  configuration profiles, and selecting from this list will change the configuration profile.
-	</para>
+    <para>
+      <command>The right side</command> shows the selected configuration profile.  
+      Clicking in this part of the statusbar will bring up a menu with all available
+      configuration profiles, and selecting from this list will change the configuration profile.
+    </para>
       </listitem>
     </itemizedlist>
     <para>
       <figure id="ChUseWiresharkStatusbarProfile">
-	<title>The Statusbar with a configuration profile menu</title>
-	<graphic entityref="WiresharkStatusbarProfile" format="PNG"/>
+    <title>The Statusbar with a configuration profile menu</title>
+    <graphic entityref="WiresharkStatusbarProfile" format="PNG"/>
       </figure>
       For a detailed description of configuration profiles, see 
       <xref linkend="ChCustConfigProfilesSection"/>.
     </para>
     <para>
       <figure id="ChUseWiresharkStatusbarSelected">
-	<title>The Statusbar with a selected protocol field</title>
-	<graphic entityref="WiresharkStatusbarSelected" format="PNG"/>
+    <title>The Statusbar with a selected protocol field</title>
+    <graphic entityref="WiresharkStatusbarSelected" format="PNG"/>
       </figure>
       This is displayed if you have selected a protocol field from the
       "Packet Details" pane.
@@ -2774,8 +2774,8 @@
     </tip>
     <para>
       <figure id="ChUseWiresharkStatusbarFilter">
-	<title>The Statusbar with a display filter message</title>
-	<graphic entityref="WiresharkStatusbarFilter" format="PNG"/>
+    <title>The Statusbar with a display filter message</title>
+    <graphic entityref="WiresharkStatusbarFilter" format="PNG"/>
       </figure>
       This is displayed if you are trying to use a display filter which
       may have unexpected results.  For a detailed description, see
diff --git a/docbook/wsug_src/WSUG_chapter_work.xml b/docbook/wsug_src/WSUG_chapter_work.xml
index 22c431c002..c09d0281f7 100644
--- a/docbook/wsug_src/WSUG_chapter_work.xml
+++ b/docbook/wsug_src/WSUG_chapter_work.xml
@@ -16,32 +16,32 @@
     <para>
       You can then expand any part of the tree view by clicking on the 
       <command>plus</command> sign (the symbol itself may vary) to the left of 
-	  that part of the payload, 
+      that part of the payload, 
       and you can select individual fields by clicking on them in the tree 
       view pane. An example with a TCP packet selected is shown in 
       <xref linkend="ChWorkSelPack1"/>. It also has the Acknowledgment number 
-	in the TCP header selected, which shows up in the byte view as the 
-	selected bytes.
-	<figure id="ChWorkSelPack1">
-	  <title>Wireshark with a TCP packet selected for viewing</title>
-	  <graphic entityref="WiresharkPacketSelected1" format="PNG"/>
-	</figure>
+    in the TCP header selected, which shows up in the byte view as the 
+    selected bytes.
+    <figure id="ChWorkSelPack1">
+      <title>Wireshark with a TCP packet selected for viewing</title>
+      <graphic entityref="WiresharkPacketSelected1" format="PNG"/>
+    </figure>
     </para>
     <para>
       You can also select and view packets the same way, while Wireshark is 
-	  capturing, if you selected "Update list of packets in real time" in the 
-	  Wireshark Capture Preferences dialog box.
+      capturing, if you selected "Update list of packets in real time" in the 
+      Wireshark Capture Preferences dialog box.
     </para>
     <para>
       In addition, you can view individual packets in a separate window as 
       shown in <xref linkend="ChWorkPacketSepView"/>. Do this by selecting the 
-	packet in which you are interested in the packet list pane, and then 
-	select "Show Packet in New Windows" from the Display menu. This 
-	allows you to easily compare two or even more packets.
-	<figure id="ChWorkPacketSepView">
-	  <title>Viewing a packet in a separate window</title>
-	  <graphic entityref="WiresharkPacketSepView" format="PNG"/>
-	</figure>
+    packet in which you are interested in the packet list pane, and then 
+    select "Show Packet in New Windows" from the Display menu. This 
+    allows you to easily compare two or even more packets.
+    <figure id="ChWorkPacketSepView">
+      <title>Viewing a packet in a separate window</title>
+      <graphic entityref="WiresharkPacketSepView" format="PNG"/>
+    </figure>
     </para>
   </section>
   
@@ -51,754 +51,754 @@
       column header, or
       "Packet Details" pane by clicking your right mouse button at the
       corresponding pane.
-    </para>	
+    </para>    
 
   <section id="ChWorkColumnHeaderPopUpMenuSection">
     <title>Pop-up menu of the "Packet List" column header</title>
     <para>
       <figure id="ChWorkColumnHeaderPopUpMenu">
-	<title>Pop-up menu of the "Packet List" column header</title>
-	<graphic entityref="WiresharkColumnHeaderPopupMenu" format="PNG"/>
+    <title>Pop-up menu of the "Packet List" column header</title>
+    <graphic entityref="WiresharkColumnHeaderPopupMenu" format="PNG"/>
       </figure>
-	</para>
-	  <para>
-	  The following table gives an overview of which functions are available
-	  in this header, where to find the corresponding function in the main menu,
-	  and a short description of each item.
-	  </para>
-	<table id="ColumnHeaderPopupMenuTable">
-	  <title>The menu items of the "Packet List" column header pop-up menu</title>
-	  <tgroup cols="3">
-		<colspec colnum="1" colwidth="80pt"/>
-		<colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Item</entry>
-		<entry>Identical to main menu's item:</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Sort Ascending</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Sort the packet list in ascending order based on this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Sort Descending</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Sort the packet list in descending order based on this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>No Sort</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Remove sorting order based on this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Align Left</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-		  Set left alignment of the values in this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Align Center</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-		  Set center alignment of the values in this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Align Right</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-		  Set right alignment of the values in this column.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Column Preferences...</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-		  Open the Preferences dialog box on the column tab.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Resize Column</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Resize the column to fit the values.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Rename Column Title</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Allows you to change the title of the column header.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Displayed Column</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-	      This menu items folds out with a list of all configured columns.
-	      These columns can now be shown or hidden in the packet list.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Hide Column</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Allows you to hide the column from the packet list.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Remove Column</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Allows you to remove the column from the packet list.
-	    </para>
-		</entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-	</table>
+    </para>
+      <para>
+      The following table gives an overview of which functions are available
+      in this header, where to find the corresponding function in the main menu,
+      and a short description of each item.
+      </para>
+    <table id="ColumnHeaderPopupMenuTable">
+      <title>The menu items of the "Packet List" column header pop-up menu</title>
+      <tgroup cols="3">
+        <colspec colnum="1" colwidth="80pt"/>
+        <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Item</entry>
+        <entry>Identical to main menu's item:</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Sort Ascending</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Sort the packet list in ascending order based on this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Sort Descending</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Sort the packet list in descending order based on this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>No Sort</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Remove sorting order based on this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Align Left</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Set left alignment of the values in this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Align Center</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Set center alignment of the values in this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Align Right</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Set right alignment of the values in this column.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Column Preferences...</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Open the Preferences dialog box on the column tab.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Resize Column</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Resize the column to fit the values.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Rename Column Title</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Allows you to change the title of the column header.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Displayed Column</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          This menu items folds out with a list of all configured columns.
+          These columns can now be shown or hidden in the packet list.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Hide Column</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Allows you to hide the column from the packet list.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Remove Column</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Allows you to remove the column from the packet list.
+        </para>
+        </entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
   </section>
   
   <section id="ChWorkPacketListPanePopUpMenuSection">
     <title>Pop-up menu of the "Packet List" pane</title>
     <para>
       <figure id="ChWorkPacketListPanePopUpMenu">
-	<title>Pop-up menu of the "Packet List" pane</title>
-	<graphic entityref="WiresharkPacketPanePopupMenu" format="PNG"/>
+    <title>Pop-up menu of the "Packet List" pane</title>
+    <graphic entityref="WiresharkPacketPanePopupMenu" format="PNG"/>
       </figure>
-	</para>
-	  <para>
-	  The following table gives an overview of which functions are available 
-	  in this pane, where to find the corresponding function in the main menu, 
-	  and a short description of each item.
-	  </para>
-	<table id="PacketListPopupMenuTable">
-	  <title>The menu items of the "Packet List" pop-up menu</title>
-	  <tgroup cols="3">
-		<colspec colnum="1" colwidth="80pt"/>
-		<colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Item</entry>
-		<entry>Identical to main menu's item:</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Mark Packet (toggle)</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Mark/unmark a packet.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Ignore Packet (toggle)</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Ignore or inspect this packet while dissecting the capture file.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Set Time Reference (toggle)</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Set/reset a time reference.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Manually Resolve Address</command></entry>
-		<entry></entry>
-		<entry>
-	    <para>
-	      Allows you to enter a name to resolve for the selected address.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Apply as Filter</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Prepare and apply a display filter based on the currently selected 
-		  item.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Prepare a Filter</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Prepare a display filter based on the currently selected item.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Conversation Filter</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      This menu item applies a display filter with the address information 
-		  from the selected packet. E.g. the IP menu entry will set a filter 
-		  to show the traffic between the two IP addresses of the current 
-		  packet.
-		  XXX - add a new section describing this better.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize Conversation</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      This menu item uses a display filter with the address information 
-		  from the selected packet to build a new colorizing rule.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>SCTP</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      Allows you to analyze and prepare a filter for this SCTP association.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow TCP Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Allows you to view all the data on a TCP 
-	      stream between a pair of nodes.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow UDP Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Allows you to view all the data on a UDP datagram
-	      stream between a pair of nodes.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow SSL Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-	      Same as "Follow TCP Stream" but for SSL.
-		  XXX - add a new section describing this better.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-		  <row>
-		<entry><command>Copy/ Summary (Text)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the summary fields as displayed to the clipboard, as tab-separated text.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Summary (CSV)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the summary fields as displayed to the clipboard, as comma-separated text.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ As Filter</command></entry>
-		<entry></entry>
-		<entry>
-		<para>
-		  Prepare a display filter based on the currently selected item
-		  and copy that filter to the clipboard.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Offset Hex Text)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard in hexdump-like format.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Offset Hex)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard in hexdump-like format, but without the text portion.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Printable Text Only)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as ASCII text, excluding non-printable characters.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Hex Stream)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as an unpunctuated list of hex digits.
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Binary Stream)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as raw binary. The data is stored in the
-		  clipboard as MIME-type "application/octet-stream".</para>
-		</entry>
-		  </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Decode As...</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Change or apply a new relation between two dissectors. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Print...</command></entry>
-		<entry>File</entry>
-		<entry>
-	    <para>
-		  Print packets.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Show Packet in New Window</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-		  Display the selected packet in a new window.
-	    </para>
-		</entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-	</table>
+    </para>
+      <para>
+      The following table gives an overview of which functions are available 
+      in this pane, where to find the corresponding function in the main menu, 
+      and a short description of each item.
+      </para>
+    <table id="PacketListPopupMenuTable">
+      <title>The menu items of the "Packet List" pop-up menu</title>
+      <tgroup cols="3">
+        <colspec colnum="1" colwidth="80pt"/>
+        <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Item</entry>
+        <entry>Identical to main menu's item:</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Mark Packet (toggle)</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Mark/unmark a packet.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Ignore Packet (toggle)</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Ignore or inspect this packet while dissecting the capture file.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Set Time Reference (toggle)</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Set/reset a time reference.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Manually Resolve Address</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Allows you to enter a name to resolve for the selected address.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Apply as Filter</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Prepare and apply a display filter based on the currently selected 
+          item.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Prepare a Filter</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Prepare a display filter based on the currently selected item.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Conversation Filter</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          This menu item applies a display filter with the address information 
+          from the selected packet. E.g. the IP menu entry will set a filter 
+          to show the traffic between the two IP addresses of the current 
+          packet.
+          XXX - add a new section describing this better.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Colorize Conversation</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          This menu item uses a display filter with the address information 
+          from the selected packet to build a new colorizing rule.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>SCTP</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Allows you to analyze and prepare a filter for this SCTP association.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow TCP Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Allows you to view all the data on a TCP 
+          stream between a pair of nodes.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow UDP Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Allows you to view all the data on a UDP datagram
+          stream between a pair of nodes.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow SSL Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Same as "Follow TCP Stream" but for SSL.
+          XXX - add a new section describing this better.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Summary (Text)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the summary fields as displayed to the clipboard, as tab-separated text.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Summary (CSV)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the summary fields as displayed to the clipboard, as comma-separated text.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ As Filter</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Prepare a display filter based on the currently selected item
+          and copy that filter to the clipboard.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Offset Hex Text)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard in hexdump-like format.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Offset Hex)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard in hexdump-like format, but without the text portion.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Printable Text Only)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as ASCII text, excluding non-printable characters.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Hex Stream)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as an unpunctuated list of hex digits.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Binary Stream)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as raw binary. The data is stored in the
+          clipboard as MIME-type "application/octet-stream".</para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Decode As...</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Change or apply a new relation between two dissectors. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Print...</command></entry>
+        <entry>File</entry>
+        <entry>
+        <para>
+          Print packets.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Show Packet in New Window</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          Display the selected packet in a new window.
+        </para>
+        </entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
   </section>
   
   <section id="ChWorkPacketDetailsPanePopUpMenuSection">
     <title>Pop-up menu of the "Packet Details" pane</title>
     <para>
       <figure id="ChWorkPacketDetailsPanePopUpMenu">
-	<title>Pop-up menu of the "Packet Details" pane</title>
-	<graphic entityref="WiresharkDetailsPanePopupMenu" format="PNG"/>
+    <title>Pop-up menu of the "Packet Details" pane</title>
+    <graphic entityref="WiresharkDetailsPanePopupMenu" format="PNG"/>
       </figure>
-	  </para>
-	  <para>
-	  The following table gives an overview of which functions are available 
-	  in this pane, where to find the corresponding function in the main menu, 
-	  and a short description of each item.
-	  </para>
-	<table id="PacketDetailsPopupMenuTable">
-	  <title>The menu items of the "Packet Details" pop-up menu</title>
-	  <tgroup cols="3">
-		<colspec colnum="1" colwidth="80pt"/>
-		<colspec colnum="2" colwidth="80pt"/>
-	    <thead>
-	      <row>
-		<entry>Item</entry>
-		<entry>Identical to main menu's item:</entry>
-		<entry>Description</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry><command>Expand Subtrees</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-	      Expand the currently selected subtree. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Expand All</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-	      Expand all subtrees in all packets in the capture. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Collapse All</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-	      Wireshark keeps a list of all the protocol subtrees that are 
-	      expanded, and uses it to ensure that the correct subtrees 
-	      are expanded when you display a packet. This menu item 
-	      collapses the tree view of all packets in the capture list.  
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Apply as Column</command></entry>
-		<entry></entry>
-		<entry>
-		<para>
-		  Use the selected protocol item to create a new column in the packet list.
-		</para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Apply as Filter</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Prepare and apply a display filter based on the currently selected
-		  item.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Prepare a Filter</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Prepare a display filter based on the currently selected item.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Colorize with Filter</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      This menu item uses a display filter with the information
-		  from the selected protocol item to build a new colorizing rule.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow TCP Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Allows you to view all the data on a TCP
-	      stream between a pair of nodes.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow UDP Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Allows you to view all the data on a UDP datagram
-	      stream between a pair of nodes.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Follow SSL Stream</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-	      Same as "Follow TCP Stream" but for SSL.
-		  XXX - add a new section describing this better.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Copy/ Description</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Copy the displayed text of the selected field to the system 
-		  clipboard. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Copy/ Fieldname</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Copy the name of the selected field to the system clipboard. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Copy/ Value</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-	      Copy the value of the selected field to the system clipboard. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Copy/ As Filter</command></entry>
-		<entry>Edit</entry>
-		<entry>
-	    <para>
-		  Prepare a display filter based on the currently selected item
-		  and copy it to the clipboard.
-	    </para>
-		</entry>
-	      </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Offset Hex Text)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard in hexdump-like format; similar to the Packet List Pane 
-		  command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
-		  in the Packet Bytes Pane).
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Offset Hex)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard in hexdump-like format, but without the text portion; similar to the 		Packet List Pane 
-		  command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
-		  in the Packet Bytes Pane).
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Printable Text Only)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as ASCII text, excluding non-printable characters; similar to the Packet List Pane 
-		  command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
-		  in the Packet Bytes Pane).
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Hex Stream)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as an unpunctuated list of hex digits; similar to the Packet List Pane 
-		  command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
-		  in the Packet Bytes Pane).
-		</para>
-		</entry>
-		  </row>
-		  <row>
-		<entry><command>Copy/ Bytes (Binary Stream)</command></entry>
-		<entry>-</entry>
-		<entry>
-		<para>
-		  Copy the packet bytes to the clipboard as raw binary; similar to the Packet List Pane 
-		  command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
-		  in the Packet Bytes Pane). The data is stored in the
-		  clipboard as MIME-type "application/octet-stream".</para>
-		</entry>
-		  </row>
-	      <row>
-		<entry><command>Export Selected Packet Bytes...</command></entry>
-		<entry>File</entry>
-		<entry>
-	    <para>
-	      This menu item is the same as the File menu item of the same 
-	      name. It allows you to export raw packet bytes to a binary file.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Wiki Protocol Page</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      Show the wiki page corresponding to the currently selected protocol 
-		  in your web browser.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Filter Field Reference</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-		  Show the filter field reference web page corresponding to the 
-		  currently selected protocol in your web browser.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Protocol Preferences...</command></entry>
-		<entry>-</entry>
-		<entry>
-	    <para>
-	      The menu item takes you to the properties dialog and selects the 
-		  page corresponding to the protocol if there are properties 
-		  associated with the highlighted field.  
-	      More information on preferences can be found in 
-	      <xref linkend="ChCustGUIPrefPage"/>.
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry>-----</entry>
-		<entry></entry>
-		<entry></entry>
-	      </row>
-	      <row>
-		<entry><command>Decode As...</command></entry>
-		<entry>Analyze</entry>
-		<entry>
-	    <para>
-		  Change or apply a new relation between two dissectors. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Disable Protocol</command></entry>
-		<entry></entry>
-		<entry>
-		<para>
-		  Allows you to temporarily disable a protocol dissector, which may
-		  be blocking the legitimate dissector.
-		</para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Resolve Name</command></entry>
-		<entry>View</entry>
-		<entry>
-	    <para>
-	      Causes a name resolution to be performed for 
-	      the selected packet, but NOT every packet in the capture. 
-	    </para>
-		</entry>
-	      </row>
-	      <row>
-		<entry><command>Go to Corresponding Packet</command></entry>
-		<entry>Go</entry>
-		<entry>
-	    <para>
-	      If the selected field has a corresponding packet, go to it. 
-		  Corresponding packets will usually be a request/response packet pair 
-		  or such.
-	    </para>
-		</entry>
-	      </row>
-		</tbody>
-	  </tgroup>
-	</table>
+      </para>
+      <para>
+      The following table gives an overview of which functions are available 
+      in this pane, where to find the corresponding function in the main menu, 
+      and a short description of each item.
+      </para>
+    <table id="PacketDetailsPopupMenuTable">
+      <title>The menu items of the "Packet Details" pop-up menu</title>
+      <tgroup cols="3">
+        <colspec colnum="1" colwidth="80pt"/>
+        <colspec colnum="2" colwidth="80pt"/>
+        <thead>
+          <row>
+        <entry>Item</entry>
+        <entry>Identical to main menu's item:</entry>
+        <entry>Description</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry><command>Expand Subtrees</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          Expand the currently selected subtree. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Expand All</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          Expand all subtrees in all packets in the capture. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Collapse All</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          Wireshark keeps a list of all the protocol subtrees that are 
+          expanded, and uses it to ensure that the correct subtrees 
+          are expanded when you display a packet. This menu item 
+          collapses the tree view of all packets in the capture list.  
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Apply as Column</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Use the selected protocol item to create a new column in the packet list.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Apply as Filter</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Prepare and apply a display filter based on the currently selected
+          item.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Prepare a Filter</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Prepare a display filter based on the currently selected item.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Colorize with Filter</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          This menu item uses a display filter with the information
+          from the selected protocol item to build a new colorizing rule.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow TCP Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Allows you to view all the data on a TCP
+          stream between a pair of nodes.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow UDP Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Allows you to view all the data on a UDP datagram
+          stream between a pair of nodes.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Follow SSL Stream</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Same as "Follow TCP Stream" but for SSL.
+          XXX - add a new section describing this better.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Description</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Copy the displayed text of the selected field to the system 
+          clipboard. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Fieldname</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Copy the name of the selected field to the system clipboard. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Value</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Copy the value of the selected field to the system clipboard. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ As Filter</command></entry>
+        <entry>Edit</entry>
+        <entry>
+        <para>
+          Prepare a display filter based on the currently selected item
+          and copy it to the clipboard.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Offset Hex Text)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard in hexdump-like format; similar to the Packet List Pane 
+          command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
+          in the Packet Bytes Pane).
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Offset Hex)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard in hexdump-like format, but without the text portion; similar to the         Packet List Pane 
+          command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
+          in the Packet Bytes Pane).
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Printable Text Only)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as ASCII text, excluding non-printable characters; similar to the Packet List Pane 
+          command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
+          in the Packet Bytes Pane).
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Hex Stream)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as an unpunctuated list of hex digits; similar to the Packet List Pane 
+          command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
+          in the Packet Bytes Pane).
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Copy/ Bytes (Binary Stream)</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Copy the packet bytes to the clipboard as raw binary; similar to the Packet List Pane 
+          command, but copies only the bytes relevant to the selected part of the tree (the bytes selected
+          in the Packet Bytes Pane). The data is stored in the
+          clipboard as MIME-type "application/octet-stream".</para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Export Selected Packet Bytes...</command></entry>
+        <entry>File</entry>
+        <entry>
+        <para>
+          This menu item is the same as the File menu item of the same 
+          name. It allows you to export raw packet bytes to a binary file.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Wiki Protocol Page</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Show the wiki page corresponding to the currently selected protocol 
+          in your web browser.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Filter Field Reference</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          Show the filter field reference web page corresponding to the 
+          currently selected protocol in your web browser.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Protocol Preferences...</command></entry>
+        <entry>-</entry>
+        <entry>
+        <para>
+          The menu item takes you to the properties dialog and selects the 
+          page corresponding to the protocol if there are properties 
+          associated with the highlighted field.  
+          More information on preferences can be found in 
+          <xref linkend="ChCustGUIPrefPage"/>.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry>-----</entry>
+        <entry></entry>
+        <entry></entry>
+          </row>
+          <row>
+        <entry><command>Decode As...</command></entry>
+        <entry>Analyze</entry>
+        <entry>
+        <para>
+          Change or apply a new relation between two dissectors. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Disable Protocol</command></entry>
+        <entry></entry>
+        <entry>
+        <para>
+          Allows you to temporarily disable a protocol dissector, which may
+          be blocking the legitimate dissector.
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Resolve Name</command></entry>
+        <entry>View</entry>
+        <entry>
+        <para>
+          Causes a name resolution to be performed for 
+          the selected packet, but NOT every packet in the capture. 
+        </para>
+        </entry>
+          </row>
+          <row>
+        <entry><command>Go to Corresponding Packet</command></entry>
+        <entry>Go</entry>
+        <entry>
+        <para>
+          If the selected field has a corresponding packet, go to it. 
+          Corresponding packets will usually be a request/response packet pair 
+          or such.
+        </para>
+        </entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
   </section>
   
   </section>
@@ -810,48 +810,48 @@
       packets, and one used when displaying packets.  In this section we 
       explore that second type of filter: Display filters.  The first one 
       has already been dealt with in 
-	  <xref linkend="ChCapCaptureFilterSection"/>.
+      <xref linkend="ChCapCaptureFilterSection"/>.
     </para>
     <para>
       Display filters allow you to concentrate on the packets you are 
       interested in while hiding the currently uninteresting ones. They allow 
-	  you to select packets by:
-	<itemizedlist>
-	  <listitem><para>Protocol</para></listitem>
-	  <listitem><para>The presence of a field</para></listitem>
-	  <listitem><para>The values of fields</para></listitem>
-	  <listitem><para>A comparison between fields</para></listitem>
-	  <listitem><para>... and a lot more!</para></listitem>
+      you to select packets by:
+    <itemizedlist>
+      <listitem><para>Protocol</para></listitem>
+      <listitem><para>The presence of a field</para></listitem>
+      <listitem><para>The values of fields</para></listitem>
+      <listitem><para>A comparison between fields</para></listitem>
+      <listitem><para>... and a lot more!</para></listitem>
       </itemizedlist>
     </para>
     <para>
       To select packets based on protocol type, simply type the protocol in which you 
       are interested in the <command>Filter:</command> field in the filter 
-	  toolbar of the Wireshark window and press enter to initiate 
+      toolbar of the Wireshark window and press enter to initiate 
       the filter. <xref linkend="ChWorkTCPFilter"/> shows an example of what 
-	happens when you type <command>tcp</command> in the filter field.
+    happens when you type <command>tcp</command> in the filter field.
     </para>
     <note>
       <title>Note!</title>
       <para>
-	All protocol and field names are entered in lowercase.  Also, don't 
-	forget to press enter after entering the filter expression.
+    All protocol and field names are entered in lowercase.  Also, don't 
+    forget to press enter after entering the filter expression.
       </para>
     </note>
     <figure id="ChWorkTCPFilter"><title>Filtering on the TCP protocol</title>
       <graphic entityref="WiresharkFilterTCP" format="JPG"/>
     </figure>
     <para>
-	As you might have noticed, only packets of the TCP protocol are displayed 
-	now (e.g. packets 1-10 are hidden). The packet numbering will remain as 
-	before, so the first packet shown is now packet number 11.
+    As you might have noticed, only packets of the TCP protocol are displayed 
+    now (e.g. packets 1-10 are hidden). The packet numbering will remain as 
+    before, so the first packet shown is now packet number 11.
     </para>
     <note>
       <title>Note!</title>
       <para>
-	  When using a display filter, all packets remain in the capture file.
-	  The display filter only changes the display of the capture file but
-	  not its content!	  
+      When using a display filter, all packets remain in the capture file.
+      The display filter only changes the display of the capture file but
+      not its content!      
       </para>
     </note>
     <para>
@@ -871,187 +871,187 @@
     <note>
       <title>Note!</title>
       <para>
-	To remove the filter, click on the <command>Clear</command> button 
-	to the right of the filter field.
+    To remove the filter, click on the <command>Clear</command> button 
+    to the right of the filter field.
       </para>
     </note>
     </section>
-	
+    
     <section id="ChWorkBuildDisplayFilterSection">
       <title>Building display filter expressions</title>
       <para>
-	Wireshark provides a simple but powerful display filter language that allows you 
-	to build quite complex filter expressions.  You can compare 
-	values in packets as well as combine expressions into more 
-	specific expressions.  The following sections provide more 
-	information on doing this.
+    Wireshark provides a simple but powerful display filter language that allows you 
+    to build quite complex filter expressions.  You can compare 
+    values in packets as well as combine expressions into more 
+    specific expressions.  The following sections provide more 
+    information on doing this.
       </para>
     <tip>
       <title>Tip!</title>
       <para>
-	  You will find a lot of Display Filter examples at the <command>Wireshark 
-	  Wiki Display Filter page</command> at <ulink 
-	  url="&WiresharkWikiDisplayFiltersPage;">&WiresharkWikiDisplayFiltersPage;</ulink>.
+      You will find a lot of Display Filter examples at the <command>Wireshark 
+      Wiki Display Filter page</command> at <ulink 
+      url="&WiresharkWikiDisplayFiltersPage;">&WiresharkWikiDisplayFiltersPage;</ulink>.
       </para>
     </tip>
       <section>
-	<title>Display filter fields</title>
-	<para>
-	Every field in the packet details pane can be used as a filter 
-	string, this will result in showing only the packets where this field 
-	exists. For example: the 
-	filter string: <command>tcp</command> will show all packets containing the 
-	tcp protocol. 
-	</para>
-	<para>
-	There is a complete list of all filter fields available
-	through the menu item "Help/Supported Protocols" in the page "Display Filter 
-	Fields" of the Supported Protocols dialog. 
-	</para>
-	<para>
-	XXX - add some more info here and a link to the statusbar info.
-	</para>
+    <title>Display filter fields</title>
+    <para>
+    Every field in the packet details pane can be used as a filter 
+    string, this will result in showing only the packets where this field 
+    exists. For example: the 
+    filter string: <command>tcp</command> will show all packets containing the 
+    tcp protocol. 
+    </para>
+    <para>
+    There is a complete list of all filter fields available
+    through the menu item "Help/Supported Protocols" in the page "Display Filter 
+    Fields" of the Supported Protocols dialog. 
+    </para>
+    <para>
+    XXX - add some more info here and a link to the statusbar info.
+    </para>
       </section>
       <section>
-	<title>Comparing values</title>
-	<para>
-	  You can build display filters that compare values using a number 
-	  of different comparison operators.  They are shown in 
-	  <xref linkend="DispCompOps"/>.
-	</para>
-	<tip><title>Tip!</title>
-	<para>
-	You can use English and C-like terms in the same way, they can even be 
-	mixed in a filter string!
-	</para>
-	</tip>
-	<table id="DispCompOps">
-	  <title>Display Filter comparison operators</title>
-	  <tgroup cols="3">
-		<colspec colnum="1" colwidth="50pt"/>
-		<colspec colnum="2" colwidth="50pt"/>
-	    <thead>
-	      <row>
-		<entry>English</entry>
-		<entry>C-like</entry>
-		<entry>Description and example</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry>eq</entry>
-		<entry><programlisting>==</programlisting></entry>
-		<entry><para>
-		    <command>Equal</command></para><para>
-		    <programlisting>ip.src==10.0.0.5</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>ne</entry>
-		<entry><programlisting>!=</programlisting></entry>
-		<entry><para>
-		    <command>Not equal</command></para><para>
-		    <programlisting>ip.src!=10.0.0.5</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>gt</entry>
-		<entry><programlisting>&gt;</programlisting></entry>
-		<entry><para>
-		    <command>Greater than</command></para><para>
-		    <programlisting>frame.len &gt; 10</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>lt</entry>
-		<entry><programlisting>&lt;</programlisting></entry>
-		<entry><para><command>Less than</command></para><para>
-		    <programlisting>frame.len &lt; 128</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>ge</entry>
-		<entry><programlisting>&gt;=</programlisting></entry>
-		<entry><para>
-		    <command>Greater than or equal to</command></para><para>
-		    <programlisting>frame.len ge 0x100</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>le</entry>
-		<entry><programlisting>&lt;=</programlisting></entry>
-		<entry><para>
-		    <command>Less than or equal to</command></para><para>
-		    <programlisting>frame.len &lt;= 0x20</programlisting>
-		  </para></entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-	</table>
-	<para>
-	  In addition, all protocol fields are typed. 
-	  <xref linkend="ChWorkFieldTypes"/> provides a list of the types and 
-	    example of how to express them.
-	    <table id="ChWorkFieldTypes">
-	      <title>Display Filter Field Types</title>
-	      <tgroup cols="2">
-		<thead>
-		  <row>
-		    <entry>Type</entry>
-		    <entry>Example</entry>
-		  </row>
-		</thead>
-		<tbody>
-		  <row>
-		    <entry>
-		      Unsigned integer (8-bit, 16-bit, 24-bit, 32-bit)
-		    </entry>
-		    <entry><para>
-			You can express integers in decimal, octal, or 
-			hexadecimal. The following display filters are 
-			equivalent:
-			<programlisting>
+    <title>Comparing values</title>
+    <para>
+      You can build display filters that compare values using a number 
+      of different comparison operators.  They are shown in 
+      <xref linkend="DispCompOps"/>.
+    </para>
+    <tip><title>Tip!</title>
+    <para>
+    You can use English and C-like terms in the same way, they can even be 
+    mixed in a filter string!
+    </para>
+    </tip>
+    <table id="DispCompOps">
+      <title>Display Filter comparison operators</title>
+      <tgroup cols="3">
+        <colspec colnum="1" colwidth="50pt"/>
+        <colspec colnum="2" colwidth="50pt"/>
+        <thead>
+          <row>
+        <entry>English</entry>
+        <entry>C-like</entry>
+        <entry>Description and example</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry>eq</entry>
+        <entry><programlisting>==</programlisting></entry>
+        <entry><para>
+            <command>Equal</command></para><para>
+            <programlisting>ip.src==10.0.0.5</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>ne</entry>
+        <entry><programlisting>!=</programlisting></entry>
+        <entry><para>
+            <command>Not equal</command></para><para>
+            <programlisting>ip.src!=10.0.0.5</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>gt</entry>
+        <entry><programlisting>&gt;</programlisting></entry>
+        <entry><para>
+            <command>Greater than</command></para><para>
+            <programlisting>frame.len &gt; 10</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>lt</entry>
+        <entry><programlisting>&lt;</programlisting></entry>
+        <entry><para><command>Less than</command></para><para>
+            <programlisting>frame.len &lt; 128</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>ge</entry>
+        <entry><programlisting>&gt;=</programlisting></entry>
+        <entry><para>
+            <command>Greater than or equal to</command></para><para>
+            <programlisting>frame.len ge 0x100</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>le</entry>
+        <entry><programlisting>&lt;=</programlisting></entry>
+        <entry><para>
+            <command>Less than or equal to</command></para><para>
+            <programlisting>frame.len &lt;= 0x20</programlisting>
+          </para></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+    <para>
+      In addition, all protocol fields are typed. 
+      <xref linkend="ChWorkFieldTypes"/> provides a list of the types and 
+        example of how to express them.
+        <table id="ChWorkFieldTypes">
+          <title>Display Filter Field Types</title>
+          <tgroup cols="2">
+        <thead>
+          <row>
+            <entry>Type</entry>
+            <entry>Example</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+            <entry>
+              Unsigned integer (8-bit, 16-bit, 24-bit, 32-bit)
+            </entry>
+            <entry><para>
+            You can express integers in decimal, octal, or 
+            hexadecimal. The following display filters are 
+            equivalent:
+            <programlisting>
 ip.len le 1500
 ip.len le 02734
 ip.len le 0x436
-			</programlisting>
-		      </para></entry>
-		  </row>
-		  <row>
-		    <entry>
-		      Signed integer (8-bit, 16-bit, 24-bit, 32-bit)
-		    </entry>
-		    <entry></entry>
-		  </row>
-		  <row>
-		    <entry>Boolean</entry>
-		    <entry><para>
-			A boolean field is present in the protocol decode 
-			only if its value is true. For example, 
-			<command>tcp.flags.syn</command> is present, and 
-			thus true, only if the SYN flag is present in a 
-			TCP segment header.</para><para>
-			Thus the filter expression 
-			<command>tcp.flags.syn</command> will select only 
-			those packets for which this flag exists, that is, 
-			TCP segments where the segment header contains the 
-			SYN flag. Similarly, to find source-routed token 
-			ring packets, use a filter expression of 
-			<command>tr.sr</command>.
-		      </para></entry>
-		  </row>
-		  <row>
-		    <entry>Ethernet address (6 bytes)</entry>
-		    <entry><para>Separators can be a colon
-			(:), dot (.) or dash (-) and can have one or
-			two bytes between separators:<programlisting>
+            </programlisting>
+              </para></entry>
+          </row>
+          <row>
+            <entry>
+              Signed integer (8-bit, 16-bit, 24-bit, 32-bit)
+            </entry>
+            <entry></entry>
+          </row>
+          <row>
+            <entry>Boolean</entry>
+            <entry><para>
+            A boolean field is present in the protocol decode 
+            only if its value is true. For example, 
+            <command>tcp.flags.syn</command> is present, and 
+            thus true, only if the SYN flag is present in a 
+            TCP segment header.</para><para>
+            Thus the filter expression 
+            <command>tcp.flags.syn</command> will select only 
+            those packets for which this flag exists, that is, 
+            TCP segments where the segment header contains the 
+            SYN flag. Similarly, to find source-routed token 
+            ring packets, use a filter expression of 
+            <command>tr.sr</command>.
+              </para></entry>
+          </row>
+          <row>
+            <entry>Ethernet address (6 bytes)</entry>
+            <entry><para>Separators can be a colon
+            (:), dot (.) or dash (-) and can have one or
+            two bytes between separators:<programlisting>
 eth.dst == ff:ff:ff:ff:ff:ff
 eth.dst == ff-ff-ff-ff-ff-ff
 eth.dst == ffff.ffff.ffff</programlisting></para></entry>
-		  </row>
-		  <row>
-		    <entry>IPv4 address</entry>
-		    <entry>
+          </row>
+          <row>
+            <entry>IPv4 address</entry>
+            <entry>
                 <para>ip.addr == 192.168.0.1</para>
                 <para>Classless InterDomain Routing (CIDR) notation
                 can be used to test if an IPv4 address is in a
@@ -1059,154 +1059,154 @@ eth.dst == ffff.ffff.ffff</programlisting></para></entry>
                 will find all packets in the 129.111 Class-B
                 network:
                 </para><para>ip.addr == 129.111.0.0/16</para></entry>
-		  </row>
-		  <row>
-		    <entry>IPv6 address</entry>
-		    <entry>ipv6.addr == ::1</entry>
-		  </row>
-		  <row>
-		    <entry>IPX address</entry>
-		    <entry>ipx.addr == 00000000.ffffffffffff</entry>
-		  </row>
-		  <row>
-		    <entry>String (text)</entry>
-		    <entry>http.request.uri == "http://www.wireshark.org/"</entry>
-		  </row>
-		</tbody>
-	      </tgroup>
-	    </table>
-	</para>
+          </row>
+          <row>
+            <entry>IPv6 address</entry>
+            <entry>ipv6.addr == ::1</entry>
+          </row>
+          <row>
+            <entry>IPX address</entry>
+            <entry>ipx.addr == 00000000.ffffffffffff</entry>
+          </row>
+          <row>
+            <entry>String (text)</entry>
+            <entry>http.request.uri == "http://www.wireshark.org/"</entry>
+          </row>
+        </tbody>
+          </tgroup>
+        </table>
+    </para>
       </section>
       <section>
-	<title>Combining expressions</title>
-	<para>
-	  You can combine filter expressions in Wireshark using the 
-	  logical operators shown in <xref linkend="FiltLogOps"/>
-	</para>
-	<table id="FiltLogOps">
-	  <title>Display Filter Logical Operations</title>
-	  <tgroup cols="3">
-		<colspec colnum="1" colwidth="50pt"/>
-		<colspec colnum="2" colwidth="50pt"/>
-	    <thead>
-	      <row>
-		<entry>English</entry>
-		<entry>C-like</entry>
-		<entry>Description and example</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry>and</entry>
-		<entry>&amp;&amp;</entry>
-		<entry><para>
-		    <command>Logical AND</command></para><para>
-		    <programlisting>ip.src==10.0.0.5 and tcp.flags.fin</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>or</entry>
-		<entry>||</entry>
-		<entry><para>
-		    <command>Logical OR</command></para><para>
-		    <programlisting>ip.scr==10.0.0.5 or ip.src==192.1.1.1</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>xor</entry>
-		<entry>^^</entry>
-		<entry><para>
-		    <command>Logical XOR</command></para><para>
-		    <programlisting>tr.dst[0:3] == 0.6.29 xor tr.src[0:3] == 0.6.29</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>not</entry>
-		<entry>!</entry>
-		<entry><para>
-		    <command>Logical NOT</command></para><para>
-		    <programlisting>not llc</programlisting>
-		  </para></entry>
-	      </row>
-	      <row>
-		<entry>[...]</entry>
-		<entry></entry>
-		<entry><para>
-		    <command>Substring Operator</command></para><para>
-		    Wireshark allows you to select subsequences of a 
-		    sequence in rather elaborate ways.  After a label you 
-		    can place a pair of brackets [] containing a comma 
-		    separated list of range specifiers. </para><para>
-		    <programlisting>eth.src[0:3] == 00:00:83</programlisting></para><para>
-		    The example above uses the n:m format to specify a 
-		    single range.  In this case n is the beginning offset 
-		    and m is the length of the range 
-		    being specified.</para><para>
-		    <programlisting>
+    <title>Combining expressions</title>
+    <para>
+      You can combine filter expressions in Wireshark using the 
+      logical operators shown in <xref linkend="FiltLogOps"/>
+    </para>
+    <table id="FiltLogOps">
+      <title>Display Filter Logical Operations</title>
+      <tgroup cols="3">
+        <colspec colnum="1" colwidth="50pt"/>
+        <colspec colnum="2" colwidth="50pt"/>
+        <thead>
+          <row>
+        <entry>English</entry>
+        <entry>C-like</entry>
+        <entry>Description and example</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+        <entry>and</entry>
+        <entry>&amp;&amp;</entry>
+        <entry><para>
+            <command>Logical AND</command></para><para>
+            <programlisting>ip.src==10.0.0.5 and tcp.flags.fin</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>or</entry>
+        <entry>||</entry>
+        <entry><para>
+            <command>Logical OR</command></para><para>
+            <programlisting>ip.scr==10.0.0.5 or ip.src==192.1.1.1</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>xor</entry>
+        <entry>^^</entry>
+        <entry><para>
+            <command>Logical XOR</command></para><para>
+            <programlisting>tr.dst[0:3] == 0.6.29 xor tr.src[0:3] == 0.6.29</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>not</entry>
+        <entry>!</entry>
+        <entry><para>
+            <command>Logical NOT</command></para><para>
+            <programlisting>not llc</programlisting>
+          </para></entry>
+          </row>
+          <row>
+        <entry>[...]</entry>
+        <entry></entry>
+        <entry><para>
+            <command>Substring Operator</command></para><para>
+            Wireshark allows you to select subsequences of a 
+            sequence in rather elaborate ways.  After a label you 
+            can place a pair of brackets [] containing a comma 
+            separated list of range specifiers. </para><para>
+            <programlisting>eth.src[0:3] == 00:00:83</programlisting></para><para>
+            The example above uses the n:m format to specify a 
+            single range.  In this case n is the beginning offset 
+            and m is the length of the range 
+            being specified.</para><para>
+            <programlisting>
 eth.src[1-2] == 00:83
-		    </programlisting></para><para>
-		    The example above uses the n-m format to specify a 
-		    single range. In this case n is the beginning offset 
-		    and m is the ending offset. </para><para>
-		    <programlisting>eth.src[:4] == 00:00:83:00</programlisting></para><para>
-		    The example above uses the :m format, which takes 
-		    everything from the beginning of a sequence to offset m.  
-		    It is equivalent to 0:m</para><para>
-		    <programlisting>eth.src[4:] == 20:20</programlisting></para><para>
-		    The example above uses the n: format, which takes 
-		    everything from offset n to the end of the 
-		    sequence. </para><para>
-		    <programlisting>eth.src[2] == 83</programlisting></para><para>
-		    The example above uses the n format to specify a 
-		    single range.  In this case the element in the 
-		    sequence at offset n is selected.  This is equivalent 
-		    to n:1.</para><para>
-		    <programlisting>eth.src[0:3,1-2,:4,4:,2] == 
+            </programlisting></para><para>
+            The example above uses the n-m format to specify a 
+            single range. In this case n is the beginning offset 
+            and m is the ending offset. </para><para>
+            <programlisting>eth.src[:4] == 00:00:83:00</programlisting></para><para>
+            The example above uses the :m format, which takes 
+            everything from the beginning of a sequence to offset m.  
+            It is equivalent to 0:m</para><para>
+            <programlisting>eth.src[4:] == 20:20</programlisting></para><para>
+            The example above uses the n: format, which takes 
+            everything from offset n to the end of the 
+            sequence. </para><para>
+            <programlisting>eth.src[2] == 83</programlisting></para><para>
+            The example above uses the n format to specify a 
+            single range.  In this case the element in the 
+            sequence at offset n is selected.  This is equivalent 
+            to n:1.</para><para>
+            <programlisting>eth.src[0:3,1-2,:4,4:,2] == 
 00:00:83:00:83:00:00:83:00:20:20:83</programlisting></para><para>
-		    Wireshark allows you to string together single ranges 
-		    in a comma separated list to form compound ranges as 
-		    shown above.
-		  </para></entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-	</table>
+            Wireshark allows you to string together single ranges 
+            in a comma separated list to form compound ranges as 
+            shown above.
+          </para></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
       </section>
       <section id="ChWorkBuildDisplayFilterMistake"><title>A common mistake</title>
-	  <warning><title>Warning!</title>
-	  <para>
-	  Using the != operator on combined expressions like: eth.addr, ip.addr, 
-	  tcp.port, udp.port and alike will probably not work as expected!
-	  </para>
-	  </warning>
-	  <para>
-	  Often people use a filter string to display something like 
-	  <command>ip.addr == 1.2.3.4</command> which will display all packets
-	  containing the IP address 1.2.3.4.
-	  </para>
-	  <para>
-	  Then they use <command>ip.addr != 1.2.3.4</command> to see all packets 
-	  not containing the IP address 1.2.3.4 in it. Unfortunately, this does 
-	  <command>not</command> do the expected.
-	  </para>
-	  <para>
-	Instead, that expression will even be true for packets where either
-	source or destination IP address equals 1.2.3.4. The reason for this,
-	is that the expression <command>ip.addr != 1.2.3.4</command> must be read as "the
-	packet contains a field named ip.addr with a value
-	different from 1.2.3.4". As an IP datagram contains both a source and
-	a destination address, the expression will evaluate to true whenever
-	at least one of the two addresses differs from 1.2.3.4. 
-	  </para>
-	  <para>
-	If you want to
-	filter out all packets containing IP datagrams to or from IP address
-	1.2.3.4, then the correct filter is <command>!(ip.addr == 1.2.3.4)</command> as it
-	reads "show me all the packets for which it is not true
-	that a field named ip.addr exists with a value of 1.2.3.4", or in
-	other words, "filter out all packets for which there are
-	no occurrences of a field named ip.addr with the value 1.2.3.4".
-	  </para>
+      <warning><title>Warning!</title>
+      <para>
+      Using the != operator on combined expressions like: eth.addr, ip.addr, 
+      tcp.port, udp.port and alike will probably not work as expected!
+      </para>
+      </warning>
+      <para>
+      Often people use a filter string to display something like 
+      <command>ip.addr == 1.2.3.4</command> which will display all packets
+      containing the IP address 1.2.3.4.
+      </para>
+      <para>
+      Then they use <command>ip.addr != 1.2.3.4</command> to see all packets 
+      not containing the IP address 1.2.3.4 in it. Unfortunately, this does 
+      <command>not</command> do the expected.
+      </para>
+      <para>
+    Instead, that expression will even be true for packets where either
+    source or destination IP address equals 1.2.3.4. The reason for this,
+    is that the expression <command>ip.addr != 1.2.3.4</command> must be read as "the
+    packet contains a field named ip.addr with a value
+    different from 1.2.3.4". As an IP datagram contains both a source and
+    a destination address, the expression will evaluate to true whenever
+    at least one of the two addresses differs from 1.2.3.4. 
+      </para>
+      <para>
+    If you want to
+    filter out all packets containing IP datagrams to or from IP address
+    1.2.3.4, then the correct filter is <command>!(ip.addr == 1.2.3.4)</command> as it
+    reads "show me all the packets for which it is not true
+    that a field named ip.addr exists with a value of 1.2.3.4", or in
+    other words, "filter out all packets for which there are
+    no occurrences of a field named ip.addr with the value 1.2.3.4".
+      </para>
       </section>
   </section>
   
@@ -1221,10 +1221,10 @@ eth.src[1-2] == 00:83
       dialog box helps with this.
     </para>
     <tip><title>Tip!</title>
-	<para>
+    <para>
       The "Filter Expression" dialog box is an excellent way to learn how to 
-	  write Wireshark display filter strings.
-	</para>
+      write Wireshark display filter strings.
+    </para>
     </tip>
     <figure id="ChWorkFilterAddExpression1">
       <title>The "Filter Expression" dialog box</title>
@@ -1237,28 +1237,28 @@ eth.src[1-2] == 00:83
     </para>
     <variablelist>
       <varlistentry><term><command>Field Name</command></term>
-	<listitem>
-	  <para>
-	    Select a protocol field from the protocol field tree.  
-	    Every protocol with filterable fields is listed at the 
-	    top level.  (You can search for a particular protocol
+    <listitem>
+      <para>
+        Select a protocol field from the protocol field tree.  
+        Every protocol with filterable fields is listed at the 
+        top level.  (You can search for a particular protocol
             entry by entering the first few letters of the protocol name).
             By clicking on the "+" next to a protocol name 
-	    you can get a list of the field names available for filtering 
-	    for that protocol.
-	  </para>
-	</listitem>
+        you can get a list of the field names available for filtering 
+        for that protocol.
+      </para>
+    </listitem>
       </varlistentry>
       <varlistentry><term><command>Relation</command></term>
-	<listitem>
-	  <para>
-	    Select a relation from the list of available relation.  
-	    The <command>is present</command> is a unary relation which 
-	    is true if the selected field is present in a packet.  All 
-	    other listed relations are binary relations which require additional 
-	    data (e.g. a <command>Value</command> to match) to complete.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        Select a relation from the list of available relation.  
+        The <command>is present</command> is a unary relation which 
+        is true if the selected field is present in a packet.  All 
+        other listed relations are binary relations which require additional 
+        data (e.g. a <command>Value</command> to match) to complete.
+      </para>
+    </listitem>
       </varlistentry>
     </variablelist>
     <para> 
@@ -1269,49 +1269,49 @@ eth.src[1-2] == 00:83
     </para>
     <variablelist>
       <varlistentry><term><command>Value</command></term>
-	<listitem>
-	  <para>
-	    You may enter an appropriate value in the 
-	    <command>Value</command> text box.  The <command>Value</command> 
-	    will also indicate the type of value for the 
-	    <command>field name</command> you have selected (like 
-	    character string).
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        You may enter an appropriate value in the 
+        <command>Value</command> text box.  The <command>Value</command> 
+        will also indicate the type of value for the 
+        <command>field name</command> you have selected (like 
+        character string).
+      </para>
+    </listitem>
       </varlistentry>
       <varlistentry><term><command>Predefined values</command></term>
-	<listitem>
-	  <para>
-	  Some of the protocol fields have predefined values available, much like
-	  enum's in C. If the selected protocol field has such values defined, you
-	  can choose one of them here.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+      Some of the protocol fields have predefined values available, much like
+      enum's in C. If the selected protocol field has such values defined, you
+      can choose one of them here.
+      </para>
+    </listitem>
       </varlistentry>
       <varlistentry><term><command>Range</command></term>
-	<listitem>
-	  <para>
-	  XXX - add an explanation here!
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+      XXX - add an explanation here!
+      </para>
+    </listitem>
       </varlistentry>
       <varlistentry><term><command>OK</command></term>
-	<listitem>
-	  <para>
-	    When you have built a satisfactory expression click 
-	    <command>OK</command> and a filter string will be 
-	    built for you. 
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        When you have built a satisfactory expression click 
+        <command>OK</command> and a filter string will be 
+        built for you. 
+      </para>
+    </listitem>
       </varlistentry>
       <varlistentry><term><command>Cancel</command></term>
-	<listitem>
-	  <para>
-	    You can leave the <command>Add Expression...</command> dialog 
-	    box without any effect by clicking the <command>Cancel</command>
-		button.
-	  </para>
-	</listitem>
+    <listitem>
+      <para>
+        You can leave the <command>Add Expression...</command> dialog 
+        box without any effect by clicking the <command>Cancel</command>
+        button.
+      </para>
+    </listitem>
       </varlistentry>
     </variablelist>
   </section>
@@ -1325,121 +1325,121 @@ eth.src[1-2] == 00:83
     <para>
       To define a new filter or edit an existing one, select the 
       <command>Capture Filters...</command> menu item from the Capture menu 
-	  or the <command>Display Filters...</command> menu item from the Analyze 
-	  menu. Wireshark will then pop up the Filters dialog as shown in 
-	  <xref linkend="FiltersDialog"/>.
+      or the <command>Display Filters...</command> menu item from the Analyze 
+      menu. Wireshark will then pop up the Filters dialog as shown in 
+      <xref linkend="FiltersDialog"/>.
+    </para>
+    <note>
+      <title>Note!</title>
+      <para>
+        The mechanisms for defining and saving capture filters and display 
+        filters are almost identical. So both will be described here, 
+        differences between these two will be marked as such.
+      </para>
+    </note>
+    <warning><title>Warning!</title>
+    <para>
+    You must use <command>Save</command> to save your filters permanently. 
+    <command>Ok</command> or <command>Apply</command> will not save the filters,
+    so they will be lost when you close Wireshark.
     </para>
-	<note>
-	  <title>Note!</title>
-	  <para>
-		The mechanisms for defining and saving capture filters and display 
-		filters are almost identical. So both will be described here, 
-		differences between these two will be marked as such.
-	  </para>
-	</note>
-	<warning><title>Warning!</title>
-	<para>
-	You must use <command>Save</command> to save your filters permanently. 
-	<command>Ok</command> or <command>Apply</command> will not save the filters,
-	so they will be lost when you close Wireshark.
-	</para>
-	</warning>
+    </warning>
     <figure id="FiltersDialog">
       <title>The "Capture Filters" and "Display Filters" dialog boxes</title>
       <graphic entityref="WiresharkFilters" format="PNG"/>
     </figure>
     <para>
       <variablelist>
-	<varlistentry><term><command>New</command></term>
-	  <listitem>
-	    <para>
-	      This button adds a new filter to the list of filters. The currently 
-		  entered values from Filter name and Filter string will be used. If 
-		  any of these fields are empty, it will be set to "new".
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Delete</command></term>
-	  <listitem>
-	  <para>
-	  This button deletes the selected filter. It will be greyed out, if no 
-	  filter is selected.
-	  </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Filter</command></term>
-	  <listitem>
-	    <para>
-		You can select a filter from this list (which will fill in the 
-		filter name and filter string in the fields down at the bottom of the 
-		dialog box).
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Filter name:</command></term>
-	  <listitem>
-	    <para>
-		You can change the name of the currently selected filter here.
-	    </para>
-		<note><title>Note!</title>
-		<para>
-		The filter name will only be used in this dialog to identify the 
-		filter for your convenience, it will not be used elsewhere. You can 
-		add multiple filters with the same name, but this is not very useful.
-		</para>
-		</note>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Filter string:</command></term>
-	  <listitem>
-	    <para>
-		You can change the filter string of the currently selected filter here.
-		Display Filter only: the string will be syntax checked while you are 
-		typing.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Add Expression...</command></term>
-	  <listitem>
-	    <para>
-	      Display Filter only: This button brings up the Add Expression 
-		  dialog box which assists in building filter strings.  You can find 
-		  more information about the Add Expression dialog in 
-	      <xref linkend="ChWorkFilterAddExpressionSection"/>
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>OK</command></term>
-	  <listitem>
-	    <para>
-	      Display Filter only: This button applies the selected filter to the 
-		  current display and closes the dialog.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Apply</command></term>
-	  <listitem>
-	    <para>
-	      Display Filter only: This button applies the selected filter to the 
-		  current display, and keeps the dialog open.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Save</command></term>
-	  <listitem>
-	    <para>
-	      Save the current settings in this dialog. The file location and 
-		  format is explained in <xref linkend="AppFiles"/>.
-	    </para>
-	  </listitem>
-	</varlistentry>
-	<varlistentry><term><command>Close</command></term>
-	  <listitem>
-	    <para>
-	      Close this dialog. This will discard unsaved settings.
-	    </para>
-	  </listitem>
-	</varlistentry>
+    <varlistentry><term><command>New</command></term>
+      <listitem>
+        <para>
+          This button adds a new filter to the list of filters. The currently 
+          entered values from Filter name and Filter string will be used. If 
+          any of these fields are empty, it will be set to "new".
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Delete</command></term>
+      <listitem>
+      <para>
+      This button deletes the selected filter. It will be greyed out, if no 
+      filter is selected.
+      </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Filter</command></term>
+      <listitem>
+        <para>
+        You can select a filter from this list (which will fill in the 
+        filter name and filter string in the fields down at the bottom of the 
+        dialog box).
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Filter name:</command></term>
+      <listitem>
+        <para>
+        You can change the name of the currently selected filter here.
+        </para>
+        <note><title>Note!</title>
+        <para>
+        The filter name will only be used in this dialog to identify the 
+        filter for your convenience, it will not be used elsewhere. You can 
+        add multiple filters with the same name, but this is not very useful.
+        </para>
+        </note>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Filter string:</command></term>
+      <listitem>
+        <para>
+        You can change the filter string of the currently selected filter here.
+        Display Filter only: the string will be syntax checked while you are 
+        typing.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Add Expression...</command></term>
+      <listitem>
+        <para>
+          Display Filter only: This button brings up the Add Expression 
+          dialog box which assists in building filter strings.  You can find 
+          more information about the Add Expression dialog in 
+          <xref linkend="ChWorkFilterAddExpressionSection"/>
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>OK</command></term>
+      <listitem>
+        <para>
+          Display Filter only: This button applies the selected filter to the 
+          current display and closes the dialog.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Apply</command></term>
+      <listitem>
+        <para>
+          Display Filter only: This button applies the selected filter to the 
+          current display, and keeps the dialog open.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Save</command></term>
+      <listitem>
+        <para>
+          Save the current settings in this dialog. The file location and 
+          format is explained in <xref linkend="AppFiles"/>.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry><term><command>Close</command></term>
+      <listitem>
+        <para>
+          Close this dialog. This will discard unsaved settings.
+        </para>
+      </listitem>
+    </varlistentry>
       </variablelist>
     </para>
   </section>
@@ -1463,83 +1463,83 @@ eth.src[1-2] == 00:83
       <command>Edit</command> menu.  Wireshark will pop up the dialog box 
       shown in <xref linkend="ChWorkFindPacketDialog"/>.
     </para>
-	<section><title>The "Find Packet" dialog box</title>
+    <section><title>The "Find Packet" dialog box</title>
     <figure id="ChWorkFindPacketDialog">
       <title>The "Find Packet" dialog box</title>
       <graphic entityref="WiresharkFindPacket" format="PNG"/>
     </figure>
     <para>
-	You might first select the kind of thing to search for:
-	<itemizedlist>
-		<listitem>
-			<para>
-    		<command>Display filter</command>
-			</para>
-			<para>
-			Simply enter a display filter string into the 
-			<command>Filter:</command> field, select a direction, and click on OK.
-			</para>
-			<para>
-			For example, to find the three way handshake for a connection from 
-			host 192.168.0.1, use the following filter string:
-			<programlisting>ip.src==192.168.0.1 and tcp.flags.syn==1</programlisting>
-			For more details on display filters, see <xref linkend="ChWorkDisplayFilterSection"/>
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-    		<command>Hex Value</command>
-			</para>
-			<para>
-			Search for a specific byte sequence in the packet data.
-			</para>
-			<para>
-			For example, use "00:00" to find the next packet including two 
-			null bytes in the packet data.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-    		<command>String</command>
-			</para>
-			<para>
-			Find a string in the packet data, with various options.
-			</para>
-		</listitem>
-	</itemizedlist>
+    You might first select the kind of thing to search for:
+    <itemizedlist>
+        <listitem>
+            <para>
+            <command>Display filter</command>
+            </para>
+            <para>
+            Simply enter a display filter string into the 
+            <command>Filter:</command> field, select a direction, and click on OK.
+            </para>
+            <para>
+            For example, to find the three way handshake for a connection from 
+            host 192.168.0.1, use the following filter string:
+            <programlisting>ip.src==192.168.0.1 and tcp.flags.syn==1</programlisting>
+            For more details on display filters, see <xref linkend="ChWorkDisplayFilterSection"/>
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>Hex Value</command>
+            </para>
+            <para>
+            Search for a specific byte sequence in the packet data.
+            </para>
+            <para>
+            For example, use "00:00" to find the next packet including two 
+            null bytes in the packet data.
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>String</command>
+            </para>
+            <para>
+            Find a string in the packet data, with various options.
+            </para>
+        </listitem>
+    </itemizedlist>
     </para>
     <para>
-	The value to be found will be syntax checked while you type it in. If the 
-	syntax check of your value succeeds, the background of the entry field 
-	will turn green, if it fails, it will turn red.
-	</para>
+    The value to be found will be syntax checked while you type it in. If the 
+    syntax check of your value succeeds, the background of the entry field 
+    will turn green, if it fails, it will turn red.
+    </para>
     <para>
-	You can choose the search direction:
-	<itemizedlist>
-		<listitem>
-    		<para><command>Up</command></para>
-			<para>Search upwards in the packet list (decreasing packet numbers).</para>
-		</listitem>
-	</itemizedlist>
-	<itemizedlist>
-		<listitem>
-    		<para><command>Down</command></para>
-			<para>Search downwards in the packet list (increasing packet numbers).</para>
-		</listitem>
-	</itemizedlist>
-	</para>
+    You can choose the search direction:
+    <itemizedlist>
+        <listitem>
+            <para><command>Up</command></para>
+            <para>Search upwards in the packet list (decreasing packet numbers).</para>
+        </listitem>
+    </itemizedlist>
+    <itemizedlist>
+        <listitem>
+            <para><command>Down</command></para>
+            <para>Search downwards in the packet list (increasing packet numbers).</para>
+        </listitem>
+    </itemizedlist>
+    </para>
   </section>
   <section><title>The "Find Next" command</title>
     <para>
-	"Find Next" will continue searching with the same options used in the last 
-	"Find Packet".
-	</para>
+    "Find Next" will continue searching with the same options used in the last 
+    "Find Packet".
+    </para>
   </section>
   <section><title>The "Find Previous" command</title>
     <para>
-	"Find Previous" will do the same thing as "Find Next", but with reverse 
-	search direction.
-	</para>
+    "Find Previous" will do the same thing as "Find Next", but with reverse 
+    search direction.
+    </para>
   </section>
   </section>
     
@@ -1566,239 +1566,239 @@ eth.src[1-2] == 00:83
       <graphic entityref="WiresharkGoToPacket" format="PNG"/>
     </figure>
     <para>
-	This dialog box will let you enter a packet number. When you press 
-	<command>OK</command>, Wireshark will jump to that packet.
-	</para>
+    This dialog box will let you enter a packet number. When you press 
+    <command>OK</command>, Wireshark will jump to that packet.
+    </para>
   </section>
   <section><title>The "Go to Corresponding Packet" command</title>
     <para>
-	If a protocol field is selected which points to another packet in the 
-	capture file, this command will jump to that packet.
-	</para>
+    If a protocol field is selected which points to another packet in the 
+    capture file, this command will jump to that packet.
+    </para>
     <note><title>Note!</title>
     <para>
-	As these protocol fields now work like links (just as in your 
-	Web browser), it's easier to simply double-click on the field to jump
-	to the corresponding field.
+    As these protocol fields now work like links (just as in your 
+    Web browser), it's easier to simply double-click on the field to jump
+    to the corresponding field.
     </para>
     </note>
   </section>
   <section><title>The "Go to First Packet" command</title>
     <para>
-	This command will simply jump to the first packet displayed.
-	</para>
+    This command will simply jump to the first packet displayed.
+    </para>
   </section>
   <section><title>The "Go to Last Packet" command</title>
     <para>
-	This command will simply jump to the last packet displayed.
-	</para>
+    This command will simply jump to the last packet displayed.
+    </para>
   </section>
   </section>
     
   <section id="ChWorkMarkPacketSection"><title>Marking packets</title>
     <para>
-	You can mark packets in the "Packet List" pane. A marked packet will 
-	be shown with black background, regardless of the coloring rules set.
-	Marking a packet can be useful to find it later while analyzing in a large 
-	capture file.
+    You can mark packets in the "Packet List" pane. A marked packet will 
+    be shown with black background, regardless of the coloring rules set.
+    Marking a packet can be useful to find it later while analyzing in a large 
+    capture file.
     </para>
     <warning><title>Warning!</title>
     <para>
-	The packet marks are not stored in the capture file or anywhere else, 
-	so all packet marks will be lost if you close the capture file.
+    The packet marks are not stored in the capture file or anywhere else, 
+    so all packet marks will be lost if you close the capture file.
     </para>
     </warning>
     <para>
-	You can use packet marking to control the output of packets when 
-	saving/exporting/printing. To do so, an option in the packet range is 
-	available, see <xref linkend="ChIOPacketRangeSection"/>.
+    You can use packet marking to control the output of packets when 
+    saving/exporting/printing. To do so, an option in the packet range is 
+    available, see <xref linkend="ChIOPacketRangeSection"/>.
     </para>
     <para>
-	There are three functions to manipulate the marked state of a packet:
-	<itemizedlist>
-		<listitem>
-    		<para>
-			<command>Mark packet (toggle)</command> toggles the marked state 
-			of a single packet.
-    		</para>
-		</listitem>
-		<listitem>
-    		<para>
-			<command>Mark all displayed packets</command> set the mark state of all 
-			displayed packets.
-    		</para>
-		</listitem>
-		<listitem>
-    		<para>
-			<command>Unmark all packets</command> reset the mark state of all 
-			packets.
-    		</para>
-		</listitem>
-	</itemizedlist>
-	These mark functions are available from the "Edit" menu, and the 
-	"Mark packet (toggle)" function is also available from the pop-up menu of 
-	the "Packet List" pane.
+    There are three functions to manipulate the marked state of a packet:
+    <itemizedlist>
+        <listitem>
+            <para>
+            <command>Mark packet (toggle)</command> toggles the marked state 
+            of a single packet.
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>Mark all displayed packets</command> set the mark state of all 
+            displayed packets.
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>Unmark all packets</command> reset the mark state of all 
+            packets.
+            </para>
+        </listitem>
+    </itemizedlist>
+    These mark functions are available from the "Edit" menu, and the 
+    "Mark packet (toggle)" function is also available from the pop-up menu of 
+    the "Packet List" pane.
     </para>
   </section>
-	
+    
   <section id="ChWorkIgnorePacketSection"><title>Ignoring packets</title>
     <para>
-	You can ignore packets in the "Packet List" pane.  Wireshark will then pretend that this
-	packets does not exist in the capture file. 
-	An ignored packet will be shown with white background and gray foreground, regardless
-	of the coloring rules set.
+    You can ignore packets in the "Packet List" pane.  Wireshark will then pretend that this
+    packets does not exist in the capture file. 
+    An ignored packet will be shown with white background and gray foreground, regardless
+    of the coloring rules set.
     </para>
     <warning><title>Warning!</title>
     <para>
-	The packet ignored marks are not stored in the capture file or anywhere else, 
-	so all packet ignored marks will be lost if you close the capture file.
+    The packet ignored marks are not stored in the capture file or anywhere else, 
+    so all packet ignored marks will be lost if you close the capture file.
     </para>
     </warning>
     <para>
-	There are three functions to manipulate the ignored state of a packet:
-	<itemizedlist>
-		<listitem>
-    		<para>
-			<command>Ignore packet (toggle)</command> toggles the ignored state 
-			of a single packet.
-    		</para>
-		</listitem>
-		<listitem>
-    		<para>
-			<command>Ignore all displayed packets</command> set the ignored state of all 
-			displayed packets.
-    		</para>
-		</listitem>
-		<listitem>
-    		<para>
-			<command>Un-Ignore all packets</command> reset the ignored state of all 
-			packets.
-    		</para>
-		</listitem>
-	</itemizedlist>
-	These ignore functions are available from the "Edit" menu, and the 
-	"Ignore packet (toggle)" function is also available from the pop-up menu of 
-	the "Packet List" pane.
+    There are three functions to manipulate the ignored state of a packet:
+    <itemizedlist>
+        <listitem>
+            <para>
+            <command>Ignore packet (toggle)</command> toggles the ignored state 
+            of a single packet.
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>Ignore all displayed packets</command> set the ignored state of all 
+            displayed packets.
+            </para>
+        </listitem>
+        <listitem>
+            <para>
+            <command>Un-Ignore all packets</command> reset the ignored state of all 
+            packets.
+            </para>
+        </listitem>
+    </itemizedlist>
+    These ignore functions are available from the "Edit" menu, and the 
+    "Ignore packet (toggle)" function is also available from the pop-up menu of 
+    the "Packet List" pane.
     </para>
   </section>
-	
+    
   <section id="ChWorkTimeFormatsSection"><title>Time display formats and time 
   references</title>
-	<para>
-	While packets are captured, each packet is timestamped. These timestamps 
-	will be saved to the capture file, so they will be available for later 
-	analysis.
-	</para>
-	<para>
-	A detailed description of timestamps, timezones and alike can be found at: <xref 
-		linkend="ChAdvTimestamps"/>.
-	</para>
-	<para>
-	The timestamp presentation format and the precision in the packet list can 
-	be chosen using the View menu, see <xref linkend="ChUseWiresharkViewMenu"/>. 
-	</para>
-	<para>
-	The available presentation formats are:
-	<itemizedlist>
-	<listitem><para><command>Date and Time of Day:  1970-01-01 01:02:03.123456</command>
-		The absolute date and time of the day when the packet was captured.</para>
-	</listitem>
-	<listitem><para><command>Time of Day:  01:02:03.123456</command>
-		The absolute time of the day when the packet was captured.</para>
-	</listitem>
-	<listitem><para><command>Seconds Since Beginning of Capture:  123.123456</command>
-		The time relative to the start of the capture file or the first 
-		"Time Reference" before this packet (see <xref 
-		linkend="ChWorkTimeReferencePacketSection"/>).</para>
-	</listitem>
-	<listitem><para><command>Seconds Since Previous Captured Packet:  1.123456</command>
-		The time relative to the previous captured packet.</para>
-	</listitem>
-	<listitem><para><command>Seconds Since Previous Displayed Packet:  1.123456</command>
-		The time relative to the previous displayed packet.</para>
-	</listitem>
-	<listitem><para><command>Seconds Since Epoch (1970-01-01):  1234567890.123456</command>
-		The time relative to epoch (midnight UTC of January 1, 1970).</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	<para>
-	The available precisions (aka. the number of displayed decimal places) are:
-	<itemizedlist>
-	<listitem><para><command>Automatic</command>
-	The timestamp precision of  
-	the loaded capture file format will be used (the default).</para>
-	</listitem>
-	<listitem><para><command>Seconds, Deciseconds, Centiseconds, Milliseconds, 
-	Microseconds or Nanoseconds</command>
-	The timestamp precision will be forced to the given setting. If the 
-	actually available
-	precision is smaller, zeros will be appended. If the precision is larger, 
-	the remaining decimal places will be cut off.</para>
-	</listitem>
-	</itemizedlist>
-	</para>
-	<para>
-	Precision example: If you have a timestamp and it's displayed using,
-	"Seconds Since Previous Packet", : the value might be 1.123456. This will
-	be displayed using the "Automatic" setting for libpcap files (which is 
-	microseconds). If you use Seconds it would show simply 1 and if you use
-	Nanoseconds it shows 1.123456000.
-	</para>
+    <para>
+    While packets are captured, each packet is timestamped. These timestamps 
+    will be saved to the capture file, so they will be available for later 
+    analysis.
+    </para>
+    <para>
+    A detailed description of timestamps, timezones and alike can be found at: <xref 
+        linkend="ChAdvTimestamps"/>.
+    </para>
+    <para>
+    The timestamp presentation format and the precision in the packet list can 
+    be chosen using the View menu, see <xref linkend="ChUseWiresharkViewMenu"/>. 
+    </para>
+    <para>
+    The available presentation formats are:
+    <itemizedlist>
+    <listitem><para><command>Date and Time of Day:  1970-01-01 01:02:03.123456</command>
+        The absolute date and time of the day when the packet was captured.</para>
+    </listitem>
+    <listitem><para><command>Time of Day:  01:02:03.123456</command>
+        The absolute time of the day when the packet was captured.</para>
+    </listitem>
+    <listitem><para><command>Seconds Since Beginning of Capture:  123.123456</command>
+        The time relative to the start of the capture file or the first 
+        "Time Reference" before this packet (see <xref 
+        linkend="ChWorkTimeReferencePacketSection"/>).</para>
+    </listitem>
+    <listitem><para><command>Seconds Since Previous Captured Packet:  1.123456</command>
+        The time relative to the previous captured packet.</para>
+    </listitem>
+    <listitem><para><command>Seconds Since Previous Displayed Packet:  1.123456</command>
+        The time relative to the previous displayed packet.</para>
+    </listitem>
+    <listitem><para><command>Seconds Since Epoch (1970-01-01):  1234567890.123456</command>
+        The time relative to epoch (midnight UTC of January 1, 1970).</para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    <para>
+    The available precisions (aka. the number of displayed decimal places) are:
+    <itemizedlist>
+    <listitem><para><command>Automatic</command>
+    The timestamp precision of  
+    the loaded capture file format will be used (the default).</para>
+    </listitem>
+    <listitem><para><command>Seconds, Deciseconds, Centiseconds, Milliseconds, 
+    Microseconds or Nanoseconds</command>
+    The timestamp precision will be forced to the given setting. If the 
+    actually available
+    precision is smaller, zeros will be appended. If the precision is larger, 
+    the remaining decimal places will be cut off.</para>
+    </listitem>
+    </itemizedlist>
+    </para>
+    <para>
+    Precision example: If you have a timestamp and it's displayed using,
+    "Seconds Since Previous Packet", : the value might be 1.123456. This will
+    be displayed using the "Automatic" setting for libpcap files (which is 
+    microseconds). If you use Seconds it would show simply 1 and if you use
+    Nanoseconds it shows 1.123456000.
+    </para>
   <section id="ChWorkTimeReferencePacketSection">
   <title>Packet time referencing</title>
     <para>
-	The user can set time references to packets. A time reference is the 
-	starting point for all subsequent packet time calculations. It will be 
-	useful, if you want to see the time values relative to a special packet,
-	e.g. the start of a new request. It's possible to set multiple time 
-	references in the capture file.
+    The user can set time references to packets. A time reference is the 
+    starting point for all subsequent packet time calculations. It will be 
+    useful, if you want to see the time values relative to a special packet,
+    e.g. the start of a new request. It's possible to set multiple time 
+    references in the capture file.
     </para>
     <warning><title>Warning!</title>
     <para>
-	The time references will not be saved permanently and will be lost when 
-	you close the capture file.
-	</para>
+    The time references will not be saved permanently and will be lost when 
+    you close the capture file.
+    </para>
     </warning>
     <note><title>Note!</title>
     <para>
-	Time referencing will only be useful, if the time display format is set to 
-	"Seconds Since Beginning of Capture". If one of the other time display 
-	formats are used, time referencing will have no effect (and will make no 
-	sense either).
-	</para>
+    Time referencing will only be useful, if the time display format is set to 
+    "Seconds Since Beginning of Capture". If one of the other time display 
+    formats are used, time referencing will have no effect (and will make no 
+    sense either).
+    </para>
     </note>
     <para>
-	To work with time references, choose one of the "Time Reference" items 
-	in the "Edit" menu , see <xref linkend="ChUseEditMenuSection"/>, or from 
-	the pop-up menu of the "Packet List" pane.
-	</para>
-	<itemizedlist>
-	<listitem><para><command>Set Time Reference (toggle)</command>
-		Toggles the time reference state of the currently selected 
-		packet to on or off.</para>
-	</listitem>
-	<listitem><para><command>Find Next</command>
-		Find the next time referenced packet in the "Packet List" pane.
-		</para>
-	</listitem>
-	<listitem><para><command>Find Previous</command>
-		Find the previous time referenced packet in the "Packet List" 
-		pane.
-		</para>
-	</listitem>
-	</itemizedlist>
+    To work with time references, choose one of the "Time Reference" items 
+    in the "Edit" menu , see <xref linkend="ChUseEditMenuSection"/>, or from 
+    the pop-up menu of the "Packet List" pane.
+    </para>
+    <itemizedlist>
+    <listitem><para><command>Set Time Reference (toggle)</command>
+        Toggles the time reference state of the currently selected 
+        packet to on or off.</para>
+    </listitem>
+    <listitem><para><command>Find Next</command>
+        Find the next time referenced packet in the "Packet List" pane.
+        </para>
+    </listitem>
+    <listitem><para><command>Find Previous</command>
+        Find the previous time referenced packet in the "Packet List" 
+        pane.
+        </para>
+    </listitem>
+    </itemizedlist>
     <para>
     <figure id="ChWorkTimeReference">
       <title>Wireshark showing a time referenced packet</title>
       <graphic entityref="WiresharkTimeReference" format="PNG"/>
     </figure>
-	</para>
-	<para>
-	A time referenced packet will be marked with the string *REF* in the Time 
-	column (see packet number 10). All subsequent packets will show the time 
-	since the last time reference.
-	</para>
+    </para>
+    <para>
+    A time referenced packet will be marked with the string *REF* in the Time 
+    column (see packet number 10). All subsequent packets will show the time 
+    since the last time reference.
+    </para>
   </section>
   </section>
 
diff --git a/docbook/wsug_src/WSUG_preface.xml b/docbook/wsug_src/WSUG_preface.xml
index 0beec59202..6a638da127 100644
--- a/docbook/wsug_src/WSUG_preface.xml
+++ b/docbook/wsug_src/WSUG_preface.xml
@@ -11,7 +11,7 @@
   </para>
   <para>
     This document is part of an effort by the Wireshark team to improve the 
-	usability of Wireshark.
+    usability of Wireshark.
   </para>
   <para>
     We hope that you find it useful, and look forward to your comments.
@@ -48,71 +48,71 @@
   <title>Acknowledgements</title>
   <para>
     The authors would like to thank the whole Wireshark team for their 
-	assistance. In particular, the authors would like to thank:
+    assistance. In particular, the authors would like to thank:
     <itemizedlist>
       <listitem>
-	<para>
-	  Gerald Combs, for initiating the Wireshark project and funding to 
-	  do this documentation.
-	</para>
+    <para>
+      Gerald Combs, for initiating the Wireshark project and funding to 
+      do this documentation.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Guy Harris, for many helpful hints and a great deal of patience 
-	  in reviewing this document.
-	</para>
+    <para>
+      Guy Harris, for many helpful hints and a great deal of patience 
+      in reviewing this document.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Gilbert Ramirez, for general encouragement and helpful hints along 
-	  the way.
-	</para>
+    <para>
+      Gilbert Ramirez, for general encouragement and helpful hints along 
+      the way.
+    </para>
       </listitem>
     </itemizedlist>
   </para>
   <para>
     The authors would also like to thank the following people for their 
-	helpful feedback on this document:
+    helpful feedback on this document:
     <itemizedlist>
       <listitem>
-	<para>
-	  Pat Eyler, for his suggestions on improving the example on 
-	  generating a backtrace.
-	</para>
+    <para>
+      Pat Eyler, for his suggestions on improving the example on 
+      generating a backtrace.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Martin Regner, for his various suggestions and corrections.
-	</para>
+    <para>
+      Martin Regner, for his various suggestions and corrections.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Graeme Hewson, for a lot of grammatical corrections.
-	</para>
+    <para>
+      Graeme Hewson, for a lot of grammatical corrections.
+    </para>
       </listitem>
     </itemizedlist>
   </para>
   <para>
     The authors would like to acknowledge those man page and README authors 
-	for the Wireshark project from who sections of this document borrow heavily:
+    for the Wireshark project from who sections of this document borrow heavily:
     <itemizedlist>
       <listitem>
-	<para>
-	  Scott Renfro from whose <command>mergecap</command> man page 
-	  <xref linkend="AppToolsmergecap"/> is derived.
-	</para>
+    <para>
+      Scott Renfro from whose <command>mergecap</command> man page 
+      <xref linkend="AppToolsmergecap"/> is derived.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Ashok Narayanan from whose <command>text2pcap</command> man page 
-	  <xref linkend="AppToolstext2pcap"/> is derived.
-	</para>
+    <para>
+      Ashok Narayanan from whose <command>text2pcap</command> man page 
+      <xref linkend="AppToolstext2pcap"/> is derived.
+    </para>
       </listitem>
       <listitem>
-	<para>
-	  Frank Singleton from whose <filename>README.idl2wrs</filename> 
-	  <xref linkend="AppToolsidl2wrs"/> is derived. 
-	</para>
+    <para>
+      Frank Singleton from whose <filename>README.idl2wrs</filename> 
+      <xref linkend="AppToolsidl2wrs"/> is derived. 
+    </para>
       </listitem>
     </itemizedlist>
   </para>
@@ -124,31 +124,31 @@
       This book was originally developed by 
       <ulink url="mailto:&AuthorEmail2;">Richard Sharpe</ulink> with 
       funds provided from the Wireshark Fund. It was updated by 
-	  <ulink url="mailto:&AuthorEmail3;">Ed Warnicke</ulink> and more recently 
-	  redesigned and updated by <ulink url="mailto:&AuthorEmail;">Ulf 
-	  Lamping</ulink>.
+      <ulink url="mailto:&AuthorEmail3;">Ed Warnicke</ulink> and more recently 
+      redesigned and updated by <ulink url="mailto:&AuthorEmail;">Ulf 
+      Lamping</ulink>.
     </para>
     <para>
       It is written in DocBook/XML.
     </para>
     <para>
-	You will find some specially marked parts in this book:
+    You will find some specially marked parts in this book:
     </para>
     <warning><title>This is a warning!</title>
-	<para>
-	You should pay attention to a warning, as otherwise data loss might occur.
-	</para>
+    <para>
+    You should pay attention to a warning, as otherwise data loss might occur.
+    </para>
     </warning>
     <note><title>This is a note!</title>
-	<para>
-	A note will point you to common mistakes and things that might not be 
-	obvious.
-	</para>
+    <para>
+    A note will point you to common mistakes and things that might not be 
+    obvious.
+    </para>
     </note>
     <tip><title>This is a tip!</title>
-	<para>
-	Tips will be helpful for your everyday work using Wireshark.
-	</para>
+    <para>
+    Tips will be helpful for your everyday work using Wireshark.
+    </para>
     </tip>
   </section>