Surrogate pair encoding char-codes #x10000-#x1FFFF #6
Conversation
This file contains 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.
Original description:
According to the documentation found in the net [1], characters outside basic multilingual plane should be encoded using surrogate pairs.
This is minimally tested, but works on my use case where I need to feed EMOJI to a mobile client and my users were getting garbage displayed to them.
Optimally, the decoding side should probably be hacked to be able to do the reverse as well. I don't have need for this at the moment so haven't looked into it yet.
[1] http://www.ietf.org/rfc/rfc4627.txt "2.5 Strings"