[whatwg/encoding] EUC-JP encoding is currently ambiguous (#225)

Step 7 currently reads as follows:

"Let pointer be the index pointer for code point in index jis0208."

This is ambiguous because there are several code points where there are several pointers to the same code point, such as 0xFA16 has two.  I've observed that Chrome and Firefox always choose the larger of the two.  Strangely, 0xFFE2 has three pointers (137, 8644, and 10736) and Chrome and Firefox use the smallest (137) in this case.  The web platform tests cover these cases.

I was implementing this in https://bugs.webkit.org/show_bug.cgi?id=215970 and noticed these were not specified, so I thought I'd make an issue and see if it's worth making the spec more specific since we are about to have 3 identical implementations.


-- 
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/225

Received on Saturday, 29 August 2020 05:04:22 UTC