Nut upsdev - Jan 2021 - Encoding when communicating with a NUT server?

Hi everyone,

I apologize in advance if this is an obvious question - I haven't dealt 
with string encoding much when programming before.

I'm working on a library in .Net to communicate with NUT servers as a 
client. I'm at the point of setting up a socket to send and receive 
information from a NUT server, but I've realized that I don't actually 
know what encoding I should use when sending the raw bytes. ASCII? 
UTF-8? Something else? I want to assume that it's UTF-8, but just in 
case there's some sort of edge-case, I'd like to know for sure.

Thank you,

Glen

On Wed, 20 Jan 2021, Glen Bakeman via Nut-upsdev wrote:
> I'm working on a library in .Net to communicate with NUT servers as a 
> client. I'm at the point of setting up a socket to send and receive 
> information from a NUT server, but I've realized that I don't
actually
> know what encoding I should use when sending the raw bytes. ASCII? 
> UTF-8? Something else? I want to assume that it's UTF-8, but just in 
> case there's some sort of edge-case, I'd like to know for sure.
The vocabulary of commands from the client and responses from upsd are all in 
basic ASCII which is the same as UTF-8 in the first 127 characters.  As long as 
you stick to characters 0-127, UTF-8 is ok.  Future expansion beyond character 
code 127 has yet to be considered.  So far no-one has requested accents on ups 
names.

Roger