You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UTF-8 today (well since 2003 😏 ) must not contain any code-point byte sequences for Unicode code points beyond those that can be encoded in UTF-16 - which means that the maximum acceptable Unicode code point is U+10FFF - which is within the range that can be conveyed with 4-bytes. This suggests that the code in the listed method can detect something as UTF-8 when it MUST (for RFC values of MUST 😀 ) in fact reject it (as per RFC3629)...
The text was updated successfully, but these errors were encountered:
UTF-8 today (well since 2003 😏 ) must not contain any code-point byte sequences for Unicode code points beyond those that can be encoded in UTF-16 - which means that the maximum acceptable Unicode code point is U+10FFF - which is within the range that can be conveyed with 4-bytes. This suggests that the code in the listed method can detect something as UTF-8 when it MUST (for RFC values of MUST 😀 ) in fact reject it (as per RFC3629)...
The text was updated successfully, but these errors were encountered: