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: Can watermarking Unicode text using invisible differences sneak through Emacs, or can Emacs detect it? Date: Fri, 28 Jan 2022 15:31:31 +0200 Message-ID: <83o83wc7gs.fsf@gnu.org> References: <87sftk49ih.fsf@yahoo.com> <837dawt0h4.fsf@gnu.org> <838rv9plyf.fsf@gnu.org> <837dasntoj.fsf@gnu.org> <834k5tl4a9.fsf@gnu.org> <87mtjkt6m9.fsf@gmail.com> <83ilu8htws.fsf@gnu.org> <3E718CA2-889F-4AEE-B79C-EB3A221D1CB2@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13416"; mail-complaints-to="usenet@ciao.gmane.io" Cc: psainty@orcon.net.nz, luangruo@yahoo.com, kevin.legouguec@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 28 15:23:37 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 1nDSA4-0003Fy-1S for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Jan 2022 15:23:36 +0100 Original-Received: from localhost ([::1]:45590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nDSA2-0006Et-S0 for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Jan 2022 09:23:34 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:52262) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDRM3-0006E8-18 for emacs-devel@gnu.org; Fri, 28 Jan 2022 08:31:57 -0500 Original-Received: from [2001:470:142:3::e] (port=51008 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 1nDRM1-00030K-VO; Fri, 28 Jan 2022 08:31:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=XfFA93+iHLMLSzf5fdUZcUI9XmfuulAuSqEhZaJJuGQ=; b=VZ2D+O29kUPxWgNxuTw2 EIrm9ilq84DdBHSDfTD5Xd1zOMq1MY+meTS7bM6SXipv3FTtrreug8qijcP7zAxHtCqssMMNuikCX OuxT9jJGfwwKZokHbxyt7nlaNbHTVM70HUdgszE7EZBAkI55sgpcyMB/qfEDm4Vk7gFqpbyUfAvN1 OTKwXQYsVzmtELs2GABFXbiq3ri05uQgOSeroyA4JGtSGZBqB9t9TMJyE7eEZ0izOuMaQjDU3Yy5C BrJfchKQdGZ7rJCmofNbU1vY54g15CMKKRNnOZ8qTtIVjP7onUaf91t3bVBAz9K98mmPfhvR13AO4 Q9loMJiiRvLuHw==; Original-Received: from [87.69.77.57] (port=3157 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 1nDRLi-0002Kl-Ra; Fri, 28 Jan 2022 08:31:37 -0500 In-Reply-To: (message from Richard Stallman on Fri, 28 Jan 2022 08:04:49 -0500) 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:285514 Archived-At: > From: Richard Stallman > Cc: psainty@orcon.net.nz, luangruo@yahoo.com, emacs-devel@gnu.org, > kevin.legouguec@gmail.com > Date: Fri, 28 Jan 2022 08:04:49 -0500 > > > The most widely known example is Latin characters with diacritics, such as ç and à. > > Since my terminal handles many of those characters, they work ok for > me. But there are some it does not support. Many Vietnamese > characters, for instance. > > If this feature is implemented to handle ligatures, it could handle > the letters with diacritics too. That would be as easy as populating > the table of the sequences they stand for. IIUC what you mean by "this feature", we already have that in latin1-disp.el. It just isn't automatic, because most terminals and terminal emulators don't have a way of reporting which sequences they are capable of composing. So we let it to the users to determine whether they need this kind of "ASCII-fied" display. I asked whether adding a command that specifically targets ligatures like "fi" would be useful -- can you answer that? > The terminfo item for `linux' could indicate which characters are ok > to display unchanged and which ones need to be displayed as the > equivalent digraphs (or trigraphs). Given the enormously large number of such sequences, I doubt that terminfo is the right means for determining which sequences are supported. We have a solution for the Linux console, and for the rest we allow the user to customize the value of auto-composition-mode to disable it if the terminal misbehaves with these sequences.