From: Andy Oram <andyo@oreilly.com>
To: Nominal Animal <question@nominal-animal.net>
Cc: libreplanet-discuss@gnu.org
Subject: Re: UTF-8 banned from being default in Chrome, Firefox
Date: Sat, 19 Aug 2017 17:29:27 -0400 [thread overview]
Message-ID: <CAKYPV_7Fihv8Wxby-P276xttW-88n1VxvWxJUbT3ey4q-9i7+w@mail.gmail.com> (raw)
In-Reply-To: <9c5bcec9-9b3f-12be-d254-2579351d0c9b@nominal-animal.net>
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)
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-20 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 9:10 UTF-8 banned from being default in Chrome, Firefox Nominal Animal
2017-08-19 21:29 ` Andy Oram [this message]
2017-08-19 22:36 ` Nominal Animal
2017-08-19 23:05 ` J.B. Nicholson
2017-08-20 9:09 ` François Téchené
2017-08-20 10:32 ` David Hedlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKYPV_7Fihv8Wxby-P276xttW-88n1VxvWxJUbT3ey4q-9i7+w@mail.gmail.com \
--to=andyo@oreilly.com \
--cc=libreplanet-discuss@gnu.org \
--cc=question@nominal-animal.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).