Additional thoughts on TRANSITIONAL

[Sarmad Hussain]

Thanks for correcting the subject.

 

Mapping ZWJ and ZWNJ to nothing (i.e. ignoring them) had issues and that is
why they were categorized as CONTEXTJ in the revised version and allowed “on
the wire” in the right context (after ACE conversion).  

 

The IDNA implementation in different applications will catch up at different
pace.  However that does not change the community requirements vis-à-vis the
protocol.  Correct protocol representation also empowers communities to
develop their own applications.

 

Regards,
Sarmad

 

 

From: Shawn Steele [mailto:Shawn.Steele at microsoft.com] 
Sent: Saturday, December 05, 2009 1:15 PM
To: Shawn Steele; Sarmad Hussain; idna-update at alvestrand.no
Cc: idna-arabicscript at lists.irnic.ir
Subject: Re: Additional thoughts on TRANSITIONAL 

 

Oopsy, correcting subject.

 

-Shawn

  _____  

From: idna-update-bounces at alvestrand.no [idna-update-bounces at alvestrand.no]
on behalf of Shawn Steele [Shawn.Steele at microsoft.com]
Sent: Saturday, December 05, 2009 12:07 AM
To: Sarmad Hussain; idna-update at alvestrand.no
Cc: idna-arabicscript at lists.irnic.ir
Subject: RE: Idna-update Digest, Vol 36, Issue 48

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.

 

-Shawn

  _____  

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. 

 

regards,
Sarmad  

 



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3811 (20090129) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20091205/0298798d/attachment-0001.htm