Re: [whatwg/encoding] Big5 encoding mishandles some trailing bytes, with possible XSS (#171)

moztw.org maintains a [repository of information about Big5](https://translate.google.com/translate?sl=zh-CN&tl=en&u=http%3A%2F%2Fmoztw.org%2Fdocs%2Fbig5%2F). Checking the UAO tables there, it's worth noting that [UAO had mappings](http://moztw.org/docs/big5/table/uao250-b2u.txt) for the byte pairs whose lead is in the range 0x81 to 0x86 (inclusive), so even though the research that lead to the current state of the spec concluded that HKSCS was used on the Web and UAO pretty much not (and, therefore, the spec went with HKSCS instead of UAO), a UAO encoder could produce byte pairs whose lead is in the range 0x81 to 0x86 (inclusive). Both [Python](https://pypi.org/project/uao/) and [Node](https://www.npmjs.com/package/uao-js) have quite recent UAO packages.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/171#issuecomment-461731368