fix: improve encoding correctness and update README#36
Merged
Conversation
Fix multiple UTF-8, UTF-16LE, and Windows-1252 correctness issues reported by @exodus/bytes cross-testing. Highlights: - UTF-8: proper BOM handling, validation of malformed sequences, replacement with U+FFFD, correct handling of lone surrogates - UTF-16LE: prevent emitting invalid surrogate sequences and handle odd trailing bytes - Windows-1252: fix incorrect handling of C1 control range mappings - Align fallback behavior more closely with native TextEncoder/TextDecoder Docs: - Clarify README purpose as a small encoding polyfill - Remove misleading runtime support claims
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix multiple UTF-8, UTF-16LE, and Windows-1252 correctness issues reported by @ChALkeR.
Highlights:
Docs:
Resolves #30 (hopefully)