> The CMS API doesn't currently have methods for dealing with multibyte C++ > strings so strings are expected to be encoded with values from 0-255.
So, with new ActiveMQcpp C++ consumer won't be able to reconvert a text message with UTF-8 char for example 0xC484 (this char stays for one letter which looks like 'A,'). It's kinda sad cause old consumer was able to deal with this (it was using iconv to reconvert text message from UTF-8 to proper charset and it was working like a charm). Now, i guess, only way to make this still possible is to rewrite both producer and consumer to use binary messages. Maybe, in a future releases of ActiveMQcpp, there would be a chance for some kind system dependend compilation to allow linux/unix systems with native iconv support to deal with those kind of text messages? -- View this message in context: http://www.nabble.com/ActiveMQcpp-cms%3A%3ASession%3A%3AcreateTextMessage%28%29-function-usage-question-with-ISO-8859-1-strings-tp24747592p25242884.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
