Re: [libreplanet-discuss] UTF-8 banned from being default in Chrome, Firefox

[Andy Oram]

Thanks for reporting this interesting gap in browser support, Nominal
Animal. I am not an expert in encodings or browsers, and I think the
situation for each browser may be more complicated than your email
suggests, but it looks like you have identified a problem. And it's
interesting given the following statements.

Andy

---

https://www.w3.org/International/questions/qa-choosing-encodings

"Choose UTF-8 for all content and consider converting any content in legacy
encodings to UTF-8."


https://www.w3schools.com/html/html_charset.asp

"The default character encoding for HTML5 is UTF-8."

Andy Oram  |  Editor
O'Reilly Media, Inc.  |  617-499-7479 |  oreilly.com

[image: oreilly_email_logo.png] <http://oreilly.com/>



On Sat, Aug 19, 2017 at 5:10 AM, Nominal Animal <question@nominal-animal.net
> wrote:

> We've lost another freedom, choosing the default character set encoding
> in Firefox and Chrome/Chromium browsers.
>
> I only recently noticed that Firefox has banned UTF-8 as a default
> character set encoding about four years ago.
> Chrome followed suit this year.
>
>
> (snip)