<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>Thank you for clearing that up for me!<br><br><div class="gmail_quote">On January 21, 2021 12:20:12 AM PST, Roger Price <roger@rogerprice.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Wed, 20 Jan 2021, Glen Bakeman via Nut-upsdev wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I'm working on a library in .Net to communicate with NUT servers as a <br>client. I'm at the point of setting up a socket to send and receive <br>information from a NUT server, but I've realized that I don't actually <br>know what encoding I should use when sending the raw bytes. ASCII? <br>UTF-8? Something else? I want to assume that it's UTF-8, but just in <br>case there's some sort of edge-case, I'd like to know for sure.<br></blockquote><br>The vocabulary of commands from the client and responses from upsd are all in <br>basic ASCII which is the same as UTF-8 in the first 127 characters. As long as <br>you stick to characters 0-127, UTF-8 is ok. Future expansion beyond character <br>code 127 has yet to be considered. So far no-one has requested accents on ups <br>names.<br><br>Roger<hr>Nut-upsdev mailing list<br>Nut-upsdev@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a></pre></blockquote></div></body></html>