Paul wrote: > Are unicode characters in the body part not conform the RFC then ?
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. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- 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
