From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Use IDNA on all network connections
Date: Tue, 29 Dec 2015 17:47:25 +0100 [thread overview]
Message-ID: <87si2l5hia.fsf@gnus.org> (raw)
In-Reply-To: <83k2nxdxbb.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 Dec 2015 18:38:48 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
>> Date: Tue, 29 Dec 2015 17:28:55 +0100
>>
>> So they're saying that even if it's otherwise latin, a, say,
>> KATAKANA-HIRAGANA DOUBLE HYPHEN still doesn't take it out of the Highly
>> Restrictive class?
>
> I think so, yes.
>
>> but zero width characters in domain names?
>
> They are needed to force or prevent character composition, I guess
> that's the reason. Emacs displays them as a thin space, so someone
> with sharp enough eyes will be able to notice, I think.
Okidoke. I've now added that table to the predicate.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2015-12-29 16:47 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
2015-12-29 16:28 ` Lars Ingebrigtsen
2015-12-29 16:38 ` Eli Zaretskii
2015-12-29 16:47 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si2l5hia.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.