<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 9 April 2018 at 18:02, Aaron Edwards <span dir="ltr"><<a href="mailto:aedwards@b3insight.com" target="_blank">aedwards@b3insight.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi All,<br>
<br>
Thanks for replying.<br>
<br>
The data is being read from SQL Server, where it is encoded in Latin1.  I'm reading it from SQL Server, and writing it to postgis using a .NET process.  I'm not doing anything special to convert from one character set to the other, so maybe that's the problem.<br>
<br>
Aaron<br>
<br></blockquote><div>Hi,</div><div><br></div><div>Then, you should set the PGCLIENTENCODING environment variable to 'LATIN1',  either at the system level or when initializing connection.</div><div>(<a href="https://www.postgresql.org/docs/current/static/multibyte.html">https://www.postgresql.org/docs/current/static/multibyte.html</a>)</div><div><br></div><div>Nicolas</div></div></div></div>