http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1912
Summary: Fix an assortment of typos and other minor errors in
various README files
Product: Wireshark
Version: SVN
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Low
Component: Documentation
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: acferen@xxxxxxxxx
Build Information:
wireshark 0.99.7 (SVN Rev 23160)
Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.10.11, with GLib 2.12.11, with libpcap 0.9.8, with libz
1.2.3, with libpcre 6.7, without SMI, with ADNS, without Lua, with GnuTLS
1.4.4,
with Gcrypt 1.2.3, without Kerberos, with PortAudio <= V18, without AirPcap.
Running on Linux 2.6.20-16-generic, with libpcap version 0.9.8.
Built using gcc 4.1.2 (Ubuntu 4.1.2-0ubuntu4).
--
I'll attach patch files for most issues, but there were two sentences where I
couldn't decided how they ought to read.
In README.developer:
original lines:
In addition, that also means that when opening or creating a binary
file, you must use "open()" (with O_CREAT and possibly O_TRUNC if the
file is to be created if it doesn't exist), and OR in the O_BINARY flag.
That flag is not present on most, if not all, UNIX systems, so you must
also do
#ifndef O_BINARY
#define O_BINARY 0
#endif
to properly define it for UNIX (it's not necessary on UNIX).
source of confusion:
"define it for UNIX" AND "not necessary on UNIX" ???
In README.plugins:
original lines
The plugin registration has changed with the extension of the build
scripts. These now generate the additional code needed for plugin
encapsulation in plugin.c. When using the new style build scripts,
stips the parts outlined below:
source of confusion:
"stips". Sorry, no idea how this is supposed to read.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
