This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: Updated: xterm-238-1
- From: Thomas Wolff <mined at towo dot net>
- To: <neomjp at yahoo dot co dot jp>
- To: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: Thomas Dickey <dickey at his dot com>
- Cc: cygwin-xfree at cygwin dot com
- Date: Mon, 23 Feb 2009 11:12:03 +0100 (CET)
- Subject: Re: Updated: xterm-238-1
- Reply-to: cygwin-xfree at cygwin dot com
> On 2009/02/20 20:24, Thomas Wolff wrote:
> > please add the following configure options to the xterm package:
> >
> > --enable-wide-chars to provide a UTF-8 environment for applications that need to use it
> >
> > --enable-256-color
> Both options are already enabled in xterm-238-1.
> (Try installing the xterm-238-1 source package and see
> /usr/src/xterm-238-1.cygport .)
> For more information on how to enable utf8 resource, see
> http://sourceware.org/ml/cygwin-xfree/2008-12/msg00079.html
I see, thanks. This makes it a little troublesome to invoke xterm
in enforced UTF-8 mode in a portable way, since on some other systems,
+lc is not supported or -en UTF-8 doesn't even start the xterm (blinks up
and terminates on my Linux system).
Anyway, checking this I noticed one other problem:
On cygwin, the uxterm script (which is supposed to invoke xterm and
ensure UTF-8 mode) actually invokes:
LC_CTYPE=en_US.UTF-8 xterm.exe -class UXTerm -title uxterm -u8
But xterm is configured on cygwin so that
xterm -u8 has no effect but
xterm +lc -u8 is needed (for whatever reason) to enforce UTF-8 support
The effect is that the xterm started with uxterm on cygwin has the same
bug as LC_CTYPE=en_US.UTF-8 xterm +u8 on other systems:
Output is 8-bit, input is UTF-8.
-------------
Kind regards,
Thomas
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/