ICANN ICANN Email List Archives

[ssac-gnso-irdwg]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [ssac-gnso-irdwg] Technical issues of internationalization

  • To: "Steve Sheng" <steve.sheng@xxxxxxxxx>, "Ird" <ssac-gnso-irdwg@xxxxxxxxx>
  • Subject: Re: [ssac-gnso-irdwg] Technical issues of internationalization
  • From: "YAO Jiankang" <yaojk@xxxxxxxx>
  • Date: Mon, 1 Mar 2010 11:50:02 +0800

Technical issues of internationalization
  ----- Original Message ----- 
  From: Steve Sheng 
  To: Steve Sheng ; Ird 
  Sent: Saturday, February 27, 2010 4:16 AM
  Subject: [ssac-gnso-irdwg] Technical issues of internationalization


  Hi all, I thought of an question and want to raise it here.  

  Currently Whois terminal clients may use specific encodings (e.g GB2312 for 
simplified Chinese, Big5 for traditional Chinese, etc) instead of UTF-8 or 
UTF-16. So what happens when a user submit a U-label domain name query in Big5 
or GB2312?


  comments: there will have a misunderstanding or miscoding, leading to the 
error.


   Should we expect the corresponding server to be able to interpret it?


  comments: it is not reasonable.  interpret different encoding from different 
countries is a huge load to the implementers and servers.


   How would the Whois server know what encoding the client's submission is in? 

  comments: we can not distingush what encoding the client's submission is in 
from the byte stream.

  the possible mechanism is the negotiation mechanism. the cilent send the 
token string such as gb2312 to tell the server I am using the encoding gb2312. 
or the server issues a token message to tell the client that we only support 
the utf8, otherwise, there will have a error.

   
  Warmly,  
  Steve 


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy