ISO/IEC 646 text encoding - E1.20 RDM (Remote Device Management) Protocol Forums

sblair · November 4th, 2019

Good question. I don't think this has ever come up before as a question. All characters in RDM are handled as 1 byte per character. Yes, implementation follows standard ASCII representation where the leading bit would be 0.

http://www.asciitable.com/

If my device has Multilanguage support then I would probably display the messages based on what the LANGUAGE PID is set to. I think you'll find most probably just return using the American character sit. There is no right and wrong here and you'll probably get better responses from others here that have more international language experience than I do.

It is really left up to the implementer how they want to handle it in the way that most makes sense for their product.

As far as non-printable characters there really isn't much I think you can do other than to just ignore them.

November 4th, 2019	#2
sblair Administrator Join Date: Feb 2006 Posts: 441	Good question. I don't think this has ever come up before as a question. All characters in RDM are handled as 1 byte per character. Yes, implementation follows standard ASCII representation where the leading bit would be 0. http://www.asciitable.com/ If my device has Multilanguage support then I would probably display the messages based on what the LANGUAGE PID is set to. I think you'll find most probably just return using the American character sit. There is no right and wrong here and you'll probably get better responses from others here that have more international language experience than I do. It is really left up to the implementer how they want to handle it in the way that most makes sense for their product. As far as non-printable characters there really isn't much I think you can do other than to just ignore them. __________________ Scott M. Blair RDM Protocol Forums Admin