FreeTDS Development Group

[Frediano Ziglio <freddyz77 AT tin.it>]

...
> 
> At 4:43 PM -0400 9/2/2002, James K.Lowden wrote:
> >Instead of dual
> >conversion with an internal format, have zero or one conversions, as
> >requested by the client.
> 
> That's what I'd like to see. If I want the same character set as what 
> came on the wire, I shouldn't have to have two conversions.
> 

Is not best to tell library what encoding do you want and receive only
that encoding ??

> At 9:59 AM -0500 9/3/2002, Steve Langasek wrote:
> >Further assertion: all national language character sets in current use
> >on either Unix or Windows platforms are codepoint compatible with ASCII.
> 
> Is that true for the asian character sets?
> 
> At 6:36 AM -0700 9/3/2002, James K. Lowden wrote:
> >What would be the effect of setting the client character set to 
> >UTF-8 when the protocol is 4.2 or 5.0?
> 
> This would be useful.
> 
> The biggest issue for me has been with TDS 7. At first, iconv was 
> very problematic, and the default action of stripping down to ascii 
> was too limiting for me. So I just modified the code in the libraries 
> I distribute to not use iconv and only strip the high byte and treat 
> it as latin1.
> 
> I haven't tried getting iconv to work again, but I'm sure I can get a 
> version that works from Apple. (I don't remember where I got the 
> version I tried.)
> 
> I'd prefer to not worry about using iconv, as the Mac has its own 
> built-in encoding routines. I'd just like to get what comes over the 
> wire from SQL Server 2000 and let the CoreFoundation framework deal 
> with character sets and encoding.
> 
Another solution should the use of CoreFoundation directly in FreeTDS is
MacOsX is detected...

freddy77