Subject: [sup-talk] ISO 8859-15 at the header

From: [email-masked] (Carsten Schölzki)
Date: Thu, 27 Mar 2008 05:49:02 +0100

Hi,

I started trying sup today and it seems to be wonderful for me. Till
now I'm a mutt user for over 10 years - but know I found a reason to
change...

But there is a little problem with the header-encoding. Seems, that
sup doesn't de- or encode ISO 8859-15 correct.

There are no problems with the body or with ISO 8859-1 in the
header.

Did I messed up some settings or is this bug?

I'm using sup v0.4 on MacOS X 10.5.2. - encoding in mutt works fine.

Thanks, Carsten

---

From: [email-masked] (William Morgan)
Date: Wed, 02 Apr 2008 18:12:40 -0700

> There are no problems with the body or with ISO 8859-1 in the

It should work, if you have your LANG and stuff all set up correctly.
What console character set encoding does Sup detect? (Typically the
first message of the log buffer.)

-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Carsten Schölzki)
Date: Thu, 3 Apr 2008 16:07:11 +0200

> first message of the log buffer.)

The detecting seems right to me. The log says:
using character set encoding "ISO8859-15"

---

From: [email-masked] (William Morgan)
Date: Sat, 05 Apr 2008 16:35:13 -0700

Reformatted excerpts from Carsten Sch?lzki's message of 2008-04-03:
> > It should work, if you have your LANG and stuff all set up
> > correctly.  What console character set encoding does Sup detect?
> > (Typically the first message of the log buffer.)
> 
> The detecting seems right to me. The log says: using character set
> encoding "ISO8859-15"

This means that as far as Sup can tell, it can emit iso8859-15 directly
to the terminal and not have to worry about transcoding anything. Does
that seem correct?

If so, then this may bring us to the very scary world of "why isn't
ncurses does the right thing on my particular
platform/terminal/encoding setup".