<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 12/26/2018 5:30 PM, John Levine
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1812262024440.63085@ary.qy">
<blockquote type="cite" style="font-size: large; color: #3333FF;">
<blockquote type="cite" style="font-size: large; color:
#3333FF;"> definitely tell you that without loose address
matching that matches
<br>
user expectations, whatever they are, your customers will
hate you and
<br>
decide that your system is unusable.
<br>
</blockquote>
<br>
Totally.
<br>
<br>
My point was intended to be helpful in pointing out where you
might find data
<br>
to extend loose matching.
<br>
</blockquote>
<br>
I've been wondering if it's worth spinning up an IRTF </blockquote>
<p>Typo for IETF, I take it.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:alpine.OSX.2.21.1812262024440.63085@ary.qy">group to try
and collect advice on loose matching and (sort of its inverse)
son-of-PRECIS
<br>
assigning user names that allow characters that users expect, but
that won't collide with variants or if non-speakers misenter them
as homographs or near homographs.
<br>
</blockquote>
<p><br>
</p>
<p>Can you get enough bodies to join an IETF working group for 2-3
years?</p>
<p>Without that, nothing will happen in the i18n arena.</p>
<p>A./</p>
<p>PS: would be great if some issue like this could attract enough
participants to deal with these kinds of issues.<br>
</p>
<p><br>
</p>
</body>
</html>