When using the CLI to compare two CSVs that were encoded using cp1252 on a platform with a default encoding of utf-8, it fails. Since the encoding is not specified when opening the files, the default encoding is used and fails for any byte sequences that are not valid utf-8. This looks like it would resolve #14. The fix in this PR is to allow the user to specify the encoding of the file as a command line option.
When using the CLI to compare two CSVs that were encoded using cp1252 on a platform with a default encoding of utf-8, it fails. Since the encoding is not specified when opening the files, the default encoding is used and fails for any byte sequences that are not valid utf-8. This looks like it would resolve #14. The fix in this PR is to allow the user to specify the encoding of the file as a command line option.