https://issues.apache.org/bugzilla/show_bug.cgi?id=28231
--- Comment #12 from Trejkaz <[EMAIL PROTECTED]> 2008-03-06 12:52:51 PST --- Microsoft don't even have a bug tracking system, and filing a bug won't solve all the existing files anyway. But thanks for getting this in, it's one less custom patch for our local branch. It's true that they're supposed to be multiples of 512 bytes, but if the last block in the file contains the end of a stream (happens fairly often) and the stream itself isn't a multiple of 512 bytes (also happens fairly often), sometimes they just don't pad it out to the 512-byte boundary. But since the stream length is declared elsewhere in the file and all the bytes in the stream are present, it seems silly to even warn about it possibly being truncated as none of the real data has been lost, only the padding. If a stream itself is truncated (declared to be longer than the amount of data available in its blocks) or if a block declared in the file isn't actually present... that sort of thing is a critical error still, of course. -- 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]
