FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> 
> It seems I goofed slightly in the configuration code that determines
> whether the homegrown iconv should be used. I check for UCS-2
> conversions but not the UTF-8 ones. The symptom on a system that
> attempts to use the system-supplied iconv but doesn't have the UTF-8
> conversions installed is an assert at line 338 in 
> tds_iconv_open(). The
> attached patch corrects the deficiency in the VMS-specific 
> configuration
> script.
> 

Applied (both 0.62 and 0.63). I bumped 0.62 version to 0.62.2 just to
avoid collision (I don't want someone think that 0.62 CVS is still
0.62.1).

> I'd appreciate it if this could be applied not only to the development
> stream but also to 0.62 in case we end up with an 0.62.2 at 
> some point.
> 
> In the meantime, the easiest workaround is to hide all iconv 
> conversions
> from the configuration procedure like so:
> 
> $ define SYS$I18N_ICONV NL:
> $ @[.vms]configure
> 
> The other workaround is not really a workaround, but a real solution, 
> namely to install the Unicode conversions from the optional 
> internationalization kit.  Directions for that are here:
> 
>
http://h71000.www7.hp.com/doc/732FINAL/5763/5763pro_018.html#intern_supp
ort_sec

Good for UG :)

freddy77