From: Nominal Animal <question@nominal-animal.net>
To: Andy Oram <andyo@oreilly.com>
Cc: libreplanet-discuss@gnu.org
Subject: Re: UTF-8 banned from being default in Chrome, Firefox
Date: Sun, 20 Aug 2017 01:36:59 +0300 [thread overview]
Message-ID: <243bb7ed-354f-2e83-c404-0ef4b6ba2793@nominal-animal.net> (raw)
In-Reply-To: <CAKYPV_7Fihv8Wxby-P276xttW-88n1VxvWxJUbT3ey4q-9i7+w@mail.gmail.com>
On 20/08/17 00:29, Andy Oram wrote:
> I think the situation for each browser may be more complicated than your email
> suggests,
I admit I am quite aggravated by this issue. Apologies.
I should have condensed my point to the fact that users *no longer*
can set UTF-8 as the character set to be used if neither the server
or the document itself specifies a character set.
This used to be possible, but is now deliberately disabled.
Perhaps others might take a look at the developer discussion around the
changes, and provide a more balanced summary of the situation?
This functionality was in Firefox until four years ago,
https://bugzilla.mozilla.org/show_bug.cgi?id=815551
https://bugzilla.mozilla.org/show_bug.cgi?id=1071816
https://github.com/mozilla/gecko-dev/commit/5ac2a5be04f63fc1a2ee87f2c4536064072aa71d
and in Chrome until this year:
https://bugs.chromium.org/p/chromium/issues/detail?id=597488
https://goo.gl/47cdcb
Much appreciated,
Nominal Animal
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-19 22:37 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
2017-08-19 22:36 ` Nominal Animal [this message]
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=243bb7ed-354f-2e83-c404-0ef4b6ba2793@nominal-animal.net \
--to=question@nominal-animal.net \
--cc=andyo@oreilly.com \
--cc=libreplanet-discuss@gnu.org \
/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).