Re: [whatwg/encoding] The concept of "output encoding" is not described anywhere (Issue #291)

> The respective encodings don't have a defined encoder

Well, that's a recursive explanation. _Why_ they don't have a defined encoder? Why did someone decide that if we could not encode the text in one encoding, then some other would be suitable for us? It looks absurd! I.e. we tell the recipient that we have one encoding and are actually encoded into another. Or we definitely know that the consumer expects one specific encoding, we try to encode into it... and get a text encoded in other encoding instead of error explaining that this encoding is unsupported. I have no idea what scenario of use such a substitution has. Can this be explained in the specification together with examples when this can be needed?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/291#issuecomment-1224182960
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/encoding/issues/291/1224182960@github.com>