On 2009-05-04, Lucio Chiappetti <lu...@lambrate.inaf.it> wrote:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
>
> ---40151024-1298054523-1241441543=:18813
> Content-Type: TEXT/PLAIN; FORMAT=flowed; CHARSET=US-ASCII
> Content-ID: <alpine.lsu.2.00.0905041455361.18...@cbfrvqba.ynzoengr.vans.vg>
>
> My apologies if this is (partially ?) off-topic for this list.
>
> I was trying to sort out UTF-8 support for the mail client "alpine", using
> the test page http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
> (very nice). I have copied this to a local file, which I just "cat".
>
> I was redirected also to the equally nice documentation page
> http://www.cl.cam.ac.uk/~mgk25/unicode.html#xterm
>
> While the answer for my case is clear (I run alpine in an rxvt which I
> start from .fvwm2rc and rxvt has NO UTF-8 support, so I'll have to sort
> that out otherwise), I am puzzled by the xterm behaviour.
>
> I use various xterms, both for local and remote use, and both started from
> a fvwm menu or from the shell, and I'm experiencing controversial
> behaviour.
>
> For all tests, environment: fvwm 2.5.10 under Suse 9.2
>
>
> A) local xterm started from menu via a plain Exec xterm
>
> this invokes a very simple resource file ~/XTerm (attached)
> the resulting shell has NO LC_CTYPE variable set
> the resulting xterm has UTF mode on though dimmed (control-MB3)
> UTF support works perfectly (well, with default font it does not
> display Amharic text, who cares, but with "Unicode best" it does)
>
Is LANG set? What is the output of the "locale" command? The LC_*
variables can be set individually to override defaults such as date
format or collating sequence. I don't know why LC_CTYPE would be set
as root but not as a normal user.
