diff options
| author | Gerald Combs <gerald@wireshark.org> | 2016-09-13 11:29:25 -0700 |
|---|---|---|
| committer | Gerald Combs <gerald@wireshark.org> | 2016-09-13 21:02:54 +0000 |
| commit | 3c163637d6890ce5782fc204186629b789932d32 (patch) | |
| tree | 35a67604c3e6a5538389523f90a4c56ecc7c33a4 /docbook/wsug_src/WSUG_chapter_statistics.asciidoc | |
| parent | 1e3c57b486b1d6a443cc29884337f983ca61bbfe (diff) | |
| download | wireshark-3c163637d6890ce5782fc204186629b789932d32.tar.gz | |
WSUG: Fixup PDF images.
Pass relative image directory paths to xsltproc. The DocBook documentation
says you can use a URI, but trying to get that to work with CMake
and Windows appears to be a path to tears and undignified wails of
frustration.
Add attributes for our different types of images and use them so that
the PDFs don't scale our screenshots to an unusable size.
Change-Id: I786d09d9ef9be3d423b2af426a8867739ae12c1a
Reviewed-on: https://code.wireshark.org/review/17688
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
Diffstat (limited to 'docbook/wsug_src/WSUG_chapter_statistics.asciidoc')
| -rw-r--r-- | docbook/wsug_src/WSUG_chapter_statistics.asciidoc | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/docbook/wsug_src/WSUG_chapter_statistics.asciidoc b/docbook/wsug_src/WSUG_chapter_statistics.asciidoc index d88a54b84e..f1ba386374 100644 --- a/docbook/wsug_src/WSUG_chapter_statistics.asciidoc +++ b/docbook/wsug_src/WSUG_chapter_statistics.asciidoc @@ -49,7 +49,7 @@ be pretty hard to understand. General statistics about the current capture file. .The ``Summary'' window -image::wsug_graphics/ws-stats-summary.png[] +image::wsug_graphics/ws-stats-summary.png[{screenshot-attrs}] * __File__: general information about the capture file. @@ -77,7 +77,7 @@ image::wsug_graphics/ws-stats-summary.png[] The protocol hierarchy of the captured packets. .The ``Protocol Hierarchy'' window -image::wsug_graphics/ws-stats-hierarchy.png[scaledwidth="100%"] +image::wsug_graphics/ws-stats-hierarchy.png[{screenshot-attrs}] This is a tree of all the protocols in the capture. Each row contains the statistical values of one protocol. Two of the columns (_Percent Packets_ and @@ -147,7 +147,7 @@ per second in each direction. A timeline graph is also drawn across the ``Rel Start'' / ``Abs Start'' and ``Duration'' columns. .The ``Conversations'' window -image::wsug_graphics/ws-stats-conversations.png[scaledwidth="100%"] +image::wsug_graphics/ws-stats-conversations.png[{screenshot-attrs}] Each row in the list shows the statistical values for exactly one conversation. @@ -249,7 +249,7 @@ will be received by some or all of the listed unicast endpoints. This window shows statistics about the endpoints captured. .The ``Endpoints'' window -image::wsug_graphics/ws-stats-endpoints.png[scaledwidth="100%"] +image::wsug_graphics/ws-stats-endpoints.png[{screenshot-attrs}] 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 · 4'' tells @@ -291,7 +291,7 @@ User configurable graph of the captured network packets. You can define up to five differently colored graphs. .The ``IO Graphs'' window -image::wsug_graphics/ws-stats-iographs.png[] +image::wsug_graphics/ws-stats-iographs.png[{screenshot-attrs}] The user can configure the following things: @@ -374,12 +374,12 @@ corresponding response. First of all, you have to select the DCE-RPC interface: .The "Compute DCE-RPC statistics" window -image::wsug_graphics/ws-stats-srt-dcerpc-filter.png[] +image::wsug_graphics/ws-stats-srt-dcerpc-filter.png[{screenshot-attrs}] You can optionally set a display filter, to reduce the amount of packets. .The "DCE-RPC Statistic for ..." window -image::wsug_graphics/ws-stats-srt-dcerpc.png[] +image::wsug_graphics/ws-stats-srt-dcerpc.png[{screenshot-attrs}] 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 @@ -404,7 +404,7 @@ is found it is checked for: * Packet order .The "Compare" window -image::wsug_graphics/ws-stats-compare.png[] +image::wsug_graphics/ws-stats-compare.png[{screenshot-attrs}] You can configure the following: @@ -440,7 +440,7 @@ network traffic found in the capture. Probe requests will be merged into an existing network if the SSID matches. .The "WLAN Traffic Statistics" window -image::wsug_graphics/ws-stats-wlan-traffic.png[] +image::wsug_graphics/ws-stats-wlan-traffic.png[{screenshot-attrs}] Each row in the list shows the statistical values for exactly one wireless network. |