From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#57531: 28.1; Character encoding missing for "eo" Date: Tue, 04 Oct 2022 15:13:15 +0200 Message-ID: <87tu4j7mvo.fsf@gnus.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> <83r0znvk3t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16371"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: jonathan@jonreeve.com, 57531@debbugs.gnu.org, schwab@linux-m68k.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 04 15:59:30 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 1ofiSH-00040t-Pm for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Oct 2022 15:59:29 +0200 Original-Received: from localhost ([::1]:41972 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofiSG-0005Ga-OW for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 04 Oct 2022 09:59:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofhkI-00045M-Qa for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 09:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53840) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ofhkI-0000wo-H3 for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 09:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ofhkI-000415-9s for bug-gnu-emacs@gnu.org; Tue, 04 Oct 2022 09:14:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 04 Oct 2022 13:14: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.166488921015394 (code B ref 57531); Tue, 04 Oct 2022 13:14:02 +0000 Original-Received: (at 57531) by debbugs.gnu.org; 4 Oct 2022 13:13:30 +0000 Original-Received: from localhost ([127.0.0.1]:52918 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofhjm-00040E-FP for submit@debbugs.gnu.org; Tue, 04 Oct 2022 09:13:30 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:46112) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofhji-0003zy-4O for 57531@debbugs.gnu.org; Tue, 04 Oct 2022 09:13:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=9vLOPg2n+autUDL1CQB1UZxX32IMcjj5ZI+t3TXXzX4=; b=nIhcNLbH4fTT2NhiecDoSOlZhn NOo6cqrWGAtaKGzpnbcmPrjzectYBePk8pBknKgNPhIBY08fcRin5J1fiE68aDaiMI/Lj+BKaYn9S VrlK1C9o0RH6+k4VsSUU4TfIyexZOk+8Lf2pZgbURtcVMnJcUeE1SWHDvlI23v5uygx0=; Original-Received: from [84.212.220.105] (helo=downe) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ofhjY-00046S-AQ; Tue, 04 Oct 2022 15:13:18 +0200 In-Reply-To: <83r0znvk3t.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 04 Oct 2022 15:39:18 +0300") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAG1BMVEXv6NT9/e+HhXcX FxElJBouLCG5taVXVUj///8fCikEAAAAAWJLR0QIht6VegAAAAd0SU1FB+YKBA0KCDX3LiIAAAG2 SURBVDjLddNLc5swEABgMROTK/SgXIOTmGunK8G1E4nk6lQoXKNkKl9LDPXfr15gGdK9eLyftIte CIVI7rgN2XIAhZBGKA8hbJ5wB7mBJOQxJwCk5aP5URl6n+EINmQjGwvpDBgCcFOqQGf4RhyQtjHQ I72d4AamKRJgj/TcfOPzrJMM4E8EHxNwB3ZhHq48NJ1gtscZfCnyLG2pwiz7EugopTBgEosZshtM ExXBtV0HIUPT0hhw2foZJ8HslgRI9V1YHtDWjkg8vAuYg8hhgrSM0pxRs8vEQTTcbeLIoHMAbM7S z20p/97Tnf0exKLhCo9Sj3u1BOgP5W1ZurwpNUUtoErS7E37FZ9n1NsjTUzbZAVvG6rzOaJS6FBt dvOtiSAd+uvhl1rB429RYK3WpT5Fo3KF1tCS2vw/rQGgMufljnUJ+wwLVn0BfX5FgCYrqG/zo7kJ Lwtg9SvGodMFdFSjBzdxAa+HXeZOMzQJm0gfHnN049/IxXn8xKdkuvEqntHnmyK8trDEAC/58Hwf Pq+IS30Pb9DCRY/qA74Ger4sPFntVRjzP5hWzpbww+UzxJfw5OEfjADE7Pdo8nMAAAAldEVYdGRh dGU6Y3JlYXRlADIwMjItMTAtMDRUMTM6MTA6MDgrMDA6MDBBPsSsAAAAJXRFWHRkYXRlOm1vZGlm eQAyMDIyLTEwLTA0VDEzOjEwOjA4KzAwOjAwMGN8EAAAAABJRU5ErkJggg== X-Now-Playing: New Order's _Low Life_: "track" 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:244431 Archived-At: Eli Zaretskii writes: > 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. Ah, right. >> 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. Yes, that would be helpful. On this Ubuntu system, I just uncommented the "eo" line in locale.gen and ran locale-gen, and that made both the "eo" and "eo.UTF-8" locales available. > If we think 2) will work for (almost) everyone, maybe the problem is > not serious enough to have to decide between two extremes? Yes, that's quite possible. But this might also be an opportunity to stop parsing that apparently outdated file X11 file completely...