https://bz.apache.org/bugzilla/show_bug.cgi?id=58061
Nick Burch <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Nick Burch <[email protected]> --- The files won't be identical at the byte level, as the code for assigning blocks is different in NPOIFS. Streams should be the same though It's odd that things are breaking, as I believe people have been using NPOIFS for ages with HSSF without problems. Does it happen with all files written, or only certain ones? What's the smallest file we can generate with OPOIFS and NPOIFS that shows it? (It's much easier to compare at the byte/raw level something small!) If you take a problematic file, generate it with OPOIFS and with NPOIFS, then run POIFSDump on the two, are the various streams the same? Can NPOIFS open and read the problematic file OK? Can OPOIFS read it? Can HSSF read it? -- 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]
