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: Unicode confusables and reordering characters considered harmful Date: Wed, 10 Nov 2021 19:03:18 +0200 Message-ID: <83lf1w2bah.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10545"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, mail@vasilij.de To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 10 18:09:39 2021 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 1mkr6Q-0002Z7-V2 for ged-emacs-devel@m.gmane-mx.org; Wed, 10 Nov 2021 18:09:39 +0100 Original-Received: from localhost ([::1]:47382 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mkr6P-0002pQ-To for ged-emacs-devel@m.gmane-mx.org; Wed, 10 Nov 2021 12:09:37 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37064) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mkr0P-0003df-UH for emacs-devel@gnu.org; Wed, 10 Nov 2021 12:03:25 -0500 Original-Received: from [2001:470:142:3::e] (port=39920 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 1mkr0O-0001gX-AB; Wed, 10 Nov 2021 12:03:24 -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=/dDCXPjeXxr1Z1xuELWgS35QpYu/ACTviJLGcXpCI24=; b=sgIb4ZU5tqeA q4PWFrqxTQfgwig6lWNrDr0+vrrdup1xvZr2lg9KXv1+o8l6c/19nq2xotVA1PuRAuxmg3PiAv9jp /dG+EBA+D5byuhacnG3CUFCJvIRpcylJAV/12cms1FF+vZOQ+wSBUS0s41VaNAdv1u4d1tQwvPuAn 8oi/Dl4415zUQ83LedYhZ6OhW3M2cRa7bf0GpEBeLdm3bjYIgYITMDG/he2J5MTmv4DYLYRjOSikS t9OjFMbBb52fkvtIPnnFrNknpAsDuM9Ka53A/zJKXPkMUqX8sRwqJGboSZ+h0uOOy17k6QhWTRlq2 wQuGznwQUBw1dQj6uT+26w==; Original-Received: from [87.69.77.57] (port=4310 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 1mkr0N-0003kH-Tt; Wed, 10 Nov 2021 12:03:24 -0500 In-Reply-To: (message from Dmitry Gutov on Wed, 10 Nov 2021 18:47:12 +0300) 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:279180 Archived-At: > From: Dmitry Gutov > Date: Wed, 10 Nov 2021 18:47:12 +0300 > > Here's also an article from yesterday focusing on _invisible_ characters: > > https://certitude.consulting/blog/en/invisible-backdoor/ First, that character (U+3164) is not invisible in Emacs: it displays as a very wide space, so should probably stand out even if not specifically highlighted. And second, UTS #39 covers such characters as well. So if we implement some of the recommendations there, we will flag this case as well. But yes, this is one more case we should be able to handle.