Subject: Re: IceWM 1.2.7 execution problem (iconv not up-to-date ?)
To: None <email@example.com>
From: R. Braun <firstname.lastname@example.org>
Date: 01/13/2004 16:01:15
Content-Type: text/plain; charset=us-ascii
On Mon, Jan 12, 2004 at 09:58:58PM -0800, Jeremy C. Reed wrote:
> > IceWM: iconv doesn't supply (sufficient) 646 to Unicode converters.
> I was told on the gnu.org bug-gnu-libiconv that "646" is not a valid
> encoding name.
> I was told to fix NetBSD to return a valid encoding name (such
> as "ASCII", "US-ASCII" or "ANSI_X3.4-1968") instead.
> This was with NetBSD-1.6.x, so I don't understand that, because I thought
> this was defined in GNU libiconv itself. Who knows about this?
> Or I was told to fix icewm to perform the necessary conversion from "646"
> to "ASCII". (And a converter is available in the libiconv/libcharset
> directory as an example.)
> Jeremy C. Reed
> p.s. This is regarding PR #23979 too.
If I recall correctly, NetBSD-current has its own libiconv library integrat=
into the base system, whereas NetBSD-1.6 installs it from pkgsrc. Correct m=
I'm wrong but it should be the reason why libiconv implies those problems o=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----