Re: UTF-8-problems; more tolerance for invalid charsets

> First of all, you'll run into problems reading postings with missing
> charset declarations containing umlauts, make sure you have at least
> my fallback_charset patch installed.

Thanks, the header view is much more readable now, while the messages still look the same

> As you are using a Mac, do you have libiconv installed? 

I'll check later on. I've seen ./configure options here, but no hint in the doc what to use.


> If I
> remember correctly, the iconv support in OSX is not included in
> libc like it is in Linux. If your slrn is not compiled against
> libiconv I don't think it will work very good with *any* charset
> other than *us-ascii*.

Since it does work very well in properly defined charsets, I guessed that this behaviour would be ok. I see the same behaviour on linux where you expect that it would be included by default.

> Are you running slrn in a UTF-8 terminal? 

Yes.

> slrn detects the termencoding from the locale settings? 

I hope so:  LANG=en_US.UTF-8
etc. for all the LC_*, but LC_ALL is undefined.


> The locale settings can be
> overridden by the undocumented config option "charset Display".
> Set this to "iso-8859-15" or "utf-8" depending on you terminal
> capabilities.

Oops - are there many more undocumented config options?

Thanks,
Martin

-- 

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/