From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Tue Apr 09 2002 - 06:28:24 EDT
http://bugzilla.abisource.com/show_bug.cgi?id=1101
> ------- Additional Comments From dbolack@dnai.com
> 2002-04-09 03:07 -------
> Under Solaris 9 this appears to work. I get no ill
> behaviour. I will attempt it
> on 8 when I get home.
Can somebody please grep our source code to see if
the string "ISO-8859-1" (or similar) is ever being
passed to iconv directly? If it is we will have an
even more subtle Solaris iconv bug. If this does
happen we need a new function in the EncodingManager
to get the "real name" of this encoding. I have
placed similar functions there already to resolve the
same problem with "UCS-2" encoding which uses
different
names on different iconvs.
Ideally, our UT_Iconv should take an enum. The only
literal string it's safe to pass to every iconv out
there is probably "ASCII" and I wouldn't even put
money on that one!
Also I'd like to make the iconv sniffing currently in
EncodingManager part of the build process to ease code
bloat. We could still ship binaries with the sniffing
in Abi to make sure one Abi executable will work on
any
system. Solaris appears to have an API or tool to
enumerate the encodings their iconv supports and the
sniffer should use this. Should I file this rambling
as a bug/rfe?
Andrew Dunbar.
=====
http://linguaphile.sourceforge.net http://www.abisource.com
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
This archive was generated by hypermail 2.1.4 : Tue Apr 09 2002 - 11:28:53 EDT