Some encoded strings get turned to empty strings?

Jul 30, 2014 at 1:24 PM
Took me a while to realize this, but it seems that some strings containing special characters don't make the trip through rclr. My guess is it has to do with the encoding that rclr uses for strings.
For example:
    public string returnEmDashString()
        return "Hello buddy – How are you?";
calling this through rclr:
clrCall(obj=FF_net_obj, methodName='returnEmDashString')
returns a blank string.
I've been using rclr pretty extensively so I was surprised to find this issue.
Wrote in a hurry because I don't have time to make a full working sample right now, but I'm really anxious to see this fixed, so if I can provide a better sample let me know.
Aug 5, 2014 at 9:02 AM
Noted in Thanks for providing information that can be captured in a unit test.

The string conversion is done at the C level (R and MS COM APIs) by default, and this was a pain to do; not surprised this is an issue though I would have assumed it is an issue with unicode, not ANSI (in which em-dash is?).

Do you get the same behavior after a call to setRDotNet(TRUE) ?

As an aside I am not sure it is even possible to support unicode in an R-.NET interop context. Forgot what R supports