FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: May 14, 2003 1:59 AM
> Il mar, 2003-05-13 alle 23:16, Lowden, James K ha scritto:
> > > From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> > > Sent: May 13, 2003 4:00 PM
> > > 
> > > Well... I don't personally consider libTDS stable to test in
> > > production... Not using variable charset and not using 
> no-GNU iconv
> > > version... HP/UX iconv do not run at all. Mac OS X do not work
> > > (ISO-8859-1 is not supported in Mac OS X.. strange).
> > 
> > OK, subject to those constraints.  Is there anything 0.61 
> does that can't be
> > done with current CVS?  
> > 
> 
> No, with those contraints 0.62 can do anything...

Well, as David found out, 0.61 will revert to non-iconv behavior if
iconv_open(3) fails.  Current CVS will deal stupidly with that.  This is a
case where assert(3) would have been clearer than returning an error...

> > > If a system does not have UCS-2LE we should set a flag like
> > > "convert UCS-2BE to UCS-2LE"... another suitable flag is pass 
> > > from UCS2
> > > (if direct conversion is not supported convert first to ucs2 
> > > and then to destination...)
> > 
> > tds_iconv_open() should set such a flag in the TDSICONVINFO 
> structure, and
> > tds_iconv should honor it.  That way, no other code has to 
> bother with it.  
> > 
> 
> MMmmm... a new idea.
> Currently we convert first names to canonical, than we try to use this
> name with iconv. So we fill alternative with all possible names! 

My thought exactly.  You just have to be sure to guard OS-specific named
with #if, to avoid conflicts.  Remember, we need that table for
Server->canonical->iconv lookups.  

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.