On 08/20/2017 01:05 AM, J.B. Nicholson wrote:
> Nominal Animal wrote:
>> We've lost another freedom, choosing the default character set encoding
>> in Firefox and Chrome/Chromium browsers.
>
> That sounds like upstream developers are making something you want more
> inconvenient. We should
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
On 2017-08-20 01:05, J.B. Nicholson wrote:
Nominal Animal wrote:
We've lost another freedom, choosing the default character set encoding
in Firefox and Chrome/Chromium browsers.
That sounds like upstream developers are making something you want
more inconvenient. We should distinguish
Nominal Animal wrote:
We've lost another freedom, choosing the default character set encoding
in Firefox and Chrome/Chromium browsers.
That sounds like upstream developers are making something you want more
inconvenient. We should distinguish between what's going on with Firefox (a
free
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
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.
(By banning, I mean you cannot set it
