Hi,
I'm using Beyond Compare 3.1.11, build 12204 (trial version with Pro features) and I found an annoying bug.
When I compare 2 zip files using "directory comparison", Beyond Compare 3 is not able to display and compare multiple files of the same fully-qualified name within archives.
I mean, zip format allows multiple files of the same fully-qualified name to exist within a single archive, and BC3 can't display those multiple files (only one of the two is displayed and compared). So in my case the comparison was wrong, as I did not receive any information telling me that one of my two zip file had 2 files of the same fully-qualified name within the archive...
For your information, such a zip file (with multiple files of the same fully-qualified name) was generated using an Ant task. See http://ant.apache.org/manual/Tasks/zip.html for details.
Hope this'll be fixed soon !
Thanks
Announcement
Collapse
No announcement yet.
BUG report : duplicate files in a zip archive not displayed
Collapse
X
-
BUG report : duplicate files in a zip archive not displayed
-
Hello Aaron,
Originally posted by Aaron View PostThe first solution I would recommend would be to avoid duplicate names. The Zip format supports some behavior that does not directly translate into a logical directory comparison.
Since I discovered this particular ZIP format specification, I've modified my Ant task that is generating my zip files so it's not duplicating files anymore. But I think that BC3 should be able to warn the user about that.
Originally posted by Aaron View PostIn these cases you can use the Hex Compare or treat the zips as files and run a Binary comparison on them. These would compare the zip files bit by bit, and would let you know if there were any differences between the two files.
The "directory comparison" for archive files is in my opinion one of the very best features of BC3, as it allows to compare what's inside archives, and not the archives themselves.
A directory comparison tells the user exactly what's different between two archives, and a binary comparison only tells the user "your files are different (or not)" and it's sometimes not significant at all, as depending on how the archives were build, what's inside them might be identical, even if archives are different.
Originally posted by Aaron View PostIf you could attach an example zip, or send it to us in an email (with a link back to this forum post) to support@scootersoftware.com , we would appreciate it as a test case and could look into adding a log message.
Thanks a lot for your reply,
violent_ken
Leave a comment:
-
Hello Ken,
From the article you linked to:
Please note that the zip format allows multiple files of the same fully-qualified name to exist within a single archive. This has been documented as causing various problems for unsuspecting users. If you wish to avoid this behavior you must set the duplicate attribute to a value other than its default, "add".
In these cases you can use the Hex Compare or treat the zips as files and run a Binary comparison on them. These would compare the zip files bit by bit, and would let you know if there were any differences between the two files.
If you could attach an example zip, or send it to us in an email (with a link back to this forum post) to support@scootersoftware.com , we would appreciate it as a test case and could look into adding a log message.
Leave a comment:
Leave a comment: