Non English Characters in char array using RTI Connector

3 posts / 0 new
Log in or register to post comments
Last post
Wed, 12/30/2020 - 09:37
#1
kumar.ajay11
Offline
Last seen: 3 years 11 months ago
Joined: 11/24/2016
Posts: 6
Non English Characters in char array using RTI Connector

Hi,

I am trying to use char array to publish Non-English characters using RTI Connector. But when I check in Admin console I get different values.

For ascii values it works fine but when I am sending unicode then I am not getting same values whether I use RTI connector for python or js. When I use the native libraries to generate example for same and run the program then I am getting the values in Admin console what I had sent. As a result I am not able to use connector for sending Non English Charatcers in char array.

Can anybody suggest the way to resolve the issue?

Regards,

Ajay Kumar 

Organization:
Keywords:
Top
Wed, 12/30/2020 - 10:11
gianpiero
gianpiero's picture
Offline
Last seen: 11 months 19 hours ago
Joined: 06/02/2010
Posts: 177

Hello Ajay,

Thanks for writing here. It may be that you are using char (string) instead of wchar. I think a char is too small to contain unicode. There is an article in the knlowedge base abou this:

https://community.rti.com/kb/how-do-i-send-strings-non-english-characters-utf-8-unicode-etc-over-dds

I hope this helps

Best,
  Gianpiero

Top
Thu, 01/07/2021 - 22:47
kumar.ajay11
Offline
Last seen: 3 years 11 months ago
Joined: 11/24/2016
Posts: 6

Hello Gianpiero,

Thanks for the information.

You have rightly pointed that I am using char instead of char.

I just wanted to say that I have a subscriber which is built using Core libraries of C++ and Java.

Also, I have a publiser which is built using RTI Connector (Python / Javascript). Now when I am publishing the Non-englidh characters, same is not getting reflected correctly.

But when I use a publisher built using Core libraries of C++ and Java, then Non-english characters are getting reflected correctly in Admin as well as subscriber.

Does this mean that there is some issue in the RTI connector?

Regards,

Ajay Kumar

Top