unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: Use IDNA on all network connections
Date: Mon, 28 Dec 2015 17:55:13 -0800	[thread overview]
Message-ID: <5681E801.8080205@cs.ucla.edu> (raw)
In-Reply-To: <87y4cep2os.fsf@gnus.org>

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’t satisfy the Unicode Restriction Level 3 (Highly Restrictive)? The 
Unicode folks say this restriction level “will satisfy the vast majority of users”.

http://www.unicode.org/reports/tr39/#Restriction_Level_Detection

Here's a summary of what some popular browsers do:

http://www.chromium.org/developers/design-documents/idn-in-google-chrome



  reply	other threads:[~2015-12-29  1:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 13:04 Emacs Git make bootstrap failure - idna related CHENG Gao
2015-12-28 16:56 ` Lars Ingebrigtsen
2015-12-28 17:13   ` Eli Zaretskii
2015-12-28 17:16   ` Paul Eggert
2015-12-28 17:19     ` Lars Ingebrigtsen
2015-12-28 17:39   ` CHENG Gao
2015-12-28 17:43     ` Lars Ingebrigtsen
2015-12-28 18:04       ` CHENG Gao
2015-12-28 18:18   ` Lars Ingebrigtsen
2015-12-28 19:54     ` Use IDNA on all network connections Lars Ingebrigtsen
2015-12-28 23:12       ` Lars Ingebrigtsen
2015-12-28 23:34         ` Lars Ingebrigtsen
2015-12-29  1:55           ` Paul Eggert [this message]
2015-12-29  9:03             ` Lars Ingebrigtsen
2015-12-29 11:43               ` Lars Ingebrigtsen
2015-12-29 16:05                 ` Eli Zaretskii
2015-12-29 16:28                   ` Lars Ingebrigtsen
2015-12-29 16:38                     ` Eli Zaretskii
2015-12-29 16:47                       ` Lars Ingebrigtsen
2015-12-30  9:04                         ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5681E801.8080205@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).