-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Adding documentation for System.Text APIs tergeted for 3.0 #2875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
xml/System.Text/UTF32Encoding.xml
Outdated
## Remarks | ||
The <xref:System.Text.UTF32Encoding> object can provide a preamble, which is an array of bytes that can be prefixed to the sequence of bytes resulting from the encoding process. Prefacing a sequence of encoded bytes with a byte order mark (code points U+0000 U+FEFF) helps the decoder determine the byte order and the transformation format, or UTF. The Unicode byte order mark (BOM) is serialized as follows (in hexadecimal): | ||
|
||
- Big endian byte order: 00 00 FE FF |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would probably look better with:
- Big endian byte order: 00 00 FE FF | |
- Big endian byte order: `00 00 FE FF` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok then I'll do the same on the Preamble
property of the other classes.
xml/System.Text/UTF32Encoding.xml
Outdated
|
||
- Big endian byte order: 00 00 FE FF | ||
|
||
- Little endian byte order: FF FE 00 00 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Little endian byte order: FF FE 00 00 | |
- Little endian byte order: `FF FE 00 00` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM,
Just one thing you may consider changing is, as we are dealing with the API's using Spans, would be nice in the text not to use phrases like "byte array" or "array size" and instead may use Span/Memory?
@tarekgh good point, I will remove the word "array" from the Remarks so it can be inferred that we are talking about the span. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks very good, @jozkee. I've left a number of suggestions for you to consider.
Co-Authored-By: Ron Petrusha <ronpet@microsoft.com>
Thanks for the additional changes, @jozkee. I'll merge this PR now. |
APIs documented: