Anything that you can put in a C++ string object should work, as far as Unicode we don't support that and the client would throw an exception if it received a string containing multi-byte characters. If you need to send Unicode string data I'd recommend encoding it in a ByteMessage and then unpacking that on either side.
Regards Tim. On Fri, 2008-08-01 at 16:45 +0200, Patrick Ruckstuhl wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Tim, > > is this just the "simple" ASCII set or the extended ASCII set? (e.g. > what about umlauts?) > > And what it the recommended way to deal with other characters? > > Thanks and Regards, > Patrick > > > | The CMS MapMessage supports ASCII characters > | > | Regards > | Tim. > | > | On Fri, 2008-08-01 at 12:20 +0200, Patrick Ruckstuhl wrote: > | Hi, > | > | Does anyone know what the valid characters for strings in map messages > | are (cms)? > | > | Thanks and Regards, > | Patrick > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkiTIYMACgkQaA/ofYi4EMpmwwCghn/woZ86yiz+s5GCqowuHWEN > ENAAnirE9dD8QW1ifdRRXagg+OFmwFNx > =ss4V > -----END PGP SIGNATURE-----
