camille bodart

string-encoding-problem

the problem is not in NET.TCP.SEND but in the mxj object.

think you'll be interested by this thread :

https://cycling74.com/forums/index.php?t=msg&th=26758&start=0&rid=0&S=d7220001cb905a43a508e1cd994f47ca

I think you'll have this problem each time you call a method of the Atom class (Atom String). So the problem will always occur with c74.net.* classes. That's why I said it was a mxj global problem.

In your example, you are able to print a String with the right encoding, but I don't think you'll be able to do it with an Atom. Same problem if you try to send your right encoded String back to max world.

A workaround is to implement your own tcp class.

I think you'll have this problem each time you call a method of the Atom class (Atom  String). So the problem will always occur with c74.net.* classes. That's why I said it was a mxj global problem.

I am almost 100 sure that the problem is the the jni bridging between 

max and java. Hpefully we can address this in the not to distant future.

I am almost 100 sure that the problem is the the jni bridging between 
max and java. Hpefully we can address this in the not to distant future.


String encoding Problem