Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62)

As for Edge's behavior, Edge must be interpreting EUC-KR label strictly (that is,  interpreting it as NOT being able to encode 8,821 Hangul syllables that are NOT a part of the original KS X 1001 when it was KS C 5601). Edge is lenient in the decoding direction, though. 

@ri2a, have you tried using the label 'ks_c_5601-1987' instead? It'll be interesting to see how Edge treats that label. MS IE used that label to refer to Windows-949 (they should not !)  even though KS C 5601-1987 does not have any provision to encode 8,821 Hangul syllables in the way Windows-949 encodes. 


Firefox used to have even more strict interpretation. KS X 1001 (formerly KS C 5601) has a provision to encode 8,821 Hangul syllables with 8-byte sequences and Firefox used to encode them that way with EUC-KR. It does not do that anymore, I guess. 

-- 
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/62#issuecomment-247547807