attempt to use encoding header for decoding #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The encoding of some files is getting detected incorrectly. If a character, that gets changed due to a different encoding being used, is present in the audio file path it will lead to a canonicalzation error.
While automatic encoding detection is not something that I will touch with a 10ft pole we can work around this by honoring the
#ENCODING
header if it is present.As these chars are always interpreted correctly regardless of the encoding we can decode as
ASCII
and disregard any invalid bytes. If the header is not present it falls back on the previous auto-detection algorithm.(Example File that gets misidentified: petit milady - 360° Hoshi no Orchestra (TV).txt)