You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
(9) |
Jun
(8) |
Jul
(10) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Hin-Tak L. <hin...@ya...> - 2005-04-15 11:00:39
|
cxterm pre-dates all the XIM and LC-type efforts - don't do the lctype/xim declarations... press f3 to change input method. liu jiachang wrote: > 环境: > freebsd 5.3-release, gnome2.10.0, zh-fcitx-3.1, > zh-cxterm-5.0.3, csh > > (其中gnome, zh-fcitx, zh-cxterm都是通过ports安装) > > 在doc的cxterm.faq虽可以见到如下的问答: > > 5.8 I cannot input or output Chinese in the shell > prompt -- what I got is > two random ASCII characters instead of a Chinese > character. > > Csh, sh, ksh usually don't have this problem. But be > careful of the > name of the shell, for example in Linux, csh > actually means tcsh and > sh means bash. > > Some system (or your shell startup file, e.g. > .cshrc or .login) set the > tty to strip the 8th bit. You can reset it by > typing "stty pass8". > (Different systems may have different stty format. > Read stty(1) manual > for help. Some possible stty options are "pass8", > "cs8", "-istrip", > "-parenb", etc.) > > 但我的情况是,在x window中使用CXterm或者cxterm > -GB可以通过“fx”转换各种中文输入法或者英文输入法。如在五笔输入状态下,窗口的下端虽可以显示汉字的选取,但汉字无法显示在窗口(光标不会位移)。有时乱按各键之下,可以在中文输入状态下见到有ascii码的出现。 > > 尝试在网上搜索,但还是无法解决问题。 > > 谢谢解答。 > > 附: > .xinitrc部分配置 > export LC_CTYPE=ZH_CN.GBK > export XMODIFIERS @im=fcitx > fcitx& > > > _________________________________________________________ > Do You Yahoo!? > 150万曲MP3疯狂搜,带您闯入音乐殿堂 > http://music.yisou.com/ > 美女明星应有尽有,搜遍美图、艳图和酷图 > http://image.yisou.com > 1G就是1000兆,雅虎电邮自助扩容! > http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/ > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel > |
From: liu j. <ljc...@ya...> - 2005-04-15 08:39:05
|
环境: freebsd 5.3-release, gnome2.10.0, zh-fcitx-3.1, zh-cxterm-5.0.3, csh (其中gnome, zh-fcitx, zh-cxterm都是通过ports安装) 在doc的cxterm.faq虽可以见到如下的问答: 5.8 I cannot input or output Chinese in the shell prompt -- what I got is two random ASCII characters instead of a Chinese character. Csh, sh, ksh usually don't have this problem. But be careful of the name of the shell, for example in Linux, csh actually means tcsh and sh means bash. Some system (or your shell startup file, e.g. .cshrc or .login) set the tty to strip the 8th bit. You can reset it by typing "stty pass8". (Different systems may have different stty format. Read stty(1) manual for help. Some possible stty options are "pass8", "cs8", "-istrip", "-parenb", etc.) 但我的情况是,在x window中使用CXterm或者cxterm -GB可以通过“fx”转换各种中文输入法或者英文输入法。如在五笔输入状态下,窗口的下端虽可以显示汉字的选取,但汉字无法显示在窗口(光标不会位移)。有时乱按各键之下,可以在中文输入状态下见到有ascii码的出现。 尝试在网上搜索,但还是无法解决问题。 谢谢解答。 附: .xinitrc部分配置 export LC_CTYPE=ZH_CN.GBK export XMODIFIERS @im=fcitx fcitx& _________________________________________________________ Do You Yahoo!? 150万曲MP3疯狂搜,带您闯入音乐殿堂 http://music.yisou.com/ 美女明星应有尽有,搜遍美图、艳图和酷图 http://image.yisou.com 1G就是1000兆,雅虎电邮自助扩容! http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/ |
From: Hin-Tak L. <hin...@ya...> - 2005-01-21 16:56:08
|
It is as the message said: check the font directory permission, check that it has a fonts.dir, and check your font server address and syntax. It is the last one. cxterm was written a long time before font server became popular. RH9 ships a font server as default, and you need to add /usr/X11R6/share/cxterm/fonts/ to the font server's font path. It is somewhere under /etc/X11 - "man xfs" (=X font server) for details. Yes, I did use cxterm in the big5 personally under RH9 until last summer so I know it works. (I have since upgrade to fedora 2 and then fedora 3, and cxterm works fine there also with both GB and Big5. If you have been to our project web site, you'd know I had a bit of problem with fedora 2 and needed to port the unix98 change from xterm main to cxterm, and you'd need that if you upgrade). Franky Lau wrote: > Hi All, > i have installed cxterm 5.2.3 in my RH9 machine, it works fine with GB. however when i use "cxterm -b5", it give the following errors. > > [root@rh9 www]# cxterm -b5 > xset: bad font path element (#58), possible causes are: > Directory does not exist or has wrong permissions > Directory missing fonts.dir > Incorrect font server address or syntax > cxtermb5: unable to open font "hku16et", trying "cclib16st".... > cxtermb5: unable to locate a suitable Chinese font > > i have run "make install-fonts", and i found a new directory created in /usr/X11R6/share/cxterm/fonts/ > but when i type "xlsfonts | grep hk", nothing return. > and when find BG font, "xlsfonts | grep gb" > it return : > -isas-fangsong ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 > -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 > -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 > -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 > -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 > hanzigb16fs > hanzigb16st > hanzigb24st > > what's wrong? Anyone can help me? > > thx a lot |
From: Franky L. <fr...@ca...> - 2005-01-21 09:16:48
|
Hi All, i have installed cxterm 5.2.3 in my RH9 machine, it works fine with GB. = however when i use "cxterm -b5", it give the following errors. [root@rh9 www]# cxterm -b5 xset: bad font path element (#58), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax cxtermb5: unable to open font "hku16et", trying "cclib16st".... cxtermb5: unable to locate a suitable Chinese font i have run "make install-fonts", and i found a new directory created in = /usr/X11R6/share/cxterm/fonts/ but when i type "xlsfonts | grep hk", nothing return.=20 and when find BG font, "xlsfonts | grep gb" it return : -isas-fangsong ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0 -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0 -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0 hanzigb16fs hanzigb16st hanzigb24st what's wrong? Anyone can help me? thx a lot |
From: Hin-Tak L. <hin...@ya...> - 2004-08-04 21:18:40
|
Hi people, long time no hear. I just forked cxterm with a branch to switch to the newer unix98-tty on linux. (Fedora 2 ships with legacy pty off). Seems to work for me alright, but then, I don't run cxterm except under linux these days, so I don't know if the change breaks other platforms. In the long term, we probably want to make the change permanent, as there is rumour that the legacy pty option will be removed in later 2.6 linux kernels. Have fun. Aug 04, 2004 cvs - Hini-Tak Leung <ht...@us...> + Redhat problem again. Fedora 2 shipped with the optional legacy BSD tty mode in the 2.6 kernel switched off. Well, cxterm is very old... Merged unix98-related code-changes and small extras fom xterm's source over the last 9 years since the fork. Now uses the newer unix98-style ttys on linux. Probably will break other platforms. Caution! |
From: Mitrophan C. <stm...@ya...> - 2003-08-27 17:17:25
|
I've update the hku16et big5 font to include hkscs supplement. You can download hku16hkscs font and test it from http://cs-people.bu.edu/butta1/personal/hkscs/ I tried displaying http://cs-people.bu.edu/butta1/personal/hkscs/gccsdemo.txt with cxterm with the updated font, but cxterm can not show the glyphs for the code range 8E40 to A0E6. Everything after FA40 has no problem displaying. Does anyone know how to fix that? Also for the /usr/bin/X11/cxterm shell script that came with the rpm, I had to remove all the hardcoded hanzi font setting, so that cxterm can read the default hanzi font setting in /usr/X11R6/share/cxterm/cxtermrc which I change to: cxtermb5*hanziFont: hku16hkscs -Nelson __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
From: Mitrophan C. <stm...@ya...> - 2003-08-26 19:39:54
|
I've downloaded the cxterm-big5 rpm file and installed it and it only has the following: [nelsonc /usr/X11R6/share/cxterm/dict/big5] $ rpm -qal cxterm-big5 /usr/X11R6/bin/cxtermb5 /usr/X11R6/share/cxterm/dict/big5 /usr/X11R6/share/cxterm/dict/big5/4Corner.cit /usr/X11R6/share/cxterm/dict/big5/ARRAY30.cit /usr/X11R6/share/cxterm/dict/big5/Boshiamy.cit /usr/X11R6/share/cxterm/dict/big5/CangJie.cit /usr/X11R6/share/cxterm/dict/big5/ETZY.cit /usr/X11R6/share/cxterm/dict/big5/English.cit /usr/X11R6/share/cxterm/dict/big5/HSU.cit /usr/X11R6/share/cxterm/dict/big5/PY.cit /usr/X11R6/share/cxterm/dict/big5/Punct.cit /usr/X11R6/share/cxterm/dict/big5/QJ.cit /usr/X11R6/share/cxterm/dict/big5/Simplex.cit /usr/X11R6/share/cxterm/dict/big5/ZOZY.cit /usr/X11R6/share/cxterm/dict/big5/simple.lx --- Hin-Tak Leung <hin...@ya...> wrote: > Is it not? I think just by a different name. > > cxterm/dict/big5/CTLauBig5.tit > cxterm/dict/gb/CTLau.tit > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
From: Hin-Tak L. <hin...@ya...> - 2003-08-26 19:31:04
|
Is it not? I think just by a different name. cxterm/dict/big5/CTLauBig5.tit cxterm/dict/gb/CTLau.tit Mitrophan Chin wrote: > Hi, > > My name is Nelson Chin, one of the former maintainers > of the Chinese software collection at ifcss.org back > in the 90s. I'm glad to see some of the software is > still being maintained and updated. I posted to the > forum > http://sourceforge.net/forum/forum.php?forum_id=123683, > but I'll also ask here. Can the big5 dict collection > also include the CTLauB Cantonese input method. It's > available at: > > http://www.ocrat.com/ocrat/reaf/CTLauB.tit > > and here's updated cxtermrc: > > ~Shift <KeyPress> F8: switch-HZ-mode(English) \n\ > Shift <KeyPress> F8: switch-HZ-mode(CTLauB) \n\ > > -Nelson > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines > at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel > |
From: Mitrophan C. <stm...@ya...> - 2003-08-26 14:06:33
|
Hi, My name is Nelson Chin, one of the former maintainers of the Chinese software collection at ifcss.org back in the 90s. I'm glad to see some of the software is still being maintained and updated. I posted to the forum http://sourceforge.net/forum/forum.php?forum_id=123683, but I'll also ask here. Can the big5 dict collection also include the CTLauB Cantonese input method. It's available at: http://www.ocrat.com/ocrat/reaf/CTLauB.tit and here's updated cxtermrc: ~Shift <KeyPress> F8: switch-HZ-mode(English) \n\ Shift <KeyPress> F8: switch-HZ-mode(CTLauB) \n\ -Nelson __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com |
From: Jun S. <js...@ju...> - 2003-07-29 00:46:05
|
On Tue, Jul 29, 2003 at 12:33:01AM +0100, Hin-Tak Leung wrote: > Almost. I asked you to search for "CHAR_ENCODING". > It occured twice, and you only did one thing :-). > You need > envsize += 1; > where the other is. > > (I know it is unfair because the other instance is > in a comment, but it is commented for a reason - exactly > the sort of things we are doing: so that it is possible > to searching for corresponding changes!) > I tried that, in a slight different way. See below. It did not work either. :) diff -Nru ./cxterm/main.c.orig ./cxterm/main.c --- ./cxterm/main.c.orig 2003-05-06 00:40:19.000000000 -0700 +++ ./cxterm/main.c 2003-07-28 17:43:32.000000000 -0700 @@ -2631,7 +2631,7 @@ for (i = 0 ; environ [i] != NULL ; i++) ; /* compute number of Setenv() calls below */ - envsize = 1; /* (NULL terminating entry) */ + envsize = 2; /* (NULL terminating entry) */ envsize += 3; /* TERM, WINDOWID, DISPLAY */ #ifdef UTMP envsize += 1; /* LOGNAME */ @@ -2960,7 +2960,7 @@ #ifdef HANZI Setenv ("CHAR_ENCODING=", term->misc.hz_encoding); #endif - + Setenv ("LANG=", "zh_CN"); /* need to reset after all the ioctl bashing we did above */ #if defined(sun) && !defined(SVR4) > When it works for you, do let us (the list know). > (and no need to e-mail me if you are e-mailing the list, > because I am in it!) > I was just lazy to remove your email from To list manually when I use group-reply. The mailing list really should handle that. BTW I am receiving two copies of your reply every time too for the same reason. Jun > Jun Sun wrote: > >On Mon, Jul 28, 2003 at 07:13:19PM +0100, Hin-Tak Leung wrote: > > > >>Yes, in fact I was about to write - in fact on my > >>redhat 9 box LANG is "en_GB.UTF-8" (even under cxterm) > >>which is wrong; on a normal gnome-term, the LANG > >>setting causes a warning when one starts acrobat > >>reader. > >> > >>No, you are not being greedy. cxterm should set LANG > >>internally. It already set a few environment > >>variables like TERM, and CHAR_ENCODING internally > >>already, and there is no reason why it shouldn't set > >>LANG also. Do you want to give it a go and send me a > >>patch? Search the string "CHAR_ENCODING" and see how > >>it is done. The change is quite simple I think, but I > >>just don't have the time to do it at the moment :-). > >> > > > > > >I tried the following, and it does not work. I looked around > >and find myself really in a wonderland. Couldn't figure a thing. :) > > > >Jun > > > >diff -Nru ./cxterm/main.c.orig ./cxterm/main.c > >--- ./cxterm/main.c.orig 2003-05-06 00:40:19.000000000 -0700 > >+++ ./cxterm/main.c 2003-07-28 16:04:06.000000000 -0700 > >@@ -2960,7 +2960,7 @@ > > #ifdef HANZI > > Setenv ("CHAR_ENCODING=", term->misc.hz_encoding); > > #endif > >- > >+ Setenv ("LANG=", "zh_CN"); > > > > /* need to reset after all the ioctl bashing we did above > > */ > > #if defined(sun) && !defined(SVR4) > > > > > > > >------------------------------------------------------- > >This SF.Net email sponsored by: Free pre-built ASP.NET sites including > >Data Reports, E-commerce, Portals, and Forums are available now. > >Download today and enter to win an XBOX or Visual Studio .NET. > >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > >_______________________________________________ > >cxterm-devel mailing list > >cxt...@li... > >https://lists.sourceforge.net/lists/listinfo/cxterm-devel > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel |
From: Hin-Tak L. <hin...@ya...> - 2003-07-28 23:28:36
|
Almost. I asked you to search for "CHAR_ENCODING". It occured twice, and you only did one thing :-). You need envsize += 1; where the other is. (I know it is unfair because the other instance is in a comment, but it is commented for a reason - exactly the sort of things we are doing: so that it is possible to searching for corresponding changes!) When it works for you, do let us (the list know). (and no need to e-mail me if you are e-mailing the list, because I am in it!) Jun Sun wrote: > On Mon, Jul 28, 2003 at 07:13:19PM +0100, Hin-Tak Leung wrote: > >>Yes, in fact I was about to write - in fact on my >>redhat 9 box LANG is "en_GB.UTF-8" (even under cxterm) >>which is wrong; on a normal gnome-term, the LANG >>setting causes a warning when one starts acrobat >>reader. >> >>No, you are not being greedy. cxterm should set LANG >>internally. It already set a few environment >>variables like TERM, and CHAR_ENCODING internally >>already, and there is no reason why it shouldn't set >>LANG also. Do you want to give it a go and send me a >>patch? Search the string "CHAR_ENCODING" and see how >>it is done. The change is quite simple I think, but I >>just don't have the time to do it at the moment :-). >> > > > I tried the following, and it does not work. I looked around > and find myself really in a wonderland. Couldn't figure a thing. :) > > Jun > > diff -Nru ./cxterm/main.c.orig ./cxterm/main.c > --- ./cxterm/main.c.orig 2003-05-06 00:40:19.000000000 -0700 > +++ ./cxterm/main.c 2003-07-28 16:04:06.000000000 -0700 > @@ -2960,7 +2960,7 @@ > #ifdef HANZI > Setenv ("CHAR_ENCODING=", term->misc.hz_encoding); > #endif > - > + Setenv ("LANG=", "zh_CN"); > > /* need to reset after all the ioctl bashing we did above */ > #if defined(sun) && !defined(SVR4) > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel > |
From: Jun S. <js...@ju...> - 2003-07-28 23:07:24
|
On Mon, Jul 28, 2003 at 07:13:19PM +0100, Hin-Tak Leung wrote: > Yes, in fact I was about to write - in fact on my > redhat 9 box LANG is "en_GB.UTF-8" (even under cxterm) > which is wrong; on a normal gnome-term, the LANG > setting causes a warning when one starts acrobat > reader. > > No, you are not being greedy. cxterm should set LANG > internally. It already set a few environment > variables like TERM, and CHAR_ENCODING internally > already, and there is no reason why it shouldn't set > LANG also. Do you want to give it a go and send me a > patch? Search the string "CHAR_ENCODING" and see how > it is done. The change is quite simple I think, but I > just don't have the time to do it at the moment :-). > I tried the following, and it does not work. I looked around and find myself really in a wonderland. Couldn't figure a thing. :) Jun diff -Nru ./cxterm/main.c.orig ./cxterm/main.c --- ./cxterm/main.c.orig 2003-05-06 00:40:19.000000000 -0700 +++ ./cxterm/main.c 2003-07-28 16:04:06.000000000 -0700 @@ -2960,7 +2960,7 @@ #ifdef HANZI Setenv ("CHAR_ENCODING=", term->misc.hz_encoding); #endif - + Setenv ("LANG=", "zh_CN"); /* need to reset after all the ioctl bashing we did above */ #if defined(sun) && !defined(SVR4) |
From: <hin...@ya...> - 2003-07-28 18:13:24
|
Yes, in fact I was about to write - in fact on my redhat 9 box LANG is "en_GB.UTF-8" (even under cxterm) which is wrong; on a normal gnome-term, the LANG setting causes a warning when one starts acrobat reader. No, you are not being greedy. cxterm should set LANG internally. It already set a few environment variables like TERM, and CHAR_ENCODING internally already, and there is no reason why it shouldn't set LANG also. Do you want to give it a go and send me a patch? Search the string "CHAR_ENCODING" and see how it is done. The change is quite simple I think, but I just don't have the time to do it at the moment :-). --- Jun Sun <js...@ju...> wrote: > > The problem was finally solved when Alain pointed > out that > I was setting wrong value to LANG. > > Now I am getting greedy. :) Is there a way to > automatically > set LANG to zh_CN.gb2312 when I fire cxterm?> > > BTW, setting LANG to "zh_CN" seems to work too. > > Jun > > ----------------------------- > On Tue, Jul 15, 2003 at 11:55:46AM +0200, Alain > Bench wrote: > > Hello Jun, > > > > On Sunday, July 13, 2003 at 3:00:26 PM -0700, Jun > Sun wrote: > > > > > I tried to set [LANG] to "gb2312", but I got all > "?????" marks in > > > places of chinese characters. :( > > > > Pick in output of "locale --all-locales" a > locale value using GB2312 > > charset, perhaps zh_CN or zh_CN.gb2312, or build > an en_US.gb2312 one > > (man localedef). It has to exist there, before you > assign it to LANG and > > the like. > > > > Ahh, I missed this email earlier. This actually > solves my problem by > > export LANG=zh_CN.gb2312 > > I also note that some other apps (such as vim) start > to display chinese > correctly after this setting. However some others > (such as less) still > can't get it. > > But I am happy. Thanks a bunch. > > Jun > > > Then verify in Mutt ":set ?charset" gives > "gb2312", otherwise set it > > explicitly in muttrc. Also set in muttrc: > > > > | set > +send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:iso-8859-2:windows-1 > +250:gb2312:utf-8" > > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are > available now. > Download today and enter to win an XBOX or Visual > Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
From: Jun S. <js...@ju...> - 2003-07-28 17:51:53
|
The problem was finally solved when Alain pointed out that I was setting wrong value to LANG. Now I am getting greedy. :) Is there a way to automatically set LANG to zh_CN.gb2312 when I fire cxterm?> BTW, setting LANG to "zh_CN" seems to work too. Jun ----------------------------- On Tue, Jul 15, 2003 at 11:55:46AM +0200, Alain Bench wrote: > Hello Jun, > > On Sunday, July 13, 2003 at 3:00:26 PM -0700, Jun Sun wrote: > > > I tried to set [LANG] to "gb2312", but I got all "?????" marks in > > places of chinese characters. :( > > Pick in output of "locale --all-locales" a locale value using GB2312 > charset, perhaps zh_CN or zh_CN.gb2312, or build an en_US.gb2312 one > (man localedef). It has to exist there, before you assign it to LANG and > the like. > Ahh, I missed this email earlier. This actually solves my problem by export LANG=zh_CN.gb2312 I also note that some other apps (such as vim) start to display chinese correctly after this setting. However some others (such as less) still can't get it. But I am happy. Thanks a bunch. Jun > Then verify in Mutt ":set ?charset" gives "gb2312", otherwise set it > explicitly in muttrc. Also set in muttrc: > > | set +send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:iso-8859-2:windows-1 +250:gb2312:utf-8" > |
From: Jun S. <js...@ju...> - 2003-07-14 06:01:06
|
Hi, I asked some questions in the mutt mailing list about chinese display problem with cxterm. See the attachment. I have little knowledge about utf-8 support and its relation to gb2312, etc.. Can someone more knowledgable on this enlighten me a little bit? Thanks in advance. Jun |
From: Hin-Tak L. <hin...@ya...> - 2003-07-06 10:37:19
|
Jun Sun wrote: > On Fri, Jul 04, 2003 at 03:13:58PM +0100, Hin-Tak Leung wrote: > > I tried, but 'less -r' or 'less -R' does not work. > Probably not too interesting anyway. > This is strange. > Yeah, I managed to remove the files what 'tic' has added. > > I will probably try to ask some mutt people and see if they > have any clues. I'll probably try see have a look around my office redhat 9 box to see if there is anything unusual. |
From: Jun S. <js...@ju...> - 2003-07-06 05:10:22
|
On Fri, Jul 04, 2003 at 03:13:58PM +0100, Hin-Tak Leung wrote: > BTW, there is actually no need to reply to me, as I am > on cxterm-devel list. I tend to CC that list, as it > gets to be archived for future (and I do get a copy > of my own message back as a result). > I did not mean to reply to you personally. I used "group reply", which typically would reply to you and cc: to mailing list. Most mailing lists are smart enough _not_ to send you a separate email so that net effect looks as if the reply is sent to the whole list. Somehow this mailing list is not configured so. For example, I always received two copies of your replies. Anyway that is minor annoyance. :) > > > > Thanks a lot for your reply. > > > > I found more about the problem now. Since I am not > > familiar > > with X font / Chinese at all, I am posting it here > > and hopeful > > you can tell me what is wrong. > > > > 1. the problem shows up initially with mutt, an > > email client. BTW, I notice > > that mail has a header "X-MIME-Autoconverted: > > from quoted-printable to > > 8bit by gateway.junsun.net id". Not sure if it > > matters. > > It probably does, but I don't know mutt at all to > tell. > > > > > 2. If I save the email, and then do 'cat' or tail of > > the email file, > > Chinese shows up just fine! > > I was thinking that since 'cat' and 'more' works we can at least rule out the possiblity of font server problem. True? > > 3. If I use 'less' to show the email file, fonts get > > screwed up, in > > a different way from how mutt screws it up. > > That's an unrelated problem. You would find more > works, > but less doesn't, unless you use "less -r". read the > man page of less for the -r option. > I tried, but 'less -r' or 'less -R' does not work. Probably not too interesting anyway. > > > > 4. I tried to add xterm to /etc/termcap and do "tic" > > by following > > READM.termcap. After I have done "tic", mutt > > refues to start > > and says > > > > Your terminal lacks the ability to clear the screen > > or position the cursor. > > That's strange. You should be able to revert the > change by > 1. edit /etc/termcap and remove the section appended. > (the original instruction was to append one of > the file to /etc/termcap). > > 2. remove the terminfo entry. It is a single file > "/usr/share/terminfo/c/cxtem" > Yeah, I managed to remove the files what 'tic' has added. I will probably try to ask some mutt people and see if they have any clues. Thanks a bunch. Jun |
From: <hin...@ya...> - 2003-07-04 14:14:03
|
BTW, there is actually no need to reply to me, as I am on cxterm-devel list. I tend to CC that list, as it gets to be archived for future (and I do get a copy of my own message back as a result). --- Jun Sun <js...@ju...> wrote: > > Hi, Hin-Tak, > > Thanks a lot for your reply. > > I found more about the problem now. Since I am not > familiar > with X font / Chinese at all, I am posting it here > and hopeful > you can tell me what is wrong. > > 1. the problem shows up initially with mutt, an > email client. BTW, I notice > that mail has a header "X-MIME-Autoconverted: > from quoted-printable to > 8bit by gateway.junsun.net id". Not sure if it > matters. It probably does, but I don't know mutt at all to tell. > > 2. If I save the email, and then do 'cat' or tail of > the email file, > Chinese shows up just fine! > > 3. If I use 'less' to show the email file, fonts get > screwed up, in > a different way from how mutt screws it up. That's an unrelated problem. You would find more works, but less doesn't, unless you use "less -r". read the man page of less for the -r option. > > 4. I tried to add xterm to /etc/termcap and do "tic" > by following > READM.termcap. After I have done "tic", mutt > refues to start > and says > > Your terminal lacks the ability to clear the screen > or position the cursor. That's strange. You should be able to revert the change by 1. edit /etc/termcap and remove the section appended. (the original instruction was to append one of the file to /etc/termcap). 2. remove the terminfo entry. It is a single file "/usr/share/terminfo/c/cxtem" > > I have little clue as to what might wrong. Can you > shed some lights? > ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ |
From: Jun S. <js...@ju...> - 2003-07-04 14:00:13
|
Hi, Hin-Tak, Thanks a lot for your reply. I found more about the problem now. Since I am not familiar with X font / Chinese at all, I am posting it here and hopeful you can tell me what is wrong. 1. the problem shows up initially with mutt, an email client. BTW, I notice that mail has a header "X-MIME-Autoconverted: from quoted-printable to 8bit by gateway.junsun.net id". Not sure if it matters. 2. If I save the email, and then do 'cat' or tail of the email file, Chinese shows up just fine! 3. If I use 'less' to show the email file, fonts get screwed up, in a different way from how mutt screws it up. 4. I tried to add xterm to /etc/termcap and do "tic" by following READM.termcap. After I have done "tic", mutt refues to start and says Your terminal lacks the ability to clear the screen or position the cursor. I have little clue as to what might wrong. Can you shed some lights? Jun On Wed, Jun 25, 2003 at 08:45:41AM +0100, Hin-Tak Leung wrote: > As I previously say - there is no significant change between 5.2.2 > and 5.2.3 (and CVS) other than fixing some compiler warnings. > > There is a hell lot of difference between Redhat 6.2 and Redhat 9 > regarding font management, just as the Xfree86 terminfo/termcap > problem I mentioned. Redhat 9 uses a separate font server, rather > than have static font directories like RH 6.2. > > I suspect the RH 9 font server doesn't work all the time, or > reliably. You could go back to static font directories, or have > font directories in addition to font server, by modifying the > "FontPath" entries in /etc/X11/XF86Config. "man 5 XF86Config" > for details, I think. > > Please note that cxterm is no longer in active development (the > sourceforge project is "unofficial" and the original authors > are not here)- it has worked almost as it was in 1995, so any > breakage is usually due to changes elsewhere...) > > > Jun Sun wrote: > >Just when I was happy, all of a sudden fonts are all screwed up. > >Instead of nice Chinese sentences, only some random senseless characters > >are displayed in place. > > > >And I don't even recall what I changed to cause this. I rebuilt > >cxterm with latest CVS, and still have the same results. > > > >Does anybody have a clue what goes wrong here? > > > >Actually I had this problem when I upgrade from redhat 6.2 to redhat 9 > >while still using the old 5.2.2 release. I thought I fixed the problem > >by using the latest CVS source (actually it worked on that particular > >day, I swear) > > > >Strange. > > > >Jun > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: INetU > >Attention Web Developers & Consultants: Become An INetU Hosting Partner. > >Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > >INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > >_______________________________________________ > >cxterm-devel mailing list > >cxt...@li... > >https://lists.sourceforge.net/lists/listinfo/cxterm-devel > > |
From: Hin-Tak L. <hin...@ya...> - 2003-06-25 07:42:41
|
As I previously say - there is no significant change between 5.2.2 and 5.2.3 (and CVS) other than fixing some compiler warnings. There is a hell lot of difference between Redhat 6.2 and Redhat 9 regarding font management, just as the Xfree86 terminfo/termcap problem I mentioned. Redhat 9 uses a separate font server, rather than have static font directories like RH 6.2. I suspect the RH 9 font server doesn't work all the time, or reliably. You could go back to static font directories, or have font directories in addition to font server, by modifying the "FontPath" entries in /etc/X11/XF86Config. "man 5 XF86Config" for details, I think. Please note that cxterm is no longer in active development (the sourceforge project is "unofficial" and the original authors are not here)- it has worked almost as it was in 1995, so any breakage is usually due to changes elsewhere...) Jun Sun wrote: > Just when I was happy, all of a sudden fonts are all screwed up. > Instead of nice Chinese sentences, only some random senseless characters > are displayed in place. > > And I don't even recall what I changed to cause this. I rebuilt > cxterm with latest CVS, and still have the same results. > > Does anybody have a clue what goes wrong here? > > Actually I had this problem when I upgrade from redhat 6.2 to redhat 9 > while still using the old 5.2.2 release. I thought I fixed the problem > by using the latest CVS source (actually it worked on that particular > day, I swear) > > Strange. > > Jun > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel > |
From: Jun S. <js...@ju...> - 2003-06-25 02:19:40
|
Just when I was happy, all of a sudden fonts are all screwed up. Instead of nice Chinese sentences, only some random senseless characters are displayed in place. And I don't even recall what I changed to cause this. I rebuilt cxterm with latest CVS, and still have the same results. Does anybody have a clue what goes wrong here? Actually I had this problem when I upgrade from redhat 6.2 to redhat 9 while still using the old 5.2.2 release. I thought I fixed the problem by using the latest CVS source (actually it worked on that particular day, I swear) Strange. Jun |
From: Hin-Tak L. <hin...@ya...> - 2003-06-20 23:21:06
|
Jun Sun wrote: > On Fri, Jun 20, 2003 at 08:37:09AM +0100, Hin-Tak Leung wrote: > >>Can I ask (1) how the old bug looks like? >>(2) Did you use the new termcap/terminfo files (one >>of the post-5.2.3 enhancements)? >> >>If the old bug is about screen layout, it is most-likely >>due to (2). There weren't much difference between 5.2.2 and >>5.2.3, other than removing a lot of compiler warnings/errors. > > The bug shows with redhat 6.2 + cxterm 5.2.2. I forget about mutt > version. Around v1.0. > > The workaround I used to use is "export TERM=vt100". > > My current system is redhat 9 + cxterm 5.2.3+. Mutt is 1.4. And > I don't have to use the workaround. I don't know what is responsible > for the change. > > The symptom was in threaded listing, subjects are not lined up correctly. That's screen layout corruption (it was discussed in the mailing list affecting lynx, and vi previously), particularly if you can work around it with setting TERM. The correct fix is detailed in "README.terminfo". It is a problem of Xfree86 moving away from how the older X11R6 system was like in 1995 when cxterm's terminal capability code was last updated; the proper way to fix it is to create proper "cxterm" TERM entries in the host OS. If the terminal capability database in a distro doesn't have a cxterm entry, cxterm will try to use the xterm entry (very distro and also very Xfree86-version dependent - depending on whether Eterm/GnomeTerm was intergrated, etc) which may or may not work. I think cxterm only *happened* to work on RH9 - you should fix it properly as outlined in README.terminfo. |
From: Jun S. <js...@ju...> - 2003-06-20 22:25:23
|
On Fri, Jun 20, 2003 at 08:37:09AM +0100, Hin-Tak Leung wrote: > Can I ask (1) how the old bug looks like? > (2) Did you use the new termcap/terminfo files (one > of the post-5.2.3 enhancements)? > > If the old bug is about screen layout, it is most-likely > due to (2). There weren't much difference between 5.2.2 and > 5.2.3, other than removing a lot of compiler warnings/errors. > The bug shows with redhat 6.2 + cxterm 5.2.2. I forget about mutt version. Around v1.0. The workaround I used to use is "export TERM=vt100". My current system is redhat 9 + cxterm 5.2.3+. Mutt is 1.4. And I don't have to use the workaround. I don't know what is responsible for the change. The symptom was in threaded listing, subjects are not lined up correctly. Jun > Jun Sun wrote: > >On Wed, Jun 18, 2003 at 09:00:29AM +0100, Hin-Tak Leung wrote: > > > >>Yes, ifcss.org is defunct. But you can get it from: > >> > >>http://sourceforge.net/projects/cxterm/ > >> > >>Prebuilt RPMS are available - made on glibc 2.2.5 > >>(slackware 9), and should be usable for Redhat > >>7.2 or 7.3 onwards. > >> > >>Check the news items, and there are two post-5.2.3 > >>enhancements, so you might want to get the CVS version > >>instead, or at least download about 5 files > >>from webCVS in addition to v5.2.3. > >> > > > > > >I downloaded the CVS tree. It worked like a chime. > > > >There was an old bug when I used 5.2.2 with mutt. That is even gone > >now. > > > >Thanks. > > > >Jun > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > cxterm-devel mailing list > cxt...@li... > https://lists.sourceforge.net/lists/listinfo/cxterm-devel |
From: Hin-Tak L. <hin...@ya...> - 2003-06-20 07:33:21
|
Can I ask (1) how the old bug looks like? (2) Did you use the new termcap/terminfo files (one of the post-5.2.3 enhancements)? If the old bug is about screen layout, it is most-likely due to (2). There weren't much difference between 5.2.2 and 5.2.3, other than removing a lot of compiler warnings/errors. Jun Sun wrote: > On Wed, Jun 18, 2003 at 09:00:29AM +0100, Hin-Tak Leung wrote: > >>Yes, ifcss.org is defunct. But you can get it from: >> >>http://sourceforge.net/projects/cxterm/ >> >>Prebuilt RPMS are available - made on glibc 2.2.5 >>(slackware 9), and should be usable for Redhat >>7.2 or 7.3 onwards. >> >>Check the news items, and there are two post-5.2.3 >>enhancements, so you might want to get the CVS version >>instead, or at least download about 5 files >>from webCVS in addition to v5.2.3. >> > > > I downloaded the CVS tree. It worked like a chime. > > There was an old bug when I used 5.2.2 with mutt. That is even gone > now. > > Thanks. > > Jun > |
From: Jun S. <js...@ju...> - 2003-06-20 01:11:14
|
On Wed, Jun 18, 2003 at 09:00:29AM +0100, Hin-Tak Leung wrote: > Yes, ifcss.org is defunct. But you can get it from: > > http://sourceforge.net/projects/cxterm/ > > Prebuilt RPMS are available - made on glibc 2.2.5 > (slackware 9), and should be usable for Redhat > 7.2 or 7.3 onwards. > > Check the news items, and there are two post-5.2.3 > enhancements, so you might want to get the CVS version > instead, or at least download about 5 files > from webCVS in addition to v5.2.3. > I downloaded the CVS tree. It worked like a chime. There was an old bug when I used 5.2.2 with mutt. That is even gone now. Thanks. Jun |