Unicode Support - #111
Open
siaeyy wants to merge 16 commits into
Open
Conversation
Decode utf-8 content from char array to uint32_t array
Encode raw content from uint32_t array to uint8_t array within given length
Cap messages without breaking utf-8 format
…port Before sending a message to clients, decode utf-8 formatted value and encode it ot mutf-8. With format change, now unicode characters are supported.
p2r3
requested changes
Sep 16, 2025
Owner
|
Yep, there go the merge conflicts. Good luck 😅 |
Author
|
Conflicts chose me as the victim :c |
siaeyy
force-pushed
the
unicode-support
branch
2 times, most recently
from
September 24, 2025 15:23
0f1b679 to
78f0117
Compare
|
I think the conflicts are fixed. Maybe you can merge the branch? IDK if it is efficient enough... |
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
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.
Time for criticism
Closes #52