From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Zhu Zihao Newsgroups: gmane.emacs.devel Subject: Re: Current master d5622eb6ff, font display issue. Date: Thu, 08 Aug 2019 22:30:56 +0800 Message-ID: <87y303sp9b.wl-all_but_last@163.com> References: <8736ict25t.wl-all_but_last@163.com> <838ss3bwld.fsf@gnu.org> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-2022-JP Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="184354"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/27.0 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Cc: Zhu Zihao , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 08 16:31:24 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hvjRs-000lqc-4Z for ged-emacs-devel@m.gmane.org; Thu, 08 Aug 2019 16:31:24 +0200 Original-Received: from localhost ([::1]:52240 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvjRr-0004EW-6v for ged-emacs-devel@m.gmane.org; Thu, 08 Aug 2019 10:31:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55995) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hvjRm-0004EN-TU for emacs-devel@gnu.org; Thu, 08 Aug 2019 10:31:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hvjRl-0001yb-W5 for emacs-devel@gnu.org; Thu, 08 Aug 2019 10:31:18 -0400 Original-Received: from m12-17.163.com ([220.181.12.17]:58250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hvjRi-0001kM-SQ; Thu, 08 Aug 2019 10:31:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:Message-ID:From:Subject:MIME-Version; bh=lNxTF ZXuFAu4O3ORbrxqN5UYUaoyfyc9bqT4//EsqFs=; b=k3av+cVsxGeFMyAgBDUaR Qze3SSRfLvs+lj3acx921WsRNAvr4Y7/r0O9KIrT+dUkaAnXRHb7BH3us1UHFmHw Sfh0hwzo0iiNUSvNTOo5PZywJ6v46119KXw9hN08sixomGANyMrt5zlrmuyp9Mvk U9gQMRCVVGzIOo4T3XB9mw= Original-Received: from archlinux.163.com (unknown [113.100.121.27]) by smtp13 (Coremail) with SMTP id EcCowAA3cvMgMkxdY4txHA--.37616S2; Thu, 08 Aug 2019 22:30:59 +0800 (CST) In-Reply-To: <838ss3bwld.fsf@gnu.org> X-Face: :]]%@R1{oDt0%iKgI@Kga#OZ; ogt+%OOne&J4#E*O,TIlI)yEFw--I\:3s~EV97GI$1.1!}8inmF9UgtUBB@#8>'8NWNC8qg/v*OLfQB; Z:@G3HeNf3u& ,&HpBGv%?p{bzsl'|5T";1&X X-CM-TRANSID: EcCowAA3cvMgMkxdY4txHA--.37616S2 X-Coremail-Antispam: 1Uf129KBjvdXoW7Jr1fZryrWr47tF4UZFy7KFg_yoW3GrXE9F yYyFsxC34UXFyUXFs2vwsavF1v9r1Utr1Uuw1UZrs2kF1ay34FgFs5urs8u3WSqF4YgwnI 9Fn0v3WDtr9rGjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7sRv38b5UUUUU== X-Originating-IP: [113.100.121.27] X-CM-SenderInfo: pdoosuxxwbztlvw6il2tof0z/xtbBoQMLr1QHGa1dIgAAse X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 220.181.12.17 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:239252 Archived-At: On Thu, 08 Aug 2019 21:44:30 +0800, Eli Zaretskii wrote: > > > Date: Thu, 08 Aug 2019 17:52:14 +0800 > > From: Zhu Zihao > > Cc: eliz@gnu.org > > > > I'm using Sarasa Gothic Mono font, which force a CJK character has equivalent > > width with 2 latin character. But in commit d5622eb6ff, A table seems to have > > misalignment issue. > > > > For example, check this table generated by org in Emacs. > > > > | English | 中文 | | | | > > |---------+------+---+---+---| > > | | | | | | > > Are you saying that this used to work OK for you, and now it doesn't? > If so, can you please bisect to find the offending commit? > I'm sure that Emacs 26.2 didn't have this issue, I'll try to find which commit introduced the issue, but it may take some time.