> I don't think so, the content-type charset header describes the > character encoding.
It's mostly ascii characters, but sometimes, the string contains a few unicode characters which can have different code pages for each character. Since the ClientCnx.AnswerString is an AnsiString anyway, I think the only choise is to convert them to UTF8. The D2009 ide does this too if you add some unicode characters in a unit. Unless the AnswerString becomes a unicodeString ... Or am I missing something here ? Paul ----- Original Message ----- From: "Arno Garrels" <arno.garr...@gmx.de> To: "ICS support mailing" <twsocket@elists.org> Sent: Friday, January 09, 2009 7:09 PM Subject: Re: [twsocket] ClientCnx.AnswerString > Unicode is IMHO valid, it depends on the content-type charset. > Should be "utf-16" for UnicodecodeString. > But in the wild I never saw a utf-16 header so far, probably since it's > a wast of bandwith sending double byte characters over the network > (in most cases). > >> If not, then everything needs to be UTF8 encoded before sending > > I don't think so, the content-type charset header describes the > character encoding. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
