Re: unicode server data incorrectly converted to iso-8859-1 on client
Daniel Fazekas <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
On May 31, 2010, at 12:45, Razvan Cosma wrote: > I'm stuck with what seems to be a very old problem: getting non-latin texts from SQL server 2005 into freetds. You need to set up the server's parameters (host name, port, tds version, etc) in the freetds.conf file, and then you can also specify the "client charset" option there. http://freetds.org/userguide/freetdsconf.htm There are changes in the works to provide alternatives, as you can see from previous messages here, but freetds.conf is the sure way for now. Maybe it would be time to even make utf-8 the default rather than iso-8859-1 in a future version.