According to Dom Lachowicz <[EMAIL PROTECTED]>:
> Yeah, the Eazel/Nautilus guys are having one hell of a time trying to
> "sniff" the type of these documents so that they can display proper icons or
> maybe render some of its contents. They're basically doing the same thing as
> our RecognizeContents() method (only more advanced than us).
and file(2) shokes on OLE document too.
> >What should we do then ?
> >Create a structure storage model that works ? Use OLE2 ?
> >BTW I think this is not for 1.0 :-)
> >Definetly not.
>
> Some suggestions have come up, though I'm not sure how much wieght to give
> any of them:
>
> 1) EFS - the embedded FS. Used with a few Bonobo apps
Any doc ?
> 2) TGZ - rebels!
> 3) ZIP - OpenOffice
Nope.
> 4) OLE2 - very common
Very dangerous: controlled by Microsoft which will not hesitate to corrupt it.
We'd better to not bet on the same horse.
[...]
> It should be noted that SWD (StarWriter docs), Corel's WP, and MSFT all use
> #4.
Flash Pix too.
This raise the problem of depending on libole2 for other importers (remember
my post on SDW file format investigations, a couple of monthes ago ?)
> This is probably a post-1.0 issue, but is well-worth to begin considering
> and discussing now, IMHO.
Yes.
Hub
