<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 01.11.11 23:10, Salanieta T. Tamanikaiwaimaro wrote:
<blockquote
cite="mid:CAJwbTiAtZcOafg8d=-Tfs5eE5E7NN8n2-A0oP+7jhUBShULZtA@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Wed, Nov 2, 2011 at 6:33 AM, Daniel
Kalchev <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:daniel@digsys.bg">daniel@digsys.bg</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I have
done some presentations that demonstrate the use of
different (widely available) computer fonts and the
possible confusability of these two strings.</blockquote>
</div>
<div class="im"><br>
<font class="Apple-style-span" color="#3333ff">This is
awesome and it would be great to share some of the
learnings, if possible but if you have already posted it
on a website, maybe you can direct me to the URL or email
me offline.</font><br>
</div>
</blockquote>
</div>
</blockquote>
<br>
It is publicly available and searchable on Google as well. I found
an on-line version at
<a class="moz-txt-link-freetext" href="https://www.centr.org/main/6079-CTR/version/default/part/AttachmentData/data/Daniel">https://www.centr.org/main/6079-CTR/version/default/part/AttachmentData/data/Daniel</a>
Kalchev - bgidn20110202v3.pdf<br>
<br>
I believe the different font renderings are informative enough. That
presentation was produced in the beginning of the year and is pretty
much schematic, because the target audience is deeply aware of the
issues -- there were some developments since then, but mostly in
area of... talking. (ok, politics, I know)<br>
<br>
<blockquote
cite="mid:CAJwbTiAtZcOafg8d=-Tfs5eE5E7NN8n2-A0oP+7jhUBShULZtA@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">The
official response to this is that the ISO3166 table and
therefore the current set of ccTLD names is inherited by
ICANN, but they are committed to avoid confusability in
future. Therefore, Cyrillic and Greek are declared "second
grade" alphabets and any hint on possible confusability is
taken as a show stopper.<br>
<br>
</blockquote>
<div><font class="Apple-style-span" color="#3333ff">No language
or aphabet is second grade.Article 19 of the Universal
Declaration of Human Rights gives people the right to
freedom of expression. There is also the Convention on the
Protection and Promotion of the Diversity of Cultural
Expressions 2005 and another Convention for the Safeguarding
of Intangible Cultural Heritage.</font></div>
</div>
</blockquote>
<br>
While this is true, one needs to remember what ICANN was like when
the IDN Fast Track came into effect (end of 2009). An US based
company was hired to provide the 'language expertise' for the IDN
Fast Track and unfortunately, their work is covered in secrecy. I
can understand that the combined desire to avoid any possible
'confusion' (and ICANN be blamed for making the Internet less
'stable') and the probably too US (therefore ASCII) centric
knowledge of the experts led to this situation. Thing is, they by
default assume any two letter Cyrillic or Greek strings is
"confusingly similar" to any two character ASCII string -- which is
ridiculous.. at least.<br>
<br>
<blockquote
cite="mid:CAJwbTiAtZcOafg8d=-Tfs5eE5E7NN8n2-A0oP+7jhUBShULZtA@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
Funny, that the IDN Fast Track process talk about the need to
demonstrate probable confusion, not merely possible confusion</blockquote>
<div><font class="Apple-style-span" color="#3333ff">This is
interesting, to find what the difference between probable
and possible is and which is the lower threshold?</font> <br>
</div>
</div>
</blockquote>
<br>
In my understanding of English, "possible" means it can be
demonstrated that it is (however rare) subject to confusability, in
some (even if carefully crafted and controlled) situations.
"Probably", should require further qualification of the frequency
this is happening. For example, you take an sample of 1000 persons.
For 5 of those persons .бг and .bg are confusable -- this is
"possible" but in no way "probable". If, for 200-400 it is
confusable, it is then perhaps "probable". If you have say 500-700
confused, I would call it "very probable". Sort of that.<br>
<br>
Thing is, you can demonstrate that almost any two strings are
confusable, in a specific context and using specific fonts.<br>
<br>
None of this data is available for the evaluation of the Bulgarian
application however.<br>
<br>
Daniel<br>
</body>
</html>