From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Use IDNA on all network connections Date: Tue, 29 Dec 2015 10:03:20 +0100 Message-ID: <87mvstmxt3.fsf@gnus.org> References: <87wpryv7eu.fsf@gnus.org> <871ta6v3mo.fsf@gnus.org> <874mf2tklh.fsf_-_@gnus.org> <8760ziqiak.fsf@gnus.org> <87y4cep2os.fsf@gnus.org> <5681E801.8080205@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1451379866 5527 80.91.229.3 (29 Dec 2015 09:04:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2015 09:04:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 10:04:16 2015 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 1aDqCW-0000jd-IJ for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2015 10:04:16 +0100 Original-Received: from localhost ([::1]:47782 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDqCV-0002X4-B7 for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2015 04:04:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44665) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDqC4-0002Wt-Lq for emacs-devel@gnu.org; Tue, 29 Dec 2015 04:03:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDqC1-0006aQ-Fb for emacs-devel@gnu.org; Tue, 29 Dec 2015 04:03:48 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:59253) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDqC1-0006aH-8Q for emacs-devel@gnu.org; Tue, 29 Dec 2015 04:03:45 -0500 Original-Received: from 2.150.58.24.tmi.telenormobil.no ([2.150.58.24] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aDqBd-0007yV-HB; Tue, 29 Dec 2015 10:03:21 +0100 In-Reply-To: <5681E801.8080205@cs.ucla.edu> (Paul Eggert's message of "Mon, 28 Dec 2015 17:55:13 -0800") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1.50 (gnu/linux) X-MailScanner-ID: 1aDqBd-0007yV-HB MailScanner-NULL-Check: 1451984601.69637@Kur2zGTCE/0tzPNNW84VeQ X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 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:197071 Archived-At: Paul Eggert writes: > Lars Ingebrigtsen wrote: >> Should we do something about the Unicode homographic situation in >> relation to URLs now that we have IDNA? > > Yes, that would be good. How about if we display a URL component in > punycode if it doesn=92t satisfy the Unicode Restriction Level 3 (Highly > Restrictive)? The Unicode folks say this restriction level =93will > satisfy the vast majority of users=94. > > http://www.unicode.org/reports/tr39/#Restriction_Level_Detection ----- 3 Highly Restrictive=20 * All characters in each identifier must be from a single script, or from = the combinations:=20 * Latin + Han + Hiragana + Katakana;=20 * Latin + Han + Bopomofo; or=20 * Latin + Han + Hangul=20 * No characters in the identifier can be outside of the Identifier Profile= =20 Note that this level will satisfy the vast majority of users.=20 ----- That seems like a sensible restriction. But when Emacs detects an URL, should it punify the URL (for display purposes) (if it doesn't satisfy "Highly Restrictive"), or should it just ... do something when the user tries to act on the URL? > Here's a summary of what some popular browsers do: > > http://www.chromium.org/developers/design-documents/idn-in-google-chrome For eww, I think Firefox' solution sounds nice: Display the punycode version if the domain name doesn't satisfy "Highly Restrictive"... --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no