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.devel Subject: Re: bidi-string-strip-control-characters Date: Thu, 20 Jan 2022 13:33:20 +0200 Message-ID: <8335lir69r.fsf@gnu.org> References: <83ee52rcar.fsf@gnu.org> <8735li69hl.fsf@gnus.org> <87pmom1xdy.fsf@yahoo.com> <835yqer6w1.fsf@gnu.org> <87v8ye1wif.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24099"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 20 16:14:48 2022 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 1nAZ9A-0005xK-Ur for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jan 2022 16:14:45 +0100 Original-Received: from localhost ([::1]:48410 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nAZ99-0005xR-BM for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Jan 2022 10:14:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:54732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nAVhL-0006b2-0h for emacs-devel@gnu.org; Thu, 20 Jan 2022 06:33:47 -0500 Original-Received: from [2001:470:142:3::e] (port=39298 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nAVgw-000891-Cg; Thu, 20 Jan 2022 06:33:46 -0500 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=4vat7DxrwUg01H2cuAmK41oFh6hEKflHBXDeWKJTeWU=; b=c2jVwlWH8i+K Tx5uHQCpA/rhvJpbjq6CRaiDA99KGnqi+389nkLyuD7dwr5QjJiHlcIuNGI/bOCeXO4IW+qND/AWa ys7Rv+37HoypYQTaJkO+xyctDxflGNRyBo3136NoxmLaXz/meCp2hCiCl9Pkid9wbMkxrYTWOTrZf dkh+BgVNZqs+GkBDTpsAUEuffw6CiTk8OchcI9k3drhOjcRd3munBoUd6ZiULLyt6TOM9aC4IW4RK C3OgpQcj5yxpVtiDs9OXhvv8dJlvoGxmmN2kcGYyLvJAgy3TJS2bmAAEQOhKshq1AIpVnzTodQwaA zwjkGd4baylMb12vxVM8ow==; Original-Received: from [87.69.77.57] (port=4969 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 1nAVgw-00044I-Ei; Thu, 20 Jan 2022 06:33:22 -0500 In-Reply-To: <87v8ye1wif.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 20 Jan 2022 12:23:20 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:285041 Archived-At: > From: Lars Ingebrigtsen > Cc: Po Lu , emacs-devel@gnu.org > Date: Thu, 20 Jan 2022 12:23:20 +0100 > > Eli Zaretskii writes: > > >> "Disallowed character: #x202e, RIGHT-TO-LEFT OVERRIDE" > > > > What is "this case" in this context? IOW, under what conditions do > > you suggest to omit the character itself? > > I think it makes sense to change the display to what Po Lu suggested > when the char is glyphless. That'd be fine by me for this particular use case. But what are we going to do with the function in the Subject? Is it still useful enough to have it, if we make that change?