From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Bidirectional text and URLs Date: Sun, 30 Nov 2014 17:16:06 +0200 Message-ID: <83fvd0afd5.fsf@gnu.org> References: <83zjbbkwnj.fsf@gnu.org> <834mtiaqcv.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1417360596 13478 80.91.229.3 (30 Nov 2014 15:16:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 30 Nov 2014 15:16:36 +0000 (UTC) Cc: larsi@gnus.org, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 30 16:16:29 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xv6Ef-0003rl-38 for ged-emacs-devel@m.gmane.org; Sun, 30 Nov 2014 16:16:29 +0100 Original-Received: from localhost ([::1]:50710 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xv6Ee-0003US-Ll for ged-emacs-devel@m.gmane.org; Sun, 30 Nov 2014 10:16:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xv6EM-0003SY-GS for emacs-devel@gnu.org; Sun, 30 Nov 2014 10:16:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xv6EG-0000TZ-LX for emacs-devel@gnu.org; Sun, 30 Nov 2014 10:16:10 -0500 Original-Received: from mtaout26.012.net.il ([80.179.55.182]:54054) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xv6EG-0000TL-DQ; Sun, 30 Nov 2014 10:16:04 -0500 Original-Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0NFU00J00YCO2400@mtaout26.012.net.il>; Sun, 30 Nov 2014 17:14:48 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NFU00G4HYCONX20@mtaout26.012.net.il>; Sun, 30 Nov 2014 17:14:48 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:178516 Archived-At: > Date: Sun, 30 Nov 2014 04:37:42 -0500 > From: Richard Stallman > CC: larsi@gnus.org, emacs-devel@gnu.org > > > > We seem to be talking about different questions. > > > You're talking about "some...text" but the question was specifically URLs. > > > URLs are a special case of human-readable text. > > Yes, but that's not the point. The point is that your special cases > > The places where bidi characters should work are human-readable text. > > don't overlap with URLs. My conclusion is the opposite: This issue happens _precisely_ _because_ humans review the URLs presented to them before they decide to follow the link to those URLs. The issue here is that bidirectional display features are being (ab)used to trick humans into thinking they will follow a link to some place, while in fact the link leads to a very different place. This problem would not have existed without humans reading the URLs, and without the discrepancy between what those humans perceive visually and the actual URL as seen by the program which interprets it. A program always reads and processes a URL in the logical order of its characters, i.e. in the strictly increasing order of the character positions in the string, so a program will never see any strangeness here.