From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master 188bd80: gnus-shorten-url: Improve and avoid args-out-of-range error Date: Tue, 14 Apr 2020 20:51:36 +0300 Message-ID: <83tv1mgdlj.fsf@gnu.org> References: <20200413102415.23314.52412@vcs0.savannah.gnu.org> <20200413102417.445E520D0C@vcs0.savannah.gnu.org> <87k12ia05d.fsf@gmail.com> <83blnui8n8.fsf@gnu.org> <878siy9rwj.fsf@gmail.com> <838siyi6gg.fsf@gnu.org> <874ktm9o0s.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="6381"; mail-complaints-to="usenet@ciao.gmane.io" Cc: handa@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Apr 14 19:52:37 2020 Return-path: Envelope-to: ged-emacs-devel@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 1jOPjg-0001YX-AX for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Apr 2020 19:52:36 +0200 Original-Received: from localhost ([::1]:36752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOPjf-0001xa-Du for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Apr 2020 13:52:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52669) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOPj2-0001Pc-Ri for emacs-devel@gnu.org; Tue, 14 Apr 2020 13:51:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46784) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jOPj2-0001dY-Hs; Tue, 14 Apr 2020 13:51:56 -0400 Original-Received: from [176.228.60.248] (port=3784 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jOPj2-0003jm-1y; Tue, 14 Apr 2020 13:51:56 -0400 In-Reply-To: <874ktm9o0s.fsf@gmail.com> (message from =?utf-8?B?xaB0xJtw?= =?utf-8?B?w6FuIE7Em21lYw==?= on Tue, 14 Apr 2020 15:48:19 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246958 Archived-At: > From: Štěpán Němec > Cc: handa@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Tue, 14 Apr 2020 15:48:19 +0200 > > On Tue, 14 Apr 2020 15:42:55 +0300 > Eli Zaretskii wrote: > > > I don't remember past discussions, > > They usually come in the form of "why are CJK misaligned in > tables/buffer list" or "how do I get wide characters exactly twice as > wide as non-wide characters, without messing up line height" etc. I think alignment on GUI frames is a separate issue, because most characters involved in this have glyphs that are neither 1 nor 2 columns, but somewhere in-between. And the only way of aligning those is by using the :align-to display spec. Unless one succeeds in finding a font that has each glyph's width to be an integral multiple of the font size. > > I think the GBK setting assumes some specific fonts to be used. Does > > anything change if you start Emacs in a GBK locale to begin with? > > I start emacs with LC_CTYPE="zh_CN.UTF-8" (which AFAIK is still the only > way to persuade it to use a system-wide input method), and in my init > file `set-language-environment' to "UTF-8". When I don't do the latter, > Emacs picks the "Chinese-GBK" environment. I hoped that using a GBK locale would somehow change the fonts being used, but maybe this no longer works on modern systems. That part of characters.el needs revisiting, the problem is that we no longer have people available who remember why this was done. Handa-san is my last hope, as I think he wrote most of that code.