osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

WSDG: Adjust markup and fix FOP warnings 

Wrap monospace text in our PDF output. Fix the formatting of a list. Fix
an anchor reference.

Change-Id: Id9433f3e3462569299e6702b4a4e137481ad80c4
Reviewed-on: https://code.wireshark.org/review/17877
Reviewed-by: Gerald Combs <gerald@wireshark.org>
This commit is contained in:
Gerald Combs 2016-09-22 15:43:37 -07:00
parent eeb4361e57
commit e0bc5b1c3e
3 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docbook/custom_layer_pdf.xsl
View File

@ -53,8 +53,12 @@
</xsl:attribute-set>
<!-- reduce the size of programlisting to make them fit the page -->
<!-- We might want to set the hyphenation character to "\":
http://www.sagehill.net/docbookxsl/FittingText.html
-->
<xsl:attribute-set name="monospace.verbatim.properties">
<xsl:attribute name="font-size">80%</xsl:attribute>
<xsl:attribute name="wrap-option">wrap</xsl:attribute>
</xsl:attribute-set>
</xsl:stylesheet>

23
docbook/wsug_src/WSUG_chapter_advanced.asciidoc
View File

@ -128,34 +128,35 @@ You can choose to decode the data from one of the following formats:
You can choose to view the data in one of the following formats:
. __ASCII__: In this view you see the bytes as ASCII.
[horizontal]
*ASCII*:: In this view you see the bytes as ASCII.
All control characters and non-ASCII bytes are replaced by dot.
. __ASCII & Control__: In this view all control characters are shown using a
*ASCII & Control*:: In this view all control characters are shown using a
UTF-8 symbol and all non-ASCII bytes are replaced by dot.
. __C Array__: This allows you to import the field data into your own C program.
*C Array*:: This allows you to import the field data into your own C program.
. __EBCDIC__: For the big-iron freaks out there.
*EBCDIC*:: For the big-iron freaks out there.
. __HEX Dump__: This allows you to see all the data. This will require a lot of
*HEX Dump*:: This allows you to see all the data. This will require a lot of
screen space and is best used with binary protocols.
. __HTML__: This allows you to see all the data formatted as a HTML document.
*HTML*:: This allows you to see all the data formatted as a HTML document.
The HTML supported is what's supported by the Qt QTextEdit class.
. __Image__: This will try to convert the bytes into an image.
*Image*:: This will try to convert the bytes into an image.
Images supported are what's supported by the Qt QImage class.
. __ISO 8859-1__: In this view you see the bytes as ISO 8859-1.
*ISO 8859-1*:: In this view you see the bytes as ISO 8859-1.
. __Raw__: This allows you to load the unaltered stream data into a different
*Raw*:: This allows you to load the unaltered stream data into a different
program for further examination. The display will show HEX data, but
``Save As'' will result in a binary file.
. __UTF8__: In this view you see the bytes as UTF-8.
*UTF8*:: In this view you see the bytes as UTF-8.
. __YAML__: This will show the bytes as a YAML binary dump.
*YAML*:: This will show the bytes as a YAML binary dump.
[[ChAdvExpert]]

8
docbook/wsug_src/WSUG_chapter_statistics.asciidoc
View File

@ -132,7 +132,7 @@ protocols will carry more than one IP header.
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
<<ChStatEndpointDefinition>>.
<<ChStatEndpoints>>.
[[ChStatConversationsWindow]]
@ -165,7 +165,7 @@ will show the stream contents as described in <<ChAdvFollowStream>> dialog. The
button:[Graph...] button will show a graph as described in <<ChStatIOGraphs>>.
button:[Conversation Types] lets you choose which traffic type tabs are shown.
See <<ChStatEndpointDefinition>> for a list of endpoint types. The enabled types
See <<ChStatEndpoints>> for a list of endpoint types. The enabled types
are saved in your profile settings.
[TIP]
@ -181,8 +181,6 @@ it before (or while) you are doing a live capture.
=== Endpoints
[[ChStatEndpointDefinition]]
A network endpoint is the logical endpoint of separate protocol traffic of a
specific protocol layer. The endpoint statistics of Wireshark will take the
following endpoints into account:
@ -270,7 +268,7 @@ The button:[Copy] button will copy the list values to the clipboard in CSV
endpoints mapped in your web browser.
button:[Endpoint Types] lets you choose which traffic type tabs are shown. See
<<ChStatEndpointDefinition>> above for a list of endpoint types. The enabled
<<ChStatEndpoints>> above for a list of endpoint types. The enabled
types are saved in your profile settings.
[TIP]