<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hello all,<br>
<br>
if you feel strong enough about this and can convince the powers
that be in our community perhaps could you suggest the ALAC makes a
Statement about this?<br>
Kindest regards,<br>
<br>
Olivier<br>
<br>
<div class="moz-cite-prefix">On 04/04/2024 06:45, Bill Jouris via
At-Large wrote:<br>
</div>
<blockquote type="cite"
cite="mid:303510608.3124683.1712205909118@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi Evan,
<div><br>
</div>
<div><span
style="color: rgb(11, 83, 148); font-family: tahoma, sans-serif;">Consider
that some of the apps in play are open source. ICANN could
simply contribute code to Mozilla, Thunderbird, Wordpress,
Signal and other projects to make their IDN support seamless.
If that support is an in-demand feature it will make those
applications more desirable in a competitive environment.</span><br>
</div>
<div><br>
</div>
<div>And I've been arguing, without apparent success, for ICANN to
do exactly that. </div>
<div><br>
</div>
<div>Bill <br>
<br>
<div id="ymail_android_signature"><a
id="ymail_android_signature_link"
href="https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature"
moz-do-not-send="true">Sent from Yahoo Mail on Android</a></div>
<br>
<blockquote style="margin: 0 0 20px 0;">
<div style="font-family:Roboto, sans-serif; color:#6D00F6;">
<div>On Wed, Apr 3, 2024 at 11:27 AM, Evan Leibovitch</div>
<div><a class="moz-txt-link-rfc2396E" href="mailto:evanleibovitch@gmail.com"><evanleibovitch@gmail.com></a> wrote:</div>
</div>
<div
style="padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px solid #6D00F6;">
<div id="yiv3814696577">
<div>
<div dir="ltr">
<div dir="ltr">
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">Hi Bill,<br
clear="none">
</div>
</div>
<br clear="none">
<div class="yiv3814696577gmail_quote">
<div dir="ltr" class="yiv3814696577gmail_attr">On
Wed, Apr 3, 2024 at 12:18 PM Bill Jouris <<a
rel="nofollow noopener noreferrer" shape="rect"
ymailto="mailto:b_jouris@yahoo.com"
target="_blank" href="mailto:b_jouris@yahoo.com"
moz-do-not-send="true"
class="moz-txt-link-freetext">b_jouris@yahoo.com</a>>
wrote:<br clear="none">
</div>
<div> </div>
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr">It seems to me that the
function of UA day is inherently NOT
directed at end users. It is directed at
getting vendors, those who provide software
interfaces for end users, to make provision
for IDNs.</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">Is it really
directed at apps developers?</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">Consider that
some of the apps in play are open source. ICANN
could simply contribute code to Mozilla,
Thunderbird, Wordpress, Signal and other
projects to make their IDN support seamless. If
that support is an in-demand feature it will
make those applications more desirable in a
competitive environment.<br clear="none">
</div>
</div>
<div> </div>
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr">End users are, of course,
wildly unlikely to be writing their own
browsers, email systems, etc., so they don't
really need to be involved.</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">People aren't
writing browsers, email systems, etc. to satisfy
the needs of ICANN, they're trying to meet the
needs of end-users. So if end users don't care
about IDNs, neither will apps developers, since
they have other priorities such as speed,
security, and <b><u>end-user</u></b> focused
features such as VPNs, form auto-completion,
spell-checkers, incognito modes and so on.</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
</div>
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr"> (Except to the extend that it
would be useful to show some user demand
when trying to convince vendors to become
IDN compatible.)</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">End-user
demand for IDNs isn't "useful", it's a mandatory
prerequisite. Without such bottom-up demand, app
developers have no incentive to divert
resources. In the service of i18n developers
place far more emphasis on Unicode support,
multilingual UI and multilingual integrated
search engines. If these features satisfy
end-user needs then there is no reason for them
to spend extra effort on IDNs. Developers may
well see IDNs as just a way for ICANN and its
contractors to peddle more domains, and without
end-user interest they have no incentive to
facilitate that.<br clear="none">
</div>
<br clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">One must again
remind that ICANN is not a treaty-backed
organization. It has no means to impose, let alone
enforce, its decisions on the world. Its solutions
must be superior and <u>desired</u>. Thus, so
long as end-user demand is not seen as a <b>necessary</b>
component in advancing IDNs, they will remain a
non-priority to developers and an avoidable risk
to would-be IDN registrants.<br clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">(Aside: I truly
find it amazing that this argument even needs to
be made within the community tasked with advancing
end-user interests within ICANN.)<br clear="none">
</div>
<br clear="none">
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr">Making end users aware of the
option to use non-ASCII characters for these
is, to my mind, an entirely separate
discussion.</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">If so, that
"separate discussion" is the only one worth
having within <i>ICANN At-Large</i>. Other
constituencies (civil society, governments, the
technical community, etc) all have their own
places to define and assert their own needs.<br
clear="none">
</div>
</div>
<div> </div>
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr">Both whether it is a worthwhile
effort and how to go about it if so. It is
also something that would really need to be
deferred until something like Universal
Acceptance is available on at least the most
widespread browsers and email systems.</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">Chicken and
egg.</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">If end-users
don't care about IDNs, browsers and apps won't
support them.<br clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">If browsers
and apps don't support IDNs, end-users won't
care about them.</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">BTW, the
objective is not for browsers to implement "UA".<br
clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">Support for
IDNs is the solution being pitched, UA is just
the name of the marketing campaign.<br
clear="none">
</div>
</div>
<div> </div>
<blockquote
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"
class="yiv3814696577gmail_quote">
<div>
<div
style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;">
<div dir="ltr"> Pitching to end users, when
the software they use does not yet support
IDNs, would be counterproductive.</div>
</div>
</div>
</blockquote>
<div><br clear="none">
</div>
<div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">And THAT is
why, 20 years from now, ICANN will still be
wondering why IDNs never caught on.</div>
<div id="yiv3814696577yqtfd14223"
class="yiv3814696577yqt0115941462">
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default">- Evan</div>
<div
style="font-family:tahoma, sans-serif;color:rgb(11,83,148);"
class="yiv3814696577gmail_default"><br
clear="none">
</div>
</div>
</div>
</div>
<div id="yiv3814696577yqtfd30220"
class="yiv3814696577yqt0115941462"><br clear="none">
</div>
</div>
<div id="yiv3814696577yqtfd21501"
class="yiv3814696577yqt0115941462">
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
At-Large mailing list
<a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/at-large">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a class="moz-txt-link-freetext" href="http://atlarge.icann.org">http://atlarge.icann.org</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Olivier MJ Crépin-Leblond, PhD
<a class="moz-txt-link-freetext" href="http://www.gih.com/ocl.html">http://www.gih.com/ocl.html</a></pre>
</body>
</html>