On Thu, Oct 25, 2001 at 12:13:04AM +0200, Adrian Bunk wrote: > On Tue, 23 Oct 2001, Thomas Dickey wrote: > > at the moment I can't factor out the different things (gettext/iconv). > > > > The UTF-8 part is the most suspect, since lynx is producing that itself. If > > autoconf is the only issue (and if the newer gettext is dependent on autoconf > >... > > Let me try to explain it: > - The problem only seems to occur with the translated gettext messages. > - The new gettext does character set conversion using iconv (3).
so it might be one or both. > - gettext doesn't need a more recent autoconf but I do only have unpatched > autoconf-2.13 and autoconf-2.52 installed and none of them works with > lynx... you can always install a different version of autoconf (to co-exist with packages that depend on autoconf 2.5x, I install my patched version with a different program-prefix, for instance). None of the makefiles I write calls configure (since I haven't seen any that do it right ;-) btw, installing an autoconf with different program-prefix: autoconf 2.13 (and 2.5x when I last looked) don't rename the library directory to match, so that's a potential conflict. But installing into /usr/local/ doesn't conflict with an autoconf in /usr. Anyway - both my newer Slackware's have libiconv, the Mandrake 8.1 has workable (perhaps) UTF-8 support in glibc. I've looked a little at the Debian unstable, but not seen UTF-8 working properly (but that's partly a matter of how I'm configured - I usually run that remotely, and if I'm running Debian stable on the front don't have fonts for it). But I'm not planning to do any system installs for a little while (not even Redhat ;-). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
