FreeTDS Development Group

["Mark J. Lilback" <mark AT lilback.com>]

At 2:10 PM -0400 9/1/2002, James K.Lowden wrote:
> No current developer afaik has tools to exercise the UTF-8 work.

Mac OS X uses unicode natively for strings, so any native (as opposed 
to command line port) application should be testing it. My 
application does, and I've got a few basic tests setup to check for 
Unicode support (which currently fail with freeTDS).

I was making the same assumption that utf8 would be easier than ucs2. 
However, another reason for utf8 might be to avoid worrying about 
ucs4 down the line.

Another thing for me is that I'd prefer to avoid any conversion in 
freeTDS, or at least have it at the client level. Right now, it comes 
on the wire as unicode, iconv converts it to latin1, and then my 
application converts it back to unicode.

If conversion were at the client level, I could get the unicode via 
dbdata(). As it is, that doesn't work since the iconv support is at 
the tds layer. Utf8 or ucs2 support would be better, of course.


--
__________________________________________________________________________
                                  "They that can give up essential liberty
Mark J. Lilback                    to obtain a little temporary safety
<mark AT lilback.com>                 deserve neither liberty or safety."
http://www.lilback.com/                               -- Benjamin Franklin