Conversation
The originally used xshowBlob function converted String to ByteString by truncating the character to 8-bit value, essentially limiting the character set to Latin 1. It also didn't escape XML characters properly.
zlondrej
force-pushed
the
fix-character-truncation-and-xml-escaping
branch
from
September 14, 2026 16:29
02155e5 to
6e8a650
Compare
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.
The originally used
xshowBlobfunction convertedStringtoByteStringby truncating the character to 8-bit value (Data.ByteString.Lazy.Char8.pack), essentially limiting the character set to Latin 1.It also didn't escape XML characters properly: #7.
The issues were addressed by using
xshowEscapeXmlinstead ofxshowBloband using UTF-8 conversion toByteString.