https://issues.apache.org/bugzilla/show_bug.cgi?id=51873
--- Comment #17 from Jeremy <[email protected]> 2011-10-19 15:20:02 UTC --- Unfortunately I'm still reluctant to release the document as per our contract with the source. If you could help point me in the right direction, that would be greatly appreciated. I've got all the metadata and raw text already hex-edited out. But it appears the message text is also stored in another block in some encoded manner which is then decoded and appears when the message is opened. It would be great if you could help direct me towards the specs for determining the encoding method used and any utilities that may be useful for re-encoding my newly hex-edited version of the content. I'm assuming and hoping that the re-encoded version will be of the same size and length and won't corrupt the original document? It appears the encoded version of the text is in a block labeled as: _._.s.u.b.s.t.g.1...0._.1.0.4.6.0.0.1.E Thanks again for the help. (In reply to comment #16) > I'd be happy to have a go at editing the file, to see if I can manage to > remove > all the identifiable bits. Well, as long as it takes me under about 10 > minutes... :) -- 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]
