* El 11/05/09 a las 1:04, Derek Martin chamullaba:
> On Thu, May 07, 2009 at 09:40:00PM -0300, Luis A. Florit wrote:
> > 1) why ?charset=utf-8 if I am working in a ISO-8859-1 xterm?
>
> How do you know that the xterm *is* ISO-8859-1?
This is what I said in my last email:
Good question... :o) I wrote that because of three reasons,
but maybe I am still wrong. Let's see:
1) The xterm has a drop-down menu where you can choose the encoding.
I set this as ISO-8859-1.
2) When I switch to UTF-8 in this drop-down menu, I see accents in
mutt and UTF-8 files correctly.
3) Vim works fine with this config, exactly as in my ISO-8859-1 Fedora
rxvt/xterm. And other commands like cat over ISO-8859-1 files work
equally well.
However, I just discovered something different.
It does seems that my maemo ISO-8859-1 xterm is a fake one.
As I said, VIM works just fine. However, when opening a ISO-8859-1
file, it prints '[converted]' in the status bottom line.
I googled for it, and that is printed when the file does not match the
charset given by your locale. So VIM is converting my ISO-8859-1
file into a UTF-8 one (':set fileencoding' gives me 'fileencoding=UTF-8'
in maemo, while in Fedora rxvt/xterm gives me 'fileencoding=').
Then, it seems that mutt understands my mameo xterm as an UTF-8, and
ignores the xterm drop-down menu setting. Or that my xterm is not
converting back the mutt UTF-8 output into this fake ISO-8859-1.
Does all this make any sense??
Thanks once again,
L.
