I'm having trouble displaying Korean characters in WiTango that are stored as Unicode in MS-SQL - all I get on the screen are ???'s. If the code is stored as Euc-KR then it works.
I've discovered the following: The double byte Unicode data is stored in an nvarchar field. The first character in the string should be U+ACE0 (Unicode value in hex.). However, if I do a SELECT Convert(varbinary,left(field_name,1)) from table_name to get the Hex values of the first character in the field I get 0xE0AC ... So it appears that MS-SQL is storing the byte-pair for each character backwards (ie. most significant byte comes second). I assume then that the bytes that are fed to WiTango from the select statements are also backwards and therefore appear nonsensical. Has anyone dealt with this before? Is there something I'm missing? Dave Machin ________________________________________________________________________TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
