On Wed, 18 Mar 2015, Adrian Conlon wrote:
WRT test files, there's a test file associated with the bugzilla entry, did you mean something more targeted than this?
We really want a files with a value of 69, 70 and 71, showing a mapping to 2069, 1970 and 1971 (assuming that's the right change-over date)
I've added some extra information from the Microsoft open specifications to the item which actually seems to make the use of this header in POI date metadata extraction a bit suspect. It might be better to drop the use of the message submission chunk for date extraction moving forward.
Once we have something to replace it with, that'd be good. That needs better fixed-sized property support though!
For moving HSMF forward, I'll have a think about what you said. My knowledge of the current code base is pretty slack. Only the message submission chunk really! Is the current code built upon HPSF or POIFS? If so, I might start having a play with the Microsoft specs...
POIFS. The property decoding is of MAPI properties, not OLE2 ones. Much of the decoding is there, the missing steps are around matching a property in the property chunk up to a poifs chunk with the value in, and then how to tie it all together at read time nicely
Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
