Re: [encoding] Benefits of "Legacy" Encodings – Byte Counter (#4)

The text processing tool we are working on uses UTF-8 (and converts to target encoding on output), but the tens of thousands of Oracle* projects it processes cannot be simply converted to UTF-8. I just thought if there was no such artificial restriction,** we could implement the character counting in an easy way (otherwise we will have to call a server-side character counter on input, which will be slow).

* I was just told there is no problem to name our company, I only cannot say this is an official statement.

** The browsers are (should be) capable of "legacy" encodings, e.g. because of form's [accept-charset](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form#attr-accept-charset) attribute, the standard just does not allow them to encode.

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