path: root/doc/README.xml-output
diff options
authorRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2006-05-22 08:14:01 +0000
committerRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2006-05-22 08:14:01 +0000
commitf0b33a47893e76488561e57d6c2dce07a1295d4b (patch)
tree94060daf713860116bedfbe9673d9a057b4a0824 /doc/README.xml-output
parent92552c2d765dcf89883392fcd11556d54f2843e5 (diff)
ethereal->wireshark updates
svn path=/trunk/; revision=18206
Diffstat (limited to 'doc/README.xml-output')
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.xml-output b/doc/README.xml-output
index 154b394..5af7e80 100644
--- a/doc/README.xml-output
+++ b/doc/README.xml-output
@@ -32,7 +32,7 @@ It causes Analyzer to crash. As such, the PDML that ethereal produces
is be labled with a version number of "0", which means that the PDML does
not fully follow the PDML spec. Furthemore, a creator attribute in the
"<pdml>" tag gives the version number of [t]ethereal that produced the PDML.
-In that way, as the PDML produced by ethereal matures, but still does not
+In that way, as the PDML produced by wireshark matures, but still does not
meet the PDML spec, scripts can make intelligent decisions about how to
best parse the PDML, based on the "creator" attribute.
@@ -93,7 +93,7 @@ a field with a field-name. Those appear in PDML as "<field>" tags with no
Many dissectors label the undissected payload of a protocol as belonging
to a "data" protocol, and the "data" protocol usually resided inside
that last protocol dissected. In the PDML, The "data" protocol becomes
-a "data" field, placed exactly where the "data" protocol is in ethereal's
+a "data" field, placed exactly where the "data" protocol is in wireshark's
protocol tree. So, if ethereal would normally show:
+-- Frame