Re: unicode server data incorrectly converted to iso-8859-1 on client

Hi - you're right, setting utf-8 in [global] gets rid of the error (this
should be on the bloody homepage of freetds.org :)
Still, characters outside the western alphabet are either stripped of the
accents/umlauts e.g. ă=â=a and Hebrew text is converted to question marks
(0x3f) without any warning/error message

fretds.log says:
token.c:2356:server indicated charset change to "iso_1"
iconv.c:985:setting server single-byte charset to "ISO-8859-1"
iconv.c:516:tds_iconv_info_init: converting "UTF-8"->"ISO-8859-1"
could this be server configuration issue? other tools like the .net
system.data.sqlclient dll do work as expected.

On Mon, May 31, 2010 at 2:37 PM, Daniel Fazekas <[email protected]> wrote:

> 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.
>
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds