[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gnu-libiconv] Solaris libiconv vs. GNU libiconv in terms of 646

From: Bruno Haible
Subject: Re: [bug-gnu-libiconv] Solaris libiconv vs. GNU libiconv in terms of 646
Date: Thu, 3 Apr 2008 20:19:22 +0200
User-agent: KMail/1.5.4

Dagobert Michelsen wrote:
> >> It looks like Solaris uses 646 as standard which is
> >> known to Solaris libiconv but not GNU libiconv.
> >
> > This situation has been addressed in full generality - there is not only
> > Solaris and "646", there is also HP-UX and "hp15CN", and many others -
> > in the gnulib module 'iconv_open', here:
> As I understand it there should be an encodings_solaris.def similar
> to the files for osf1 and aix with the mappings from charset.alias
> or am I getting something completely wrong here?

If you try to make all software understand the nonstandard encoding names that
Solaris uses, then you have a lot to do. It's ranging from libiconv (where
modifying the encodings*.def files would be the way to go, as you say) over
mutt up to X11.

It is more promising and less work to make all software support and use the
*standard* encoding names. Not "646", but "ASCII" or "US-ASCII". To this
effect, use
  - gnulib's module localcharset instead of nl_langinfo(CODESET),
  - gnulib's module iconv_open (as wrapper around the iconv_open from the
    system or from GNU libiconv).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]