Skip to content

doc: add documentation for invalid byte sequences #28249

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.

Sign up for GitHub

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

Closed
rexagod wants to merge 6 commits into from
Closed

doc: add documentation for invalid byte sequences #28249

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
aa01448
doc: add documentation for invalid byte sequences
rexagod Jun 16, 2019
a5c9915
Update buffer.md
rexagod Jun 16, 2019
0b2d591
re-position doc segment
rexagod Jun 16, 2019
1739d22
Update doc/api/buffer.md
rexagod Jul 5, 2019
834df54
Update doc/api/buffer.md
rexagod Jul 5, 2019
3e7d1bb
Update doc/api/buffer.md
rexagod Jul 5, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update doc/api/buffer.md 
Co-Authored-By: Rich Trott <rtrott@gmail.com>
  • Loading branch information
@rexagod @Trott
rexagod and Trott authored Jul 5, 2019
commit 3e7d1bbeb7fc0978a515c193878d3e8f838ac06b
2 changes: 1 addition & 1 deletion doc/api/buffer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -209,7 +209,7 @@ in rare cases) `'ascii'` data, and the valid [`UTF-8` code units](https://en.wik
the replacement character (`�`) is returned,
and no exception will be thrown.

It should also be noted that a `U+FFFD` replacement value
A `U+FFFD` replacement value
(representing the aforementioned replacement character) will be returned
in case of decoding errors (invalid unicode scalar values).
Copy link
Copy Markdown
Member

@addaleax addaleax Jul 5, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest, I don’t understand most of the text or its relevance here… the text basically says that invalid UTF-8 byte sequences will be decoded into U+FFFD replacement characters and that no error will be thrown in those cases, right?

How do UTF-16 and ASCII relate to that? What does “non-legal Unicode value” mean? (I would guess that this refers to characters that would be beyond U+10FFFF – if that’s correct, can you clarify that in the text?)


Expand Down