I don't fully understand the technology, but... The encoding mechanism in that client code works exactly the same as the UTF-8/RACE encoding (since the Chinese, Japanese, and Korean character sets are all subsets of UTF-8) but you still need to send the encoding type of UTF-8 (instead of Big5 or ShiftJIS or whatever)
Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of John Keegan > Sent: March 21, 2002 10:08 AM > To: [EMAIL PROTECTED] > Subject: Re: Transfering IDN Names > > > Sorry I was not clear in my message. > > We're using the original OpenSRS client multilingual code, the one first > released for Chinese, Japanese and Korean languages. UTF-8 not > required. Can > you see any reason why we could not use this client to send the > RACE encoded > domain as a transfer request? Would we need to send encoding type as well? > > -- > John Keegan > [EMAIL PROTECTED] > http://RackShare.com > > > > From: Charles Daminato <[EMAIL PROTECTED]> > > Date: Thu, 21 Mar 2002 07:32:12 -0500 (EST) > > To: John Keegan <[EMAIL PROTECTED]> > > Cc: [EMAIL PROTECTED] > > Subject: Re: Transfering IDN Names > > > > You must be using the XML API, and send the appropriate flags > (UTF-8, RACE > > encoded name) > > > > The client code does not send raq UTF-8 characters anyway, but > it will not > > convert them properly (out of the box) if the web browser is not set to > > UTF-8 :) > > > > Charles Daminato > > TUCOWS Product Manager > > [EMAIL PROTECTED] >
