You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now character encodings are taken from HTTP headers. While the RFC mandates that encodings be specified, some websites don't do that. Right now the library assumes UTF-8 if no encoding is specified in Content-Type. However, this is brittle. A better way is to use character encoding detection, for example, from text-icu. This has been started in the chardet branch.
The text was updated successfully, but these errors were encountered:
Right now character encodings are taken from HTTP headers. While the RFC mandates that encodings be specified, some websites don't do that. Right now the library assumes UTF-8 if no encoding is specified in Content-Type. However, this is brittle. A better way is to use character encoding detection, for example, from
text-icu
. This has been started in thechardet
branch.The text was updated successfully, but these errors were encountered: