Re: X11 in Leopard: xterm on start-up
Re: X11 in Leopard: xterm on start-up
- Subject: Re: X11 in Leopard: xterm on start-up
- From: Eric Gouriou <email@hidden>
- Date: Sun, 28 Oct 2007 20:51:46 -0700
On Oct 28, 2007, at 3:25 PM, B. Ludvigsen wrote:
It has to be (u)xterm because it is the only terminal we have(had)
that handles utf-8 correctly end-to-end in both the shell (on the
command line) and in local and remote applications that don't generate
their own windows.
For example:
- the emacs that comes with Tiger or Leopard runs only in an xterm
window. In order to encode utf-8 correctly it needs to run in a
uxterm. Now that doesn't work.
- when I log on to a machine at my university in Beirut (I work
there part time but live in Norway) which is behind firewalls and
other barricades, there is no way an X11 application is going to
show its own pretty face here. But I still want utf-8 to work - I
will often be working with various Latin scripts and Arabic in one
and the same file.
Having worked this far I just don't see any good reason why it
shouldn't work again. Terminal.app doesn't just doesn't do it. Don't
the people who make this stuff realize that there's a world beyond
ASCII?
Terminal in Leopard runs in UTF8 by default and declares itself to be
a xterm variant:
...
LANG=en_US.UTF-8
TERM=xterm-color
...
So most programs that deal with a xterm in UTF-8 should be well
fooled by
Leopard's Terminal. I can enter non-ASCII characters in the built-in
emacs
without any issue.
What's broken ?
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden