From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Can watermarking Unicode text using invisible differences sneak through Emacs, or can Emacs detect it? Date: Fri, 18 Feb 2022 23:54:42 -0500 Message-ID: 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> <83o83wc7gs.fsf@gnu.org> <8335l5brov.fsf@gnu.org> <83mtjc838i.fsf@gnu.org> <83zgna7hyd.fsf@gnu.org> <83ee4l78rw.fsf@gnu.org> <83tudf2h4z.fsf@gnu.org> <83sfswz834.fsf@gnu.org> <83leymyfz8.fsf@gnu.org> <83sfstwnve.fsf@gnu.org> <83v8xoup27.fsf@gnu.org> <835ypnutj8.fsf@gnu.org> <83ee48sfhp.fsf@gnu.org> <83pmnpps75.fsf@gnu.org> <83a6es45nz.fsf@gnu.org> <83iltf2esj.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28688"; mail-complaints-to="usenet@ciao.gmane.io" Cc: psainty@orcon.net.nz, luangruo@yahoo.com, emacs-devel@gnu.org, kevin.legouguec@gmail.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 19 05:56:33 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 1nLHnN-0007IX-8z for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Feb 2022 05:56:33 +0100 Original-Received: from localhost ([::1]:45120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nLHnM-0004AM-4O for ged-emacs-devel@m.gmane-mx.org; Fri, 18 Feb 2022 23:56:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:52446) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nLHla-0002nE-UA for emacs-devel@gnu.org; Fri, 18 Feb 2022 23:54:42 -0500 Original-Received: from [2001:470:142:3::e] (port=47062 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 1nLHla-0002xw-En; Fri, 18 Feb 2022 23:54:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=yj18TrwwOCl7sBdfUqaAGwU0Phl77uLL6Ze8zEoyETU=; b=fSrHoUL5VYt7 lDZaqDdrd8c9/4emBPjMlqOw7SD3Q0XAdx0sfsiGF9P83J9Er6z5fIs+rmtNDev2Bf4sfc9twIjby xpB3iFxOoLjnKIQk8OwA/HuyPFbWmOpRmhoj5FLJBp67NXHCG3DTfoCfHXcHnykgBoAISnIjBb9yN b0zoaC1BfJ8gAc6LNW1Jw1jSAy+Y7tHBcm5FJZPWcLSJKObXD8eLpgXFpN3vAhrqU00XICc/VBEa0 nFTdprTGM5XPrtbqBaUb+Zt4bhbtueuXgn372esLBcaR/5EYX68CNE2ZMLsSnBOl3Vq92vfkuI0U0 3Dl5VBlJMVoVDpfqD4jvsQ==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1nLHla-0004nr-5i; Fri, 18 Feb 2022 23:54:42 -0500 In-Reply-To: <83iltf2esj.fsf@gnu.org> (message from Eli Zaretskii on Wed, 16 Feb 2022 14:10:04 +0200) 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:286448 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Following this rule, Emacs would display ă~, if the terminal can handle that, > > otherwise a˘~ . > But in that case, it goes against the spirit of this feature, which > expresses non-ASCII characters with equivalent strings composed of > ASCII characters. Since ˘ is non-ASCII, chances are that the terminal > which cannot display ă will be unable to display ˘ as well. That's a valid point: on a terminal which can't display the BREVE character, this method would not work. There could be an additional fallback method of using `(' instead of BREVE. I can't think of any other ASCII character that would be better than that one. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)