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: idn.el and confusables.txt Date: Mon, 16 May 2011 15:38:38 +0300 Message-ID: <83ei3yhlbl.fsf@gnu.org> References: <87fwpba03q.fsf@lifelogs.com> <874o5rqr5z.fsf@lifelogs.com> <87mxjjpal4.fsf@lifelogs.com> <87vcy6nzan.fsf@lifelogs.com> <87tydl4sjj.fsf_-_@lifelogs.com> <87r58pghh7.fsf_-_@lifelogs.com> <83iptdg0yr.fsf@gnu.org> <87y629ien3.fsf@lifelogs.com> <83aaepfiuk.fsf@gnu.org> <87aaepi9k2.fsf@lifelogs.com> <834o4xfd34.fsf@gnu.org> <8739khi54z.fsf@lifelogs.com> <83y629dmmt.fsf@gnu.org> <8739kg7o63.fsf@lifelogs.com> <87hb8w5few.fsf@lifelogs.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1305549582 19488 80.91.229.12 (16 May 2011 12:39:42 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 16 May 2011 12:39:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 16 14:39:37 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QLx5F-0001NS-2c for ged-emacs-devel@m.gmane.org; Mon, 16 May 2011 14:39:37 +0200 Original-Received: from localhost ([::1]:34824 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QLx5E-00050F-Iy for ged-emacs-devel@m.gmane.org; Mon, 16 May 2011 08:39:36 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47478) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QLx5C-000506-1b for emacs-devel@gnu.org; Mon, 16 May 2011 08:39:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QLx5A-0003w1-Ik for emacs-devel@gnu.org; Mon, 16 May 2011 08:39:34 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:54782) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QLx5A-0003vh-C0 for emacs-devel@gnu.org; Mon, 16 May 2011 08:39:32 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0LLA00L00G029200@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Mon, 16 May 2011 15:38:40 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.228.84.222]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LLA00JKAGGF42H0@a-mtaout22.012.net.il>; Mon, 16 May 2011 15:38:40 +0300 (IDT) In-reply-to: <87hb8w5few.fsf@lifelogs.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.172 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:139422 Archived-At: > From: Ted Zlatanov > Date: Sun, 15 May 2011 07:14:47 -0500 > > EZ> If we were to implement the full IDNA protocol, would the above be > EZ> enough? Or will we need additional information? > > Oh, all this has been for confusables (TR39) only. IDNA and uni-idn.el > will have their own needs! Granted, but I was asking whether IDNA implementation will need anything from confusables.txt beyond what we discussed. That is, will a mapping of a character to a string be all IDNA needs to use the information in confusables.txt? > IDNA is better described in http://unicode.org/reports/tr46/ and the > links at the end of that document (a whole bunch of RFCs). I'm not > interested in implementing the IDNA code beyond supporting the current > character set detection because I don't think IDNA is popular enough, > but maybe Lennart and others want to do it. > > For further possible markchars.el functionality, take a look at > http://www.unicode.org/reports/tr36/ (Unicode Security Considerations). > It talks about the confusables issues, IDNA issues, and bidi issues > among others. It's a really good explanation of what security-related > functionality is needed from the confusables char-table and potentially > other places in Emacs. Yes, I'm familiar with these specs, but I didn't try to design an implementation of IDNA, so the answers to the above questions are not clear to me. If someone can explain how would an IDNA implementation use confusables.txt, we could make sure that the tables we produce from it will be good for IDNA as well, if and when someone will want to implement it.