As I mentioned, this was using our Visage product (thin client, browser based with thick client look & feel), and message streams were being encoded/decoded anyway, so it "hid" the problem from us.
Couldn't use the "standard" facilities (eg: queries) with terminal devices - anyway, a small change in the middle and we can now operate with or without NLS. An interesting side note to this was that one of our major Visage users (Reynolds & Reynolds) moved from D3 to Universe because of NLS - yet on the Visage front we had Chinese/multi-byte working on working on D3 (which "doesn't support it") and non-NLS UV first .... in the end it was only a day or two of mucking around to make it all happen either way. However, we had the "luxury" of working within a browser environment for the client, so we were already encoding/decoding data streams - data is stored as UTF-8 (I think) Ross Ferris Stamina Software Visage - an Evolution in Software Development >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Adrian Matthews >Sent: Thursday, 28 April 2005 8:24 PM >To: [email protected] >Subject: RE: [U2] [UV][SB+] foreign character-set support > >Ross, > >How are you storing the Chinese characters if you're not using NLS? > >We use NLS and wIntegrate with Chinese characters and found the reverse >problem that without NLS we couldn't get the characters in and out of >Universe without lots of custom encoding and decoding. > >Adrian Matthews >IG Index ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
