Wireshark · Ethereal-dev: Re: [Ethereal-dev] Native file dialogs under Windows

[Guy Harris <gharris@xxxxxxxxx>]

Gerald Combs wrote:

> Yes.  There should also be separate lists for read-only and read-write
> formats.  A comment in win32-file-dlg.c mentions pulling the extension
> list from ethereal.nsi, but we should probably find some way to dump the
> list from Wiretap to ethereal.nsi instead.

At compile time, or at run time?

> The Windows file saving code should probably add an extension if the
> user didn't supply one as well.  BTW, is there an official extension for
> pcap-formatted files?

I'm not sure there's an official extension for any file format not 
created by Microsoft, as I'm not sure there's an official registry third 
parties can use.

".cap" is an example of the apparent lack of such a registry, as several 
*different* file formats use it; I'd prefer that we not worsen the 
problem. :-)

I've been using ".pcap", although it doesn't follow the "3 characters" 
convention; we're all using modern versions of Windows that can handle 
files with four-character extensions.

Analyzer uses ".acp" for libpcap format; WildPackets' ProConvert uses 
".dmp".