Re: [whatwg/encoding] Adopt GB18030-2022 (PR #336)

@annevk commented on this pull request.



> @@ -845,7 +845,7 @@ specification, excluding <a>index single-byte</a>, which have their own table:
   <td colspan=3><a href=index-gb18030-ranges.txt>index-gb18030-ranges.txt</a>
   <td>This <a>index</a> works different from all others. Listing all code points would result
   in over a million items whereas they can be represented neatly in 207 ranges combined with trivial
-  limit checks. It therefore only superficially matches the GB18030-2005 standard for code points
+  limit checks. It therefore only superficially matches the GB18030-2022 standard for code points

So instead of

> It therefore only superficially matches the GB18030-2022 standard for code points encoded as four bytes.

maybe something like

> It therefore only superficially matches the GB18030-2005 standard for code points encoded as four bytes. It does not match the GB18030-2022 standard as that would increase the number of four-byte sequences mapping to Unicode Private Use Areas. The other direction is handled by a side table in the gb18030 encoder.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/pull/336#discussion_r1765394381
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/encoding/pull/336/review/2313250453@github.com>