* On Apr 03, Sven Guckes [[EMAIL PROTECTED]] wrote:
> i dont' the value in this iconv thing. i just seems
> to get in the way.. does anyone use it successfully?
* Jeremy Blosser <[EMAIL PROTECTED]> [2002-04-03 15:46]:
> Er, my understanding* is that all the internal support for extended
> characters has been dropped in favor of letting libiconv handle it,
> so no, being able to build without libiconv isn't going to help him.
>
> The point of being able to build without it is for people on
> very old systems that don't (want|need|have) it. For anyone
> else it seems to have been working fine for some time now.
well, so far i never really cared, but..
at some point this just stopped working.
now i am forced to find out what mutt does
differently even though it had worked before.
as far to know the system here has not changed.
but how do i make sure about that?
where to start? what to check?
let's see what the configure script says:
guckes@ritz:~/install/mutt-1.3.28> ./configure --help|grep icon
--with-libiconv-prefix=DIR search for libiconv in DIR/include and DIR/lib
so there is something you *can* set. but -
what is the default for this DIR on Solaris?
how can i test whether this is "good"?
here is some info about this system:
$ uname -a
SunOS ritz 5.8 Generic_108528-13 sun4u sparc
what else do you need to know?
i just want to know what the cause is -
the setup of our system - or mutt.
i find it *very* weird that text is screwed
when show with mutt - but when I reply to a
message or pipe it to "vim -" then it's fine.
so i'd expect mutt to show it alright, too.
am i asking too much here?
Sven [starting a new thread by deleting the IRT]
