From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.0.0.0/16 X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 2F9BB1F667 for ; Sat, 19 Aug 2017 14:01:45 +0000 (UTC) Received: from localhost ([::1]:54556 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dj4Jq-0006oF-Im for e@80x24.org; Sat, 19 Aug 2017 10:01:42 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46323) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dizlr-0004Fl-K3 for libreplanet-discuss@gnu.org; Sat, 19 Aug 2017 05:10:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dizlo-0001Um-Bu for libreplanet-discuss@gnu.org; Sat, 19 Aug 2017 05:10:19 -0400 Received: from 4.mo3.mail-out.ovh.net ([178.33.46.10]:41191) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dizlo-0001UE-52 for libreplanet-discuss@gnu.org; Sat, 19 Aug 2017 05:10:16 -0400 Received: from player158.ha.ovh.net (b6.ovh.net [213.186.33.56]) by mo3.mail-out.ovh.net (Postfix) with ESMTP id 88F4C12C161 for ; Sat, 19 Aug 2017 11:10:12 +0200 (CEST) Received: from [84.250.249.108] (dsl-hkibng31-54faf9-108.dhcp.inet.fi [84.250.249.108]) (Authenticated sender: question@nominal-animal.net) by player158.ha.ovh.net (Postfix) with ESMTPSA id 86BB462008C for ; Sat, 19 Aug 2017 11:10:12 +0200 (CEST) To: libreplanet-discuss@gnu.org From: Nominal Animal Message-ID: <9c5bcec9-9b3f-12be-d254-2579351d0c9b@nominal-animal.net> Date: Sat, 19 Aug 2017 12:10:12 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Language: en-US X-Ovh-Tracer-Id: 32651101046586077 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 50 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeelkedruddthedgudegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecufedttdenucgoteefjeefqddtgeculdehtddm X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 178.33.46.10 X-Mailman-Approved-At: Sat, 19 Aug 2017 10:01:15 -0400 Subject: UTF-8 banned from being default in Chrome, Firefox X-BeenThere: libreplanet-discuss@libreplanet.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: libreplanet-discuss-bounces+e=80x24.org@libreplanet.org Sender: "libreplanet-discuss" 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 as the default, not via the UI, or by directly editing the user preferences: the setting is disallowed in the sources. The only way to remove the ban is to recompile the browsers from sources, applying a patch that removes the ban.) This affects those web pages that do not declare a specific character set, like many mailing list archives; and local plain text files. (list.gnu.org provides a Content-Type header with charset=UTF-8, which I do warmly commend the list admin! -- but for example marc.info does not.) Both Chrome and Firefox developers insist that the *proper* default character set is none other than Windows-1252, or some other encoding (other than UTF-8) for non-Western users. The system locale used by the user is ignored in all cases. The underlying logic for these developers, as far as I could ascertain from the bug reports and changelogs, was that only "legacy" charsets should be selectable as a default, and UTF-8 is the (only) non-legacy character set encoding. In my opinion, that is a non-sequitur: those settings have nothing to do with "legacy", and everything to do with "default". I tried to raise this question with the developers involved (particularly Henri Sivonen for Firefox), but I was blocked; apparently these issues are already covered in the relevant bugzillas (marked WONTFIX). (Also, particularly Sivonen, likes to claim that choosing UTF-8 as the character set encoding if no encoding is specified is "unreasonable". On systems like GNU/Linux or GNU/Hurd, or even BSD variants, there often are no "legacy" content without character set definition, other than in UTF-8 -- this is particularly true in my case, including the servers I maintain --, so "unreasonable" seems to me be a disguise for something else.) I was wondering whether this kind of removal of user choice is something the LibrePlanet folks could help with? I suspect publicity is the best disinfectant against such encroachment. Best regards, Nominal Animal (I use a pseudonym in order to handle criticism better, as everything directed to "Nominal Animal" is directed at my expression/advice/opinions, not at my "social person". My physical identity is not a secret, and I can provide it if needed, but as mentioned, I function better under this pseudonym.) _______________________________________________ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss