Alternate Encoding Handling for Addon Content #4596
Merged
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.
Identify the Bug or Feature request
fixes #4594
Description of the Change
Adds an ugly try/catch chain that attempts to determine the encoding of the byte array instead of assuming UTF8
Possible Drawbacks
Only handles ASCII, UTF-8, UTF-16, or Latin1 - and doesn't read file if can't determine encoding (null).
Documentation Notes
Uses Standard Java Charset Decoding, assuming different encodings until it matches or fails entirely.
Release Notes
Added Encoding Checks for Addon File Import
This change is