Whilst it probably shouldn't be allowed under the FCS standard, at least one machine I work with (CellQuest Pro 6) produces FCS files that contain non-UTF8 characters.
This PR enables UnicodeDecodeError, which is thrown by illegal UTF-8 characters in the header, to be handled via string.decode("utf-8", errors="ignore") which will ignore any illegal bytes.
A warning is returned to the user, highlighting the problem.
Whilst it probably shouldn't be allowed under the FCS standard, at least one machine I work with (CellQuest Pro 6) produces FCS files that contain non-UTF8 characters.
This PR enables UnicodeDecodeError, which is thrown by illegal UTF-8 characters in the header, to be handled via
string.decode("utf-8", errors="ignore")which will ignore any illegal bytes.A warning is returned to the user, highlighting the problem.
(addresses #7)