On Wed, Oct 24, 2007 at 07:30:05PM +0200, Luis EG Ontanon wrote:
> BTW url-encoding filenames would be a solution for this kind of
> isues... guess what urlencoding was thought for exactly that!
>
> filename%20with%20spaces.ext
I was hoping that GLib would have functions to handle this, but it d
> -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. ;-)
>
>
Luis EG Ontanon wrote:
> in *NIX filenames with spaces are particularly tedious... I
> personally would forbid spaces in filenames en-toto as they tend to
> make scripts fail...
Well, insufficiently-carefully-written scripts, anyway.
$ echo a b > a\ b
$ echo c d > c\ d
BTW url-encoding filenames would be a solution for this kind of
isues... guess what urlencoding was thought for exactly that!
filename%20with%20spaces.ext
On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote:
>
>
> Luis EG Ontanon wrote:
> > On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote:
>
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 w
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 tedio
Jeff Morriss wrote:
> 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
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 objec
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, hav
Good morning.
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 been created from the original HTTP GET request
10 matches
Mail list logo
