[Nut-upsdev] Encoding when communicating with a NUT server?

Glen Bakeman gbakeman at live.com
Thu Jan 21 17:53:43 GMT 2021

Thank you for clearing that up for me!

On January 21, 2021 12:20:12 AM PST, Roger Price <roger at rogerprice.org> wrote:
>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
>> 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
>code 127 has yet to be considered.  So far no-one has requested accents
>on ups 
>Nut-upsdev mailing list
>Nut-upsdev at alioth-lists.debian.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20210121/5a4133c7/attachment.html>

More information about the Nut-upsdev mailing list