From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#57531: 28.1; Character encoding missing for "eo" Date: Mon, 05 Sep 2022 13:33:12 +0000 Message-ID: <0b2303e39222951afb20@heytings.org> References: <87h71r0w5z.fsf@jonreeve.com> <83h71qqq5e.fsf@gnu.org> <878rn1p7oz.fsf@jonreeve.com> <8335d8o6ow.fsf@gnu.org> <877d2kpfe1.fsf@jonreeve.com> <83o7vwmlet.fsf@gnu.org> <875yi4p6se.fsf@jonreeve.com> <831qsrn1im.fsf@gnu.org> <6fb0e08e80e292e6c7a0@heytings.org> <83edwqkqix.fsf@gnu.org> <0b2303e39221dde4f40f@heytings.org> <83y1uyj9el.fsf@gnu.org> <0b2303e39214d25ba3d3@heytings.org> <83sfl6j79y.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VFJaXJT1Il" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29098"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jonathan@jonreeve.com, 57531@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 05 15:36:55 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oVCHX-0007Kn-5i for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 05 Sep 2022 15:36:55 +0200 Original-Received: from localhost ([::1]:49754 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oVCHW-0005x0-6G for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 05 Sep 2022 09:36:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56954) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oVCEl-0002hy-1s for bug-gnu-emacs@gnu.org; Mon, 05 Sep 2022 09:34:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58140) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oVCEk-0008Gp-PV for bug-gnu-emacs@gnu.org; Mon, 05 Sep 2022 09:34:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oVCEk-0002tM-Dk for bug-gnu-emacs@gnu.org; Mon, 05 Sep 2022 09:34:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 05 Sep 2022 13:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57531 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 57531-submit@debbugs.gnu.org id=B57531.166238480411058 (code B ref 57531); Mon, 05 Sep 2022 13:34:02 +0000 Original-Received: (at 57531) by debbugs.gnu.org; 5 Sep 2022 13:33:24 +0000 Original-Received: from localhost ([127.0.0.1]:46839 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oVCE4-0002sF-5Q for submit@debbugs.gnu.org; Mon, 05 Sep 2022 09:33:24 -0400 Original-Received: from heytings.org ([95.142.160.155]:55956) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oVCDy-0002s2-NW for 57531@debbugs.gnu.org; Mon, 05 Sep 2022 09:33:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1662384793; bh=tY2xLs6huSMNm60Lk2mX88fHdYY1aH+oxYWpEj8tZjs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=rXPdc6a7BMamKSK0JVbmPLSg5IMGU+Apsnr1MtIAXRnGKiY6llgnZR879rZIHkw21 nBNI2gGRPMDE2a8u4HVs2jpl6toorSynLM1Syl2aoHoKlacDPW2torZWWn5XY6q3t1 UDsZnlPkU2dOBcEzf6D0JQnnAsRpEkni75EjNLfnMZUNZsYMDflqJtBb8dJ1arycNW KCB1zUHnNsv3jzZ0tp2hca+M8ROcgI6VwBJNsGSd0CAxOJQFnrNNUQE5RoMrl2j3x5 8ZS9NZELqi09QBwcfOW9Ew3V4JM48Ghul2cO9J3mZ9z3MR0aLfldvVr+YH5Dd2ihTg dRth95XcXGMyw== In-Reply-To: <83sfl6j79y.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:241565 Archived-At: --VFJaXJT1Il Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable >>> What would you suggest that Emacs does instead? >> >> I don't know, because anything that it could do would be backward=20 >> incompatible. > > The only change I could think of that is almost backward-compatible=20 > (except for this single locale) is the one I posted, if we modify it to= =20 > also make the 'lang-info' pseudo-encoding override the locale.alias=20 > file. > Agreed, yes. >> What is clear is that, on reasonably modern systems, legacy locales are= =20 >> not used anymore, and their use is discouraged (e.g. the Debian=20 >> installer does not present you with any legacy encoding, they remain=20 >> available but to activate them you need to edit the /etc/locale.gen=20 >> file manually). So perhaps Emacs could always assume UTF-8, and use=20 >> another encoding only when there are good reasons to do so (e.g. when=20 >> opening a file with a legacy encoding). The presence of the=20 >> equivalence eo / Latin-3 in locale.alias is IMO not a good enough=20 >> reason. > > I have no idea what this kind of change could do. > I have no idea either, I was thinking aloud. But what is clear (at least= =20 to me) is that this change is inevitable at some point. UTF-8 has been=20 the default encoding almost everywhere for two decades or so, and that's=20 unlikely to change in the forseeable future. In that world we cannot=20 continue forever to let Emacs choose another encoding based on some=20 heuristics, because "nobody" expects that anymore. Unless there's a good= =20 reason to do so, of course. > > Maybe nothing, maybe breakage across the board. Keep in mind that the=20 > default encoding is used for stuff other than decoding text in files=20 > Emacs visits, and also for some important tasks during startup. > > I also think our encoding detection doesn't always succeed to discern=20 > between UTF-8 and single-byte Latin-N encodings. > I keep all that in mind, yes =F0=9F=98=83 --VFJaXJT1Il--