"Unix" -> "Unicode" in Char.GetUnicodeCategory() Remarks#3075
Merged
rpetrusha merged 1 commit intodotnet:masterfrom Aug 26, 2019
Merged
"Unix" -> "Unicode" in Char.GetUnicodeCategory() Remarks#3075rpetrusha merged 1 commit intodotnet:masterfrom
rpetrusha merged 1 commit intodotnet:masterfrom
Conversation
The term "the Unix Standard" is incorrect and should instead be "the Unicode Standard". I fixed 4 instances of this mistake, all in "GetUnicodeCategory". This mistake appears to have been introduced in the following commit on March 21, 2017: dotnet@cd8c569#diff-206ae69d9a4bfeaf7052220b8e8cde2a
rpetrusha
added
the
✨ 1st-time dotnet-api-docs contributor!
Contributor
Author
|
@rpetrusha You're welcome 😺 |
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
2 participants
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 term "the Unix Standard" is incorrect and should instead be "the Unicode Standard". I fixed 4 instances of this mistake, all in "GetUnicodeCategory". This mistake appears to have been introduced in the following commit on March 21, 2017:
cd8c569#diff-206ae69d9a4bfeaf7052220b8e8cde2a