Re: French accentuated letters in 1.3.28i - stable snapshot
* On 2002.04.03, in [EMAIL PROTECTED], * Simon White [EMAIL PROTECTED] wrote: 03-Apr-02 at 16:47, Sven Guckes ([EMAIL PROTECTED]) wrote : but maybe it's just that our Solaris machines don't have proper locales installed. actually, the local installation drives me up the wall. this alone it's a good reason to switch to Linux. We run Linux on Sparc boxes and are happier with them than when they ran SunOS5.8. I run Solaris on my PC and am much happier with it than when it ran Linux. But OS advocacy doesn't address mutt questions. Chersets work fine on Solaris 8, with Sun's iconv, even, last time I checked. Unfortunately, I can't investigate this further at the moment, as I don't use 8 any longer. But I have had success, for what that's worth. (I'm not aware of any problems with iconv or locales on Solaris 8. Some charset names differ in Solaris from Linux, but I believe those have been accomodated with aliases, as they're not broken, just different.) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: French accentuated letters in 1.3.28i - stable snapshot
* Charles Gagnon [EMAIL PROTECTED] [2002-04-03 14:30]: .. I cannot get mutt-1.3.x to process and display french accentuated letters properly since the support for iconv was introduced. [..] But I compiled libiconv-1.7 and then compiled mutt-1.3.28i and I can't get it to display those accentuated properly. I always end-up with ?, spaces or \009 codes. I added: source /usr/local/doc/mutt/samples/iconv/iconv.solaris-2.7.rc I am running on a Solaris 2.8 system but I couldn't see the solaris-2.8 file anywhere. Any ideas? welcome to the MOSU club (Mutt on Solaris Users). today the no-iconv patch has been added - and I'll try again tomorrow when Thomas Roessler will upload the current snapshots. maybe then it'll work? i hope so. as a matter of fact i dont' the value in this iconv thing. i just seems to get in the way.. does anyone use it successfully? but maybe it's just that our Solaris machines don't have proper locales installed. actually, the local installation drives me up the wall. this alone it's a good reason to switch to Linux. Sven [Been there, done that, got the tshirt.]
Re: French accentuated letters in 1.3.28i - stable snapshot
03-Apr-02 at 16:47, Sven Guckes ([EMAIL PROTECTED]) wrote : but maybe it's just that our Solaris machines don't have proper locales installed. actually, the local installation drives me up the wall. this alone it's a good reason to switch to Linux. We run Linux on Sparc boxes and are happier with them than when they ran SunOS5.8. Simon -- [Simon White. vim/mutt. [EMAIL PROTECTED] GIMPS:61.24% see www.mersenne.org] Man will never be free until the last king is strangled with the entrails of the last priest. -- Diderot [Linux user #170823 http://counter.li.org. Home cooked signature rotator.]
Re: French accentuated letters in 1.3.28i - stable snapshot
On Apr 03, Sven Guckes [[EMAIL PROTECTED]] wrote: * Charles Gagnon [EMAIL PROTECTED] [2002-04-03 14:30]: .. I cannot get mutt-1.3.x to process and display french accentuated letters properly since the support for iconv was introduced. [..] But I compiled libiconv-1.7 and then compiled mutt-1.3.28i and I can't get it to display those accentuated properly. I always end-up with ?, spaces or \009 codes. I added: source /usr/local/doc/mutt/samples/iconv/iconv.solaris-2.7.rc I am running on a Solaris 2.8 system but I couldn't see the solaris-2.8 file anywhere. Any ideas? today the no-iconv patch has been added - and I'll try again tomorrow when Thomas Roessler will upload the current snapshots. maybe then it'll work? i hope so. as a matter of fact i dont' the value in this iconv thing. i just seems to get in the way.. does anyone use it successfully? 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. *Very likely flawed or incomplete, since I don't need to deal with it and remain mostly blissfully ignorant on this issue. msg26595/pgp0.pgp Description: PGP signature
