Re: xterm(229-1) does not accept "-u8"
Hi, I read at http://cygwin.com/ml/cygwin-xfree/2007-08/threads.html#00068 that support for the -u8 option was dropped from newer versions of xterm for cygwin. I'd like to vote for keeping this option, it's quite useful to me, as it allows me to read my mail in mutt over ssh without the screen getting mangled :). Arnout -- 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/
Re: xterm(229-1) does not accept "-u8"
> Poor Yorick wrote: > > Yongwei wrote: > > #!/bin/sh > > LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb > > "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" -e > > bash $@ & > > > > Double quotes around the "$@" variable will ensure that positional > variables are passed into the second shell undisturbed: > > #!/bin/sh > LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb > "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" -e > bash "$@" & I am sorry to send the wrong code. The `-e bash' was added when I tried to figure out what went wrong (perhaps the -u8 not working issue, but I do not remember exactly). It does not work as intended. The purpose of $@ here is to pass special xterm flags like `-cjk'. The script should be: #!/bin/sh LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" $@ & Thanks for giving hints, anyway. Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/ -- 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/
Re: xterm(229-1) does not accept "-u8"
> From: Yongwei Wu <[EMAIL PROTECTED]> > Subject: Re: xterm(229-1) does not accept "-u8" > Sent: 2007-08-27 14:01 > is enough to do much, like viewing multi-byte documents in Vim. I use > this script to start a UTF-8 XTerm: > > #!/bin/sh > LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb > "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" -e > bash $@ & > Double quotes around the "$@" variable will ensure that positional variables are passed into the second shell undisturbed: #!/bin/sh LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" -e bash "$@" & -- Poor Yorick -- 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/
Re: xterm(229-1) does not accept "-u8"
neomjp wrote: > I will be glad if UTF-8 support is turned back on again, > maybe in future updates. I would like to echo neomjp's request. The Unicode support in xterm is enough to do much, like viewing multi-byte documents in Vim. I use this script to start a UTF-8 XTerm: #!/bin/sh LC_CTYPE=en_US.UTF-8 xterm -u8 -fn "*-medium-*--18-*-iso10646-1" -fb "*-bold-*--18-*-iso10646-1" -fw "*-medium-*-ja-18-*-iso10646-1" -e bash $@ & And Latin1 characters, Japanese characters, and most Chinese characters can be displayed correctly. Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/ -- 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/
Re: xterm(229-1) does not accept "-u8"
On Fri, 24 Aug 2007, neomjp wrote: I understand that cygwin has limited support for locale, but even so, many small utilities in cygwin packages can work with UTF-8, such as sed, awk, perl, ruby, grep, cat, head, tail, less(with LESSCHARSET="utf-8") and so on. These are the things used very often inside xterm, and that is when "-u8" is needed. I will be glad if UTF-8 support is turned back on again, maybe in future updates. That's up to the (non-existent) Cygwin-X maintainer. It's not hard to compile your own copy of xterm however (it's one of the platforms that I usually test-compile on a new patch). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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/
Re: xterm(229-1) does not accept "-u8"
On 2007/08/23 19:56, Thomas Dickey wrote: > yes (but even if it's built to support UTF-8, cygwin has very limited > locale support - no UTF-8, except as noted a while back, applications > that have built-in locale support such as mined will work). Thank you for confirming this, Thomas. I read an debian-x thread, Bug#341686: xterm cannot be started in utf-8 mode by default http://lists.debian.org/debian-x/2005/12/msg00044.html in which you discussed this xterm locale issue, "xterm -xrm '*locale:false' -u8", and mined. I understand that cygwin has limited support for locale, but even so, many small utilities in cygwin packages can work with UTF-8, such as sed, awk, perl, ruby, grep, cat, head, tail, less(with LESSCHARSET="utf-8") and so on. These are the things used very often inside xterm, and that is when "-u8" is needed. I will be glad if UTF-8 support is turned back on again, maybe in future updates. -- neomjp -- Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar http://pr.mail.yahoo.co.jp/toolbar/ -- 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/
Re: xterm(229-1) does not accept "-u8"
On Thu, 23 Aug 2007, neomjp wrote: Similar problem was reported before for xterm-185-2, and the cause was that --enable-wide-chars was not used at the configuration step. (http://cygwin.com/ml/cygwin-xfree/2004-03/msg00616.html) I wonder if it is also the case this time. yes (but even if it's built to support UTF-8, cygwin has very limited locale support - no UTF-8, except as noted a while back, applications that have built-in locale support such as mined will work). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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/
xterm(229-1) does not accept "-u8"
The newly uploaded xterm(229-1) prematurely exits when the command line
option "-u8" is given, saying:
-
$ xterm -u8 &
[1] 2932
xterm: bad command line option "-u8"
usage: xterm [...
..
Type xterm -help for a full description.
-
"-u8" is not listed in the output of "xterm -help", either.
("-u8" is surely described in man page.)
"-u8" used to work in xterm(202-1) and was also
listed in "xterm -help".
Similar problem was reported before for xterm-185-2,
and the cause was that --enable-wide-chars was not used at
the configuration step.
(http://cygwin.com/ml/cygwin-xfree/2004-03/msg00616.html)
I wonder if it is also the case this time.
--
neomjp
--
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/
