Hi, Paolo,
The iconv implementation in Solaris libc, is not compatible with
gnu-iconv. In your case, you could either link your app with
libgnu-iconv when you building your application, or use the preloading way.
Ienup is planning and leading a effort to improve the iconv
compatibilities, refer to
http://wikis.sun.com/display/g11n/Programs+Projects, and I also copied
the section as following,
(J) GNU libiconv compatible libc iconv
We have some differences that are not supported by our iconv if we
compare with GNU libiconv, esp., support of empty encoding "" name and
"//TRANSLIT" and "//IGNORE" options at tocode of iconv_open(3C), the
lack of iconvctl(3C) API, and lack of code conversions between some
Asian major codesets and UTF-16* and UTF-32* forms. These issues cause
incompatibility issues reported in various bug reports. See also
6803313, 6827647, and 6803313.
Regards,
On 4/24/09 2:52 AM, Jan Hnatek wrote:
Adding i18n-discuss.
hnhn
Paolo Brandoli wrote:
Hi,
I have an application that runs fine under linux, but when recompiled
on OpenSolaris using SunStudio cannot initialize an ICONV with
destination charset=ASCII//IGNORE and source charset=UTF-32LE.
The opposite (ascii to utf) initializes correctly.
I've seen this discussion:
http://woss.name/2008/10/16/edge-rails-pre-22-iconv-transliteration-and-solaris/
Is this an issue in OpenSolaris? Should I file a bug for this, or is
it an intended behaviour?
BR
Paolo Brandoli
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
