Unicode & IETF

[Shawn Steele]

Several people have expressed concerns about the outcomes of Unicode’s discussions.  Some of those folks (I’m not sure about everyone) work for companies that are members of Unicode.  And those companies have representatives to the UTC.


A)     If you have concerns about Unicode, the encoding of new characters, etc., please talk to some of your organization’s representatives to Unicode.  &/or figure out how to participate, &/or

B)      Delegate those responsibilities to those coworkers with Unicode expertise that are attending the UTC, &/or

C)      If you think your organization’s UTC participants don’t have the expertise to handle IDN/networking/IETF type concerns, then please educate them so you know they’re representing your concerns in the UTC.

The wrong process is to skip A, B, & C, and then after the fact try to figure out how to ‘fix’ Unicode.  This also isn’t the first time this has happened.

It’s not that we don’t have smart people in both groups, there are very smart people in both groups, but somehow there’s no confidence that the other group is ‘doing the right thing’, or perhaps no confidence that the other group ‘understands my requirements’.  Those should be solvable problems.

-Shawn

 
http://blogs.msdn.com/shawnste
http://L3-G0.blogspot.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/idna-update/attachments/20140811/2edf2e81/attachment-0001.html>