COMMON: Add string encoding API with more informative error behavior #4017
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.
This updates the string encode API to return a status code indicating whether the encoding completely succeeded, or if it contains errors.
Currently, unmappable characters are just silently encoded as "?" so there is no way to determine if a Unicode code point is valid on a particular code page other than seeing if it comes out as "?" when the input character wasn't "?" which is a pretty gnarly hack.
The mTropolis engine needs this to filter out keystrokes that don't map to a valid character.