FreeTDS Development Group

[Vano Beridze <vano.beridze AT silkroad.ge>]

This is the first lines of /tmp/freetds.log

log.c:196:Starting log file for FreeTDS 0.91
        on 2013-07-05 23:20:33 with debug flags 0x4fff.
iconv.c:330:tds_iconv_open(0x7fd771f79e10, UTF-8)
iconv.c:187:local name for ISO-8859-1 is ISO-8859-1
iconv.c:187:local name for UTF-8 is UTF-8
iconv.c:187:local name for UCS-2LE is UCS-2LE
iconv.c:187:local name for UCS-2BE is UCS-2BE
iconv.c:349:setting up conversions for client charset "UTF-8"
iconv.c:351:preparing iconv for "UTF-8" <-> "UCS-2LE" conversion
iconv.c:391:preparing iconv for "ISO-8859-1" <-> "UCS-2LE" conversion

As for UCS2 data, table column type is nvarchar(30) and as I know if the 
column is nvarchar or nchar it is stored as UCS2

Vano Beridze
Software Developer
Silk Road Group

On 9/5/2013 6:51 AM, James K. Lowden wrote:
> On Tue, 03 Sep 2013 14:20:28 +0400
> Vano Beridze <vano.beridze AT silkroad.ge> wrote:
>
> > The script works fine. it connects and gets the data. The only
> > problem I have is that data is shown as question marks, so it's not
> > converted to UTF-8. I've read all the information I could find on the
> > internet but can not solve the problem.
> I would set TDSDUMP and examine the log.  You're right that
> FreeTDS would substitute question marks for any non-convertible
> character.  Perhaps the character set name you specified in
> freetds.conf isn't exactly right, perhaps because you're linked to the
> system iconv library.
>
> The status of iconv is listed at the top of the log.  If it says it set
> the client charset to UTF-8, that's what it will use.
>
> A different problem that sometimes crops up: sometimes the "Unicode"
> data on the server isn't UCS2.  In that event, the server will send the
> data, but the iconv library will be unable to convert the characters
> correctly.
>
> --jkl
>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds