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-32 certainly is not a legacy character encoding, since it is, in fact, a Unicode encoding defined by Unicode.
GB18030 is an interesting case, since it does encode the full repertoire but is not a Unicode encoding defined by Unicode. I think I'm fine with the ambiguity in that case?
https://www.w3.org/TR/i18n-glossary/#dfn-legacy-character-encodings
It seems that UTF-32 and GB 18030 don't count as legacy character encodings according to this definition. Is it intentional?
The text was updated successfully, but these errors were encountered: