We are using BC on the cmd line to compare 2 pdf files and return match or not matched. There are date fields in the pdf which we have successfully used Importance - Grammar to exclude within the GUI. There we are able to see the mismatched text turn blue denoting the mismatches that are ok. We did get this to work ok with docx files on the cmd line, but now with similar steps to exclude mismatched dates with our pdf files, the cmd code below is returning Error Code = 13 (Rules Based Differences).
I am guessing that the imported bcpkg settings are not being ignored, but I have tried to comment the load out and set it up manually in the GUI, but on the cmd its still returning Error=13. Its odd that it works fine for us with docx files but we have issues with our pdf files. The only difference is that there is only 1 exception with the docx and there are 3 exceptions with the pdf (due to the text spanning multiple lines).
Thoughts on how to programmatically ensure the cmd compare returns a "Match" after excluding our exceptions?
I am guessing that the imported bcpkg settings are not being ignored, but I have tried to comment the load out and set it up manually in the GUI, but on the cmd its still returning Error=13. Its odd that it works fine for us with docx files but we have issues with our pdf files. The only difference is that there is only 1 exception with the docx and there are 3 exceptions with the pdf (due to the text spanning multiple lines).
Thoughts on how to programmatically ensure the cmd compare returns a "Match" after excluding our exceptions?
Code:
@echo off set file1=%1 set file2=%2 if not exist "C:\Program Files\Beyond Compare 4\bcomp.com" goto error "C:\Program Files\Beyond Compare 4\bcompare" "Z:\Automation_Tools\Beyond Compare\PolicyGenDate_pdf.bcpkg" /silent echo %ERRORLEVEL% echo Imported bcpkg "C:\Program Files\Beyond Compare 4\bcomp.com" /qc %file1% %file2% echo %ERRORLEVEL%
Comment