https://issues.apache.org/bugzilla/show_bug.cgi?id=51873
--- Comment #19 from Jeremy <[email protected]> 2011-10-20 20:30:28 UTC --- Well thats certainly helpedme mak some headway on that today when I wasn't busy with other things. I've got a utility up and working that uses the EntryUtils to copy or skip blocks from coming over... The problem I'm having now is trying to figure out which entry is being used that holds the binary data. I removed all of the largest in size entries, but both the raw text and binary encoded version remained in the then corrupted msg file. LOL I'm guessing that perhaps one of the entries contains information as to where in the file the encoded portion of the text message resides? Any hints as to trying to pinpoint which chunk relates to the encoded message body? Either via poi utility classes or methods or through the hex-editor? I suppose worst-comes to worst, I can try dropping them one at a time and see which one works. As long as its not a combination of dropped chunks that I need. LOL (In reply to comment #18) > One option is to just drop the chunks you can't properly clean. That may > result > in a file that outlook is a bit funny about, but should help us with testing! > The way to do that would be to open the file in POIFS, iterate through the > entries, and either copy to a new POIFS instance or skip. See > org.apache.poi.poifs.filesystem.EntryUtils for a guide to doing this -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
