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

[Gerald Combs <gerald@xxxxxxxxxxxx>]

Guy Harris wrote:
> 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?

Run time would probably work; it'd be a simple matter to add something
like "-g readformats" and "-g writeformats".


> ".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".

I tend to use .pcap as well.  (It's 2006.  Can we declare 8.3 officially
dead yet?)

It's not just .cap that has overlapping formats - http://filext.com/
lists several overlapping types for .acp, and .dmp.