From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Garreau\, Alexandre" Newsgroups: gmane.emacs.devel Subject: Unicode security-issues workarounds elsewhere [Was: Re: Change of Lisp syntax for "fancy" quotes in Emacs 27?] Date: Sat, 06 Oct 2018 15:15:34 +0200 Message-ID: <2ca8cxzzzzzz.bq7.xxuns.g6.gal_-_@portable.galex-713.eu> References: <83y3bc2378.fsf@gnu.org> <4fjg1zzzzzzz.3lf.xxuns.g6.gal@portable.galex-713.eu> <83h8hz1eg1.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1538831683 13834 195.159.176.226 (6 Oct 2018 13:14:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 6 Oct 2018 13:14:43 +0000 (UTC) User-Agent: Gnus (5.13), GNU Emacs 25.1.1 (i686-pc-linux-gnu) Cc: npostavs@users.sourceforge.net, eggert@cs.ucla.edu, drew.adams@oracle.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 06 15:14:38 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g8mPm-0003Ti-5D for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 15:14:38 +0200 Original-Received: from localhost ([::1]:39236 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8mRs-0005mB-GC for ged-emacs-devel@m.gmane.org; Sat, 06 Oct 2018 09:16:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:32952) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8mR5-0005m4-Pe for emacs-devel@gnu.org; Sat, 06 Oct 2018 09:16:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8mR4-0001IH-Qq for emacs-devel@gnu.org; Sat, 06 Oct 2018 09:15:59 -0400 Original-Received: from portable.galex-713.eu ([2a00:5884:8305::1]:50156) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1g8mQu-0001AF-J8; Sat, 06 Oct 2018 09:15:58 -0400 Original-Received: from localhost ([::1] helo=portable.galex-713.eu) by portable.galex-713.eu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8mQg-000693-DS; Sat, 06 Oct 2018 15:15:35 +0200 X-GPG-FINGERPRINT: E109 9988 4197 D7CB B0BC 5C23 8DEB 24BA 867D 3F7F X-Accept-Language: fr, en, it, eo In-Reply-To: <83h8hz1eg1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Oct 2018 14:50:54 +0300") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:5884:8305::1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:230252 Archived-At: Le 06/10/2018 =C3=A0 14h50, Eli Zaretskii a =C3=A9crit=C2=A0: >> From: "Garreau\, Alexandre" >> Cc: Eli Zaretskii , emacs-devel@gnu.org, >> drew.adams@oracle.com, npostavs@users.sourceforge.net >> Date: Sat, 06 Oct 2018 13:22:14 +0200 >>=20 >> In a world where unicode is increasingly present and confusion about its >> characters increasingly problematic (typosquatting, etc.) wouldn=E2=80= =99t it be >> reasonable to expect unicode-related semantic functions to be provided >> in most frameworks, systems and languages to allow better handling of >> such problems, thus making that problem the interface=E2=80=99s one? > > I don't think I understand what this means in practice; please > elaborate. The point I wanted to make is since as I highlighted this problem is of greater importance in other interfaces than source codes, especially browsers and web sites, typically, as these gets to be the most used interfaces for everything nowadays. So I guess these unicode anti-confusion functions and more high-level functions based on these already are or will become present in browsers and in languages such as perl and php to end up in high-level functions in frameworks made in perl or php, for instance, so that at the end =E2=80=9Cother interfaces than emacs=E2=80=9D such as web-browsers or websites may end supporting features= such as coloring differently mixed-script or unusual spaces, etc. The other option being =E2=80=9Cban unicode as much as possible=E2=80=9D or= =E2=80=9Cdisallow mixed-script=E2=80=9D, and =E2=80=9Cban all unicode punctuation characters = (or all non-letters (or non-alphanumeric?) characters, or something like that) unless they=E2=80=99re inside ascii=E2=80=9D. I believe with increased support of unicode most languages, frameworks and software should end with features allowing to allow these without creating too much problems (at least not that much a lot more than in emacs).