Fix incorrect logic in CharIsPrintable for UnicodeCategory exclusions #14079
+2
−2
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.
Fixes #14072
Proposed changes
CharIsPrintablecontains a semantic error in the combination of is not and or. As a result, it returns true for any character that is notControl, incorrectly classifying characters fromFormat,LineSeparator,ParagraphSeparator, andOtherNotAssignedas printable.Impact: Zero-width spaces, line separators, paragraph separators, and unassigned code points are treated as printable, even though they render as invisible, garbled symbols, or empty spaces.
Microsoft Reviewers: Open in CodeFlow