Re: [whatwg/encoding] ISO-2022-JP encoder: convert halfwidth Katakana to fullwidth (#106)

I think we shouldn't make the encoder consider more than one code point to decide what to output, because:

1. Chromium, WebKit and Edge don't have that behavior.
2. ISO-2022-JP is a fringe encoding _on the Web_, so we shouldn't try to improve it from what most browsers do and it's better to have cross-browser consistent behavior than for Firefox to retain an arguably elegant special behavior. (I'm aware of the email situation)
3. The _encoder side_ of ISO-2022-JP is even more fringe _on the Web_, so we shouldn't try to improve it from what most browsers do and it's better to have cross-browser consistent behavior than for Firefox to retain an arguably elegant special behavior (and IMO email clients should follow Gmail's and Apple Mail's lead and always send UTF-8).
4. Half-width Katakana is a fringe feature in today's non-terminal environments that browsers exist in. So much so that ISO-2022-JP can't represent it. It's not like many users will be inputting half-width Katakana.
5. No other encoding considers more than one code point when deciding what to output. (Admittedly "no other encoding" isn't a strong reason, because ISO-2022-JP already has "no other encoding" behaviors that complicate the API surface for encoders.)

-- 
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/pull/106#issuecomment-299623334