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

["Metalitz, Steven" <met@xxxxxxx>]

With regrets I will probably not be able to participate on today's call. 

Steve Metalitz

________________________________

From: owner-ssac-gnso-irdwg@xxxxxxxxx 
To: 'Steve Sheng' ; 'Ird' 
Sent: Sun Feb 28 19:13:09 2010
Subject: RE: [ssac-gnso-irdwg] Technical issues of internationalization 


A couple of thoughts on this:

 

1. if we would suggest allowing submission of UTF8 or 16 to the WHOIS server, 
we would probably have to change the protocol, and from which we would need to 
specify some mechanism for the client to identify itself as sending UTF8

 

2. it would be somewhat impossible to distinguish definitively whether an 
incoming query is in a particular encoding (especially given such a short 
string), so it is probably not reasonable for the server to "interpret" it

 

Edmon

 

 

 

From: owner-ssac-gnso-irdwg@xxxxxxxxx [mailto:owner-ssac-gnso-irdwg@xxxxxxxxx] 
On Behalf Of Steve Sheng
Sent: Saturday, February 27, 2010 4:17 AM
To: Steve Sheng; Ird
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? Should we expect the corresponding server to be able to interpret 
it? How would the Whois server know what encoding the client’s submission is 
in? 

 
Warmly,  
Steve 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2704 - Release Date: 02/26/10 
15:34:00