Re: Use IDNA on all network connections

[Lars Ingebrigtsen <larsi@gnus.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> 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.

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?  Makes sense, but zero width characters in domain
names?  

 Code Point  Glyph  Name  
 0027  '  APOSTROPHE  
 002D  -  HYPHEN-MINUS  
 002E  .  FULL STOP  
 003A  :  COLON  
 00B7  ·  MIDDLE DOT  
 058A  ֊  ARMENIAN HYPHEN  
 05F3  ׳  HEBREW PUNCTUATION GERESH  
 05F4  ״  HEBREW PUNCTUATION GERSHAYIM  
 0F0B  ་  TIBETAN MARK INTERSYLLABIC TSHEG  
 200C    ZERO WIDTH NON-JOINER*  
 200D    ZERO WIDTH JOINER*  
 2010  ‐  HYPHEN  
 2019  ’  RIGHT SINGLE QUOTATION MARK  
 2027  ‧  HYPHENATION POINT  
 30A0  ゠  KATAKANA-HIRAGANA DOUBLE HYPHEN  
 30FB  ・  KATAKANA MIDDLE DOT  

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no