consensus Call: TATWEEL

[Mark Davis]

That's fine.

Mark


On Mon, Mar 23, 2009 at 13:45, Vint Cerf <vint at google.com> wrote:

> Mark, I think it might be best to keep the TATWEEL U+0640 call distinct
> from the NKO U+07FA call simply because I have already started the first
> one. I will issue a second call.
> vint
>
>
>
> Vint Cerf
> Google
> 1818 Library Street, Suite 400
> Reston, VA 20190
> 202-370-5637
> vint at google.com
>
>
>
>
> On Mar 23, 2009, at 4:07 PM, Mark Davis wrote:
>
> My apologies, could you reissue this call for both characters? I've
> confirmed that they share the same characteristics.
>
> U+0640 <http://unicode.org/cldr/utility/character.jsp?a=0640> ( ‎ـ‎ )
> ARABIC TATWEEL
> U+07FA <http://unicode.org/cldr/utility/character.jsp?a=07FA> ( ‎ߺ‎ ) NKO
> LAJANYALAN
>
> Mark
>
>
> On Sun, Mar 22, 2009 at 08:32, Vint Cerf <vint at google.com> wrote:
>
>> Based on the on-line exchanges, it appears to me that the general
>> consensus is to ban TATWEEL by exception (ie. make it DISALLOWED).
>>
>> Please respond with:
>>
>> YES (ie make it DISALLOWED)
>>
>> NO (ie leave it PVALID)
>>
>> OTHER: <explain what you propose>
>>
>> I will tally the responses arriving by April 4, midnight, EDT.
>>
>>
>>
>> Vint Cerf
>> Google
>> 1818 Library Street, Suite 400
>> Reston, VA 20190
>> 202-370-5637
>> vint at google.com
>>
>>
>>
>>
>> _______________________________________________
>> Idna-update mailing list
>> Idna-update at alvestrand.no
>> http://www.alvestrand.no/mailman/listinfo/idna-update
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20090323/4e1a2768/attachment.htm