Mark G. wrote:
-Original Message-
From: Stephen Fisher
Sent: Tuesday, October 23, 2007 8:29 PM
I could not think of a really good way to handle these
filenames thatare unsavable when I implemeneted the export
object feature. Were you hoping to save all of the objects
with
On 10/24/07, Jeff Morriss [EMAIL PROTECTED] wrote:
Since it's primarily Windows that should have this problem (AFAICR most
*NIXs allow anything other than / in a file name) it should be easy
enough to find a list of prohibited chars.
in *NIX filenames with spaces are particularly tedious...
Luis EG Ontanon wrote:
On 10/24/07, Jeff Morriss [EMAIL PROTECTED] wrote:
Since it's primarily Windows that should have this problem (AFAICR most
*NIXs allow anything other than / in a file name) it should be easy
enough to find a list of prohibited chars.
in *NIX filenames with spaces
-Original Message-
From: Guy Harris
Sent: Wednesday, October 24, 2007 11:23 AM
Mark G. wrote:
But for those of us who are using Wireshark to leech large
numbers of images from a commercial web site, the incremental
naming feature would be very helpful. ;-)
Isn't that
On Tue, Oct 23, 2007 at 08:04:05AM -0700, Mark G. wrote:
I am using Wireshark to capture a large number of JPEG2000 images from
a web site. The captured images appear in the export/objects/http
dialog with mime type application/octet-stream. But their default
filenames are invalid, having
