Alireza Saleh saleh at nic.ir
Fri Mar 20 12:00:27 CET 2009

I don't see why we should not just let the registry have the authority 
to do this? If you want to disallow this at the protocol level, you 
should also consider  disallowing the Low rise 'U+005F'  and 
Hyphen-minus U+002D because these have also the same shape as Tatweel 
specially when they come in between of non-joining characters. My 
opinion is to limit protocol prohibitions to absolutely necessary cases.


Mark Davis wrote:
> I propose that we make U+0640 ( ‎ـ‎ ) ARABIC TATWEEL (aka kashida) be
> DISALLOWED, adding it to
> http://tools.ietf.org/html/draft-ietf-idnabis-tables-05#section-2.6.
> Currently it is PVALID, but it does not carry semantics by any
> Arabic-Script orthography, and its only value is for spoofing.
> For example: جوجل can be written with extra kashidas as جـوجل or as
> جوجـل by inserting a kashida after the first or third character. This
> is very hard for users to detect. We added it to Unicode for use in
> manual justification, but has no place in IDNA.
> (http://en.wikipedia.org/wiki/Kashida,
> http://unicode.org/cldr/utility/character.jsp?a=0640)
> Mark
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update

More information about the Idna-update mailing list