PrestoSoft Community

Thanks. The structure I tested has multiple folder levels but maybe there is something else that is different.

Thanks for the instructions. The end result is different from yours: no errors comparing two folders from WSL, with full file comparison and plug-ins enabled. This is both in 13 and 14 Beta. There must be something different about either your setup or, less likely, with your EDP options.

Thanks for confirming! BTW, we will most likely stop supporting XP with the next version.

I believe we tested it. What error do you get?

We don't use WSL in house. Is the any way to reproduce it in Windows 10?

The following have been included in the latest Beta 14.0 build:

• New: Ability to switch between different code pages to display byte codes in binary comparison

• Improvement: The width of the address column in binary comparison views is based on file sizes

Currently, as you said, the only way to deal with these use cases is to start a new instance externally. We'll look into these scenarios more closely a bit later, and perhaps will make dealing with them easier.

Open a comparison of 2 files Select "New Comparison" Check "Run in new instance" Click on "Empty files" Bug: Current instance is closed This is not new in 14.0. "Run in new instance" only applies to real comparison while "Empty files" is a shortcut ...

OK, in light of what was said, here's the plan. We'll delay the input file code page (and default page) implementation to a future version. For this version (14, now in Beta), we'll try and make the following change to binary comparison: instead of the current Binary Options | Character Set, we'll h...

Sounds good. If we decide to go with this approach, (1) it will be done in the next version (15) and (2) the existing EBCDIC support in binary comparison will go away, for obvious reasons.

Thanks. We were thinking about these code pages... Here's an idea: why should EBCDIC files treated as second-class citizens and compared as binary files? Or, for that matter, any other non-Unicode (ANSI) code pages? So one potential approach would be to have an option in EDP to define the default co...

If the document is corrupt to begin with, while the error message looks cryptic, it's what the OOXML library returns. Interpreting all possible errors is not feasible.

What are the steps to reproduce? I try the original steps, with and without "Save files before re-comparison", and it worked as expected.

ExamDiff Pro does not have a subscription model. You can always upgrade to the latest version if you have owned ExamDiff Pro before.

Could you please provide some sample files that encoded with code page 37? And maybe a couple of code page 500 files?