Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
See this streams utility and associated information to further explore the issue.

I've never thought that SummaryInformation was stored anywhere except inside the file, for COM "Compound Document" files specifically including MS Office files. The shell extension simply looks at that.

Meanwhile, I noticed that Windows 2000 allowed a Summary tab on other files as well. I assumed it stored that in an alternate stream, but never looked into it in detail.

So I disagree with your second paragraph. To read SummaryInfo from a Structured Storage file, use the SS-related function for that. (IPropertyStorage, I think). The COM SDK has a page "Structured Storage Serialized Property Set Format". If that interface is a dual (dispatch-enabled), then it's a simple matter to drive with Perl's OLE module and then parse out the individual fields.

The alternate data stream is trivial to read from Perl, once you figure out the correct name. I suppose it uses the same serialized format.

I agree, a Perl module to read/write this information would be awesome! It would figure out which way is being used, and use the proper way to add info to a file that doesn't have it already.


In reply to Re: Win32 Strustured Storage via File - Properties - Summary by John M. Dlugosz
in thread Win32 Strustured Storage via File - Properties - Summary by idnopheq

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others lurking in the Monastery: (2)
As of 2024-06-17 20:50 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.