* [sup-talk] ISO 8859-15 at the header
@ 2008-03-27 4:49 Carsten Schölzki
2008-04-03 1:12 ` William Morgan
0 siblings, 1 reply; 4+ messages in thread
From: Carsten Schölzki @ 2008-03-27 4:49 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] ISO 8859-15 at the header
2008-03-27 4:49 [sup-talk] ISO 8859-15 at the header Carsten Schölzki
@ 2008-04-03 1:12 ` William Morgan
2008-04-03 14:07 ` Carsten Schölzki
0 siblings, 1 reply; 4+ messages in thread
From: William Morgan @ 2008-04-03 1:12 UTC (permalink / raw)
Reformatted excerpts from Carsten Sch?lzki's message of 2008-03-26:
> 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.
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>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] ISO 8859-15 at the header
2008-04-03 1:12 ` William Morgan
@ 2008-04-03 14:07 ` Carsten Schölzki
2008-04-05 23:35 ` William Morgan
0 siblings, 1 reply; 4+ messages in thread
From: Carsten Schölzki @ 2008-04-03 14:07 UTC (permalink / raw)
William Morgan <wmorgan-sup at masanjin.net> [03.04.2008 03:12]:
> Reformatted excerpts from Carsten Sch?lzki's message of 2008-03-26:
> > 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.
>
> 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"
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] ISO 8859-15 at the header
2008-04-03 14:07 ` Carsten Schölzki
@ 2008-04-05 23:35 ` William Morgan
0 siblings, 0 replies; 4+ messages in thread
From: William Morgan @ 2008-04-05 23:35 UTC (permalink / raw)
Reformatted excerpts from Carsten Sch?lzki's message of 2008-04-03:
> William Morgan <wmorgan-sup at masanjin.net> [03.04.2008 03:12]:
> > 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".
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-04-05 23:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-27 4:49 [sup-talk] ISO 8859-15 at the header Carsten Schölzki
2008-04-03 1:12 ` William Morgan
2008-04-03 14:07 ` Carsten Schölzki
2008-04-05 23:35 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox