From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#57531: 28.1; Character encoding missing for "eo" Date: Tue, 04 Oct 2022 15:39:18 +0300 Message-ID: <83r0znvk3t.fsf@gnu.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> <875yi31v17.fsf@linux-m68k.org> <83v8q3li60.fsf@gnu.org> <87wnajzj6z.fsf@linux-m68k.org> <83tu5nlgyy.fsf@gnu.org> <83r10rlf1l.fsf@gnu.org> <877d1fak51.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22218"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jonathan@jonreeve.com, 57531@debbugs.gnu.org, schwab@linux-m68k.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 04 15:06:09 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 1ofhcd-0005VW-GO for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Oct 2022 15:06:07 +0200 Original-Received: from localhost ([::1]:38658 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofhcc-0002Gg-2f for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Oct 2022 09:06:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50502) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhDO-0000wz-Au for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 08:40:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53779) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ofhDN-0006VO-WB for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 08:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ofhDN-0000wv-JA for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 08:40:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 04 Oct 2022 12:40:01 +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.16648871753610 (code B ref 57531); Tue, 04 Oct 2022 12:40:01 +0000 Original-Received: (at 57531) by debbugs.gnu.org; 4 Oct 2022 12:39:35 +0000 Original-Received: from localhost ([127.0.0.1]:52857 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofhCx-0000wA-6v for submit@debbugs.gnu.org; Tue, 04 Oct 2022 08:39:35 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:57304) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofhCs-0000vv-G7 for 57531@debbugs.gnu.org; Tue, 04 Oct 2022 08:39:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49510) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhCm-0006Mg-Bg; Tue, 04 Oct 2022 08:39:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=S9BB8VC38RlJ+/PFAKZfA0VpO5fGUK4bWRgrKVejKdw=; b=R/w3o5XAX3Or Qfh+AedCKWsZN1H63v7TiiIWR/+h7XhKFfeydoUlwDy7IQ1TAiXZ+vfDYFwJkrM/oy4gXD4mz68HM 3RJg8HHpyl07JbReUZZ228XimobMe1ysBm0gTbxwH+1qTrmvczjKL4d98BtYUDyVWwu6FcFguJRgG 9CoHpjTYfofSk1oXYjEufAj1/PYymWGipzIpP7cfCPRjpiUjl6YsvJHP8nRapL+I5t8zZbYI6KG1u T8eAEXiG6G/ekeEJfbq3qW5wURpCYl7x6M56oEAyCXFaao0vK/jB07UgACwZVhnPgh2k00MYEWBd/ N2OD52S12lMPrMmD0Kp+CA==; Original-Received: from [87.69.77.57] (port=4753 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhCl-0006SY-JR; Tue, 04 Oct 2022 08:39:23 -0400 In-Reply-To: <877d1fak51.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 04 Oct 2022 13:44:10 +0200) 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:244425 Archived-At: > From: Lars Ingebrigtsen > Cc: jonathan@jonreeve.com, 57531@debbugs.gnu.org, schwab@linux-m68k.org > Date: Tue, 04 Oct 2022 13:44:10 +0200 > > Eli Zaretskii writes: > > > Something like the below could be acceptable, if it solves the > > problem. > > > > diff --git a/lisp/international/mule-cmds.el b/lisp/international/mule-cmds.el > > index 4137642..6866291 100644 > > --- a/lisp/international/mule-cmds.el > > +++ b/lisp/international/mule-cmds.el > > @@ -2317,7 +2317,7 @@ locale-language-names > > ;; en_IN -- fx. > > ("en_IN" "English" utf-8) ; glibc uses utf-8 for English in India > > ("en" "English" iso-8859-1) ; English > > - ("eo" . "Esperanto") ; Esperanto > > + ("eo" "Esperanto" locale-info) ; Esperanto > > (etc). This does not seem to fix the problem. It won't solve the problem if you have that X11 file on your system, because we read it before we get to the code I changed. > This does work (with or without the patch): > > LANG=eo.UTF-8 ./src/emacs -Q > current-locale-environment > "eo.UTF-8" But it requires the eo.UTF-8 locale to be available, AFAIU, and for that reason somehow didn't work for the OP. I don't think I understood why it didn't work for him. I still hope the OP will come back and help us understand that. > 1) The "eo" environment should be in utf-8 -- all the indications seem > to point to that, except some outdated Debian files that nobody else > uses but Emacs. > > 2) Using eo.UTF-8 is a work-around that works fine. > > 3) Changing what Emacs does here might be disruptive to people that are > used to Emacs defaulting to Latin-3 for the "eo" locale. > > So the question is whether Emacs should start doing the right thing as > 1), or worry more about 3). > > I'm leaning more towards 1), but I don't have a strong opinion. If we think 2) will work for (almost) everyone, maybe the problem is not serious enough to have to decide between two extremes?