Re: [encoding] iso-2022-jp encoder XSS risks (#15)

Note on the implementation in Blink: 

Blink uses ICU and  emits NCRs (, etc) for U+000E, U+000F and U+001B because those characters are regarded as non-encodable in ISO-2022-JP and unencodable characters are converted to NCRs (by a generic substitution function common to all encodings).  

If it's decided that the NCR for U+FFFD be emitted for lone U+00(0E,0F,1B), the easiest for Blink would be to add a custom 'subst. function' for ISO-2022-JP (instead of trying to change ICU's behavior).  

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/15#issuecomment-174704473