Idna-update Digest, Vol 36, Issue 48
Shawn.Steele at microsoft.com
Sat Dec 5 09:07:14 CET 2009
I think that's true for all 4 characters. I don't think we can disallow them.
Note that ZWJ/ZWNJ can be used in a link in IDNA2003, but they're mapped to nothing, so the address bar will likely look funny, though you can still get to a server. I'm not saying that's good behavior, but I suppose it's better than nothing. I'm also not trying to suggest it doesn't need fixed, it is clearly a big display problem that should be addresses as soon as practical.
From: idna-update-bounces at alvestrand.no [idna-update-bounces at alvestrand.no] on behalf of Sarmad Hussain [sarmad.hussain at nu.edu.pk]
Sent: Friday, December 04, 2009 7:50 PM
To: idna-update at alvestrand.no
Cc: idna-arabicscript at lists.irnic.ir
Subject: Re: Idna-update Digest, Vol 36, Issue 48
> 200C ; DISALLOWED # ZERO WIDTH NON-JOINER
> 200D ; DISALLOWED # ZERO WIDTH JOINER
> There is no new value called TRANSITIONAL. The infamous 4 characters
> (above) start with the value DISALLOWED. Later, we change them to
> PVALID (or CONTEXTJ for 200C/200D).
Before reverting to IDNA2003 level lack of support for these characters, do re-consider why the status of these characters (ZWNJ and ZWJ) have been changed in Idnabis process: these characters are required for writing IDNs for a billion people in South Asia and beyond.
Having them as DISALLOWED and called TRANSITIONAL will only propagate older decisions, not fix them. Having them as CONTEXTJ is already a workable solution, where they are only (carefully) allowed, where they are needed.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update