Re: rxvt, ssh and utf8 - partial success

2004-06-07 Thread Olaf Föllinger
On Sun, Jun 06, 2004 at 12:53:27PM +0200, Baurjan Ismagulov wrote: > Hello, James, > > On Sat, Jun 05, 2004 at 09:21:57PM -0500, James Garrison wrote: > > >>Handling this in rxvt should solve your problem (I wonder if there are > > >>any reasons not to do that). > > This was actually an answer to

Re: rxvt, ssh and utf8 - partial success

2004-06-06 Thread Joshua Daniel Franklin
On Sun, 06 Jun 2004 13:27:40 -0500, James Garrison wrote: > Looks like the simplest > solution is just to switch to en_US locale unless I really need > Unicode for something. This is, by the way, a generic rxvt problem unrelated to Cygwin. I have to export LANG=en_US when I use rxvt on RHEL too.

Re: rxvt, ssh and utf8 - partial success

2004-06-06 Thread James Garrison
Baurjan Ismagulov wrote: Hello, James, On Sat, Jun 05, 2004 at 09:21:57PM -0500, James Garrison wrote: [snip] About ascii instead of Unicode... How do you conclude that the program (which one?) was sending Unicode sequences before using rxvt-cygwin (=> what is your locale?). The program is redhat-s

Re: rxvt, ssh and utf8 - partial success

2004-06-06 Thread Baurjan Ismagulov
Hello, James, On Sat, Jun 05, 2004 at 09:21:57PM -0500, James Garrison wrote: > >>Handling this in rxvt should solve your problem (I wonder if there are > >>any reasons not to do that). This was actually an answer to Brian, who wanted to have a single terminal type for one application (and I shar

Re: rxvt, ssh and utf8 - partial success

2004-06-05 Thread James Garrison
James Garrison wrote: Baurjan Ismagulov wrote: On Fri, Jun 04, 2004 at 10:19:01AM -0700, Brian Dessent wrote: I'd love to know why one or the other terminal setting can't just work for everything. This happens due to the following difference in the terminfo entries: -acsc=``aaffggjjkkllmmnnoop

Re: rxvt, ssh and utf8

2004-06-05 Thread James Garrison
Baurjan Ismagulov wrote: On Fri, Jun 04, 2004 at 10:19:01AM -0700, Brian Dessent wrote: I'd love to know why one or the other terminal setting can't just work for everything. This happens due to the following difference in the terminfo entries: - acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyy

Re: rxvt, ssh and utf8

2004-06-05 Thread Baurjan Ismagulov
On Fri, Jun 04, 2004 at 10:19:01AM -0700, Brian Dessent wrote: > I'd love to know why one or the other terminal setting can't just work > for everything. This happens due to the following difference in the terminfo entries: - acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, +

Re: rxvt, ssh and utf8

2004-06-04 Thread Brian Dessent
James Garrison wrote: > So, DOES the rxvt in Cygwin support UTF8? If yes, how do I > enable it (There's nothing in the man page). Well I don't know about Unicode box/line drawing characters but I've always found that applications that expect to use the line drawing characters (such as mc) only w

rxvt, ssh and utf8

2004-06-04 Thread James Garrison
I'm using rxvt to open an SSH session to a RedHat Enterprise Linux system. On that system I want to run an ansi-based app that happens to use Unicode UTF8 encoding for box-drawing characters. I can't seem to get rxvt to correctly interpret the UTF8. It just displays the 3-byte UTF8 sequences as th