<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2/12/2019 12:33 PM, John Levine
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20190212203346.8C5B2200E37E17@ary.qy">
<pre class="moz-quote-pre" wrap="">In article <a class="moz-txt-link-rfc2396E" href="mailto:1A1FCA40-9172-4FCF-AC8B-2A4A1FE3E11A@verisign.com"><1A1FCA40-9172-4FCF-AC8B-2A4A1FE3E11A@verisign.com></a> you write:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">should look into requesting an update of UTS#46 to add the “Armenian dot” or in the protocol itself (e.g. a mapping solution)?
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
No -- the problem is that you need different mappings for different
input languages. See the message I just sent.</pre>
</blockquote>
<p>What about URLs that are in a document or database?</p>
<p>There's no "input language" for them. (Or not necessarily one).</p>
<p>I think for things like separators, the only thing that works is
a generic set of acceptable ones that will be converted, so that
no matter from where you access a URL it will work the same.</p>
<p>Whether such mapping would be sensitive to the *script* of some
character found in the domain name, that's another matter.<br>
</p>
<p>A./<br>
</p>
</body>
</html>