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, 04 Feb 2022 10:10:57 +0200 Message-ID: <83r18j2gry.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> <83o83wc7gs.fsf@gnu.org> <8335l5brov.fsf@gnu.org> <83mtjc838i.fsf@gnu.org> <83zgna7hyd.fsf@gnu.org> <83ee4l78rw.fsf@gnu.org> <837dac5qth.fsf@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="38674"; 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 Feb 04 09:59:12 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 1nFuQx-0009rZ-CS for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Feb 2022 09:59:11 +0100 Original-Received: from localhost ([::1]:49398 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nFuQw-0006zk-3p for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Feb 2022 03:59:10 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44954) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFtgH-0001tp-DE for emacs-devel@gnu.org; Fri, 04 Feb 2022 03:10:58 -0500 Original-Received: from [2001:470:142:3::e] (port=44090 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 1nFtgG-0003pk-VO; Fri, 04 Feb 2022 03:10:57 -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=FsW/hy9+iNkY64H4hjP36X5FKwPmqE59EceApEobB70=; b=AcY7S8dwODFg5JLtIxpB pygxEhQfAgCrlKBPaNJNCnNJD0MAd2W6MzgopAiX1bNz9KY27wyKwkJBmC+PFbswFWMk0TRtNXpU8 vLMlAlpjno1QTwg/KEusP0VbIRCK35BS89FM7/hfWxPOICs+/2XyoOnUtBlKkmeSgMI+WvThanhHA 2vDvYkrnZ7/WFmZJ9f5R6kpak/lOMJl4jbmvQjHjMDcpWVHaHmlTBGH5rfr4/JEBzJYYmbOwR79mY 1+WNxn8cdGQjg6e02FEc9hObo+a2BYjiDY/tm6vLwhuqVoLviQ5qENTgbhSTK1rh9yYn9GkxUgMsO zxsIH0cHbacksw==; Original-Received: from [87.69.77.57] (port=1097 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 1nFtgA-0001Ua-Dh; Fri, 04 Feb 2022 03:10:51 -0500 In-Reply-To: (message from Richard Stallman on Thu, 03 Feb 2022 22:52:16 -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:285857 Archived-At: > From: Richard Stallman > Cc: psainty@orcon.net.nz, luangruo@yahoo.com, emacs-devel@gnu.org, > kevin.legouguec@gmail.com > Date: Thu, 03 Feb 2022 22:52:16 -0500 > > > > Then the natural visual representations would be ă~ (a with breve, > > > then tilde) and ã˘ (a with tilde, then breve), > > > Either one would be fine, but the former is better, I think, since ~ > > is an ASCII character, and so is universally supported. > > That's a good point, but Yuri Khan said: > > > The ordering of diacritics on the same side of the base character is > > considered significant in Unicode, so ă~ and ã˘ would be > > representations of different grapheme clusters — “a with breve and > > tilde” and “a with tilde and breve”, respectively. That's a tangent, not directly relevant to the issue at hand. If/when we bump into different characters that differ only by the order of the diacriticals, we will resolve each such case one by one.