Valid behavior for .text() and .json() if encoding is not known

[fafhrd91]

What should be valid behavior for .text() and .json() if encoding is not known.

see #108

[kxepal]

About JSON there is RFC 7159 recommendation:

JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32.  The default
encoding is UTF-8, and JSON texts that are encoded in UTF-8 are
interoperable in the sense that they will be read successfully by the
maximum number of implementations; there are many implementations
that cannot successfully read texts in other encodings (such as
UTF-16 and UTF-32).

As for text/plain it is a different story:

A critical parameter that may be specified in the Content-Type field
for "text/plain" data is the character set.  This is specified with a
"charset" parameter, as in:

 Content-type: text/plain; charset=iso-8859-1

Unlike some other parameter values, the values of the charset
parameter are NOT case sensitive.  The default character set, which
must be assumed in the absence of a charset parameter, is US-ASCII.

[kxepal]

About behaviour, raising UnicodeDecodeError is ok. May be only with more better description like: "expected utf-8 encoded data, found something weird" etc.

[fafhrd91]

sounds good

[fafhrd91]

i suppose we do not need to do anything about this.

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.