FreeTDS Development Group

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

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT mail.vodafone.it]
> Sent: May 14, 2003 12:32 PM
> > > 
> > > 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.  
> 
> In this case I think code is better than any explanation. 
> Update iconv.c and look at new code...

Nice work!  

Seeing as you've hand-edited (to our advantage) the perl-generated section,
I think we should pull the perl code out and sort the list alphabetically,
to make things easier to find, unless there's some reason not to.  Thanks
for rationalizing the names, too.  Do you think we can ignore case
(strcasecmp(3))?  ISTM the list would be shorter, and I can't imagine two
different character sets whose names differed only by case.  

One question, though, because you seem to have an idea different from mine.
When Sybase sends you its charset name "iso88597", and you're using HP
iconv, how are you going to locate the iconv name that HP uses?  

My idea is to use src/tds/sybase_character_sets.h to get the canonical name,
and src/tds/alternative_character_sets.h to back into the iconv name.  But,
to do that, we somehow have to identify the name to use.  (We could try each
one in turn, I guess.)  

--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.