FreeTDS Development Group

["Craig A. Berry" <craigberry AT mac.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.

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_support_sec

--- vms/configure.com;-0        Sat Jan  3 13:32:05 2004
+++ vms/configure.com   Sun Jan 18 15:22:17 2004
@@ -39,7 +39,9 @@
 $! for their presence and use the homegrown iconv() if necessary.
 $!
 $ IF F$SEARCH("SYS$I18N_ICONV:UCS-2_ISO8859-1.ICONV") .NES. "" -
-    .AND. F$SEARCH("SYS$I18N_ICONV:ISO8859-1_UCS-2.ICONV") .NES. ""
+    .AND. F$SEARCH("SYS$I18N_ICONV:ISO8859-1_UCS-2.ICONV") .NES. "" -
+    .AND. F$SEARCH("SYS$I18N_ICONV:UTF-8_ISO8859-1.ICONV") .NES. "" -
+    .AND. F$SEARCH("SYS$I18N_ICONV:ISO8859-1_UTF-8.ICONV") .NES. ""
 $ THEN
 $   d_have_iconv = "1"
 $   SAY "Using system-supplied iconv()"