Subject: Re: IceWM 1.2.7 execution problem (iconv not up-to-date ?)
To: None <tech-pkg@netbsd.org>
From: R. Braun <syn@sceen.net>
List: tech-pkg
Date: 01/13/2004 16:01:15
--HcAYCG3uE/tztfnV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 12, 2004 at 09:58:58PM -0800, Jeremy C. Reed wrote:
> > IceWM: iconv doesn't supply (sufficient) 646 to Unicode converters.
>=20
> I was told on the gnu.org bug-gnu-libiconv that "646" is not a valid
> encoding name.
>=20
> I was told to fix NetBSD to return a valid encoding name (such
> as "ASCII", "US-ASCII" or "ANSI_X3.4-1968") instead.
>=20
> 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?
>=20
> 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.)
>=20
>    Jeremy C. Reed
>    http://bsd.reedmedia.net/
>=20
> p.s. This is regarding PR #23979 too.
>=20
>=20

If I recall correctly, NetBSD-current has its own libiconv library integrat=
ed
into the base system, whereas NetBSD-1.6 installs it from pkgsrc. Correct m=
e if
I'm wrong but it should be the reason why libiconv implies those problems o=
nly
on NetBSD-1.6.

--=20
R. Braun

--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFABAg6PEHFMcoF1vIRApUuAJ4mVbcG1tLt3FWmJZK1+P6/PFCXQQCfQlPa
ojv8uFS0/IiYgSXLMkywE1M=
=vXAE
-----END PGP SIGNATURE-----

--HcAYCG3uE/tztfnV--