-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Normal
-
Affects Version/s: 2.8.5
-
Component/s: Lookup & Match
-
None
-
Environment:Debian GNU/Linux
When opening CD extraction logs, it seems that Picard expects the file to be in UTF-8 encoding. If the file is in ISO encoding, Picard fails to read it with an "utf8 codec can't decode byte 0xce in position...", for example.
While I agree that it's 2023 and everyone should be using UTF-8, there are people that still don't. It would be great if the file encoding would be detected instead of assuming UTF-8, because having to convert log files to UTF-8 before opening them is a bit annoying.