unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Use IDNA on all network connections
Date: Tue, 29 Dec 2015 18:05:01 +0200	[thread overview]
Message-ID: <83mvstdyvm.fsf@gnu.org> (raw)
In-Reply-To: <87io3hjx9e.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  29 Dec 2015 12:43:25 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 29 Dec 2015 12:43:25 +0100
> Cc: emacs-devel@gnu.org
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > 3 Highly Restrictive 
> >
> >  * All characters in each identifier must be from a single script, or from the
> >  combinations: 
> >
> >  * Latin + Han + Hiragana + Katakana; 
> >  * Latin + Han + Bopomofo; or 
> >  * Latin + Han + Hangul 
> 
> I've now implemented this in puny.el

Thanks.

> but...
> 
> >  * No characters in the identifier can be outside of the Identifier Profile 
> 
> I'm not sure I quite follow what they're saying here:
> 
> http://www.unicode.org/reports/tr31/#Table_Candidate_Characters_for_Inclusion_in_Identifiers

They are saying we should allow these characters in identifiers,
unless we have a very good reason not to.

> But do we have this table somewhere in Emacs already?  :-)

I don't think so.  However, the list of those characters is very
short, so having it as a list or a regexp is not a problem.



  reply	other threads:[~2015-12-29 16:05 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
2015-12-29  9:03             ` Lars Ingebrigtsen
2015-12-29 11:43               ` Lars Ingebrigtsen
2015-12-29 16:05                 ` Eli Zaretskii [this message]
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=83mvstdyvm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).