Re: xterm-237-2 still has no UTF-8 support
Jon TURNEY wrote: neomjp wrote: On 2008/12/10 0:39, Yongwei Wu wrote: 1. xterm +lc -u8 I got these messages: Warning: Cannot convert string -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-* to type FontStruct Warning: Cannot convert string nil2 to type FontStruct These are the default fonts specified in /etc/X11/app-defaults/XTerm. -adobe-helvetica-... are provided by font-adobe-dpi100 and font-adobe-dpi75, and nil2 is provided by font-misc-misc. font-misc-misc is critical to this working properly. If you don't have that installed, we end-up using the built-in 'fixed' font, which only has a limited set of glyphs (those needed for iso8859-1, I would guess) (Since 1.5.3-3, the x server has has a built-in 'fixed' font and font-misc-misc is not installed by default) Thanks very much, neomjp and Jon. My only complaints now are that the new behaviour is not well documented from the user's point of view (for both the conflict between -lc and -u8, and the lack of utf-8 fonts by default), and that the name font-misc-misc is not helpful at all (before reading your messages, I had already tried some adobe fonts, but not this one). 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/
xterm-237-2 still has no UTF-8 support
This has been raised in the past: http://cygwin.com/ml/cygwin-xfree/2007-08/msg00082.html The recent xterm-237-2 still does not have the Unicode support enabled, even though it contains a uxterm script. It seems the old xterm-202-1, which has UTF-8 support, no longer works with the new xserver :-(. Any help? 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-237-2 still has no UTF-8 support
On 4:59, Yongwei Wu wrote: The recent xterm-237-2 still does not have the Unicode support It does. But according to xterm-237-2.cygport, it is configured with --enable-luit --enable-wide-chars. man xterm(1) says in the description of -u8, This option and the utf8 resource are overridden by the -lc and -en options and locale resource. That is, if xterm has been compiled to support luit, and the locale resource is not ''false'' this option is ignored. So, -u8 will be ignored without proper options. Try either: 1. xterm +lc -u8 I got these messages: Warning: Cannot convert string -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-* to type FontStruct Warning: Cannot convert string nil2 to type FontStruct And non-ASCII characters become either spaces or question marks. I verified that I can copy the correct characters, but they do not appear. 2. xterm -en UTF-8 Same messages, but the term appears and immediately disappears. 3. or use cygwin-1.7 with proper locale settings. More details? Start bash and say, perl -we 'binmode(STDOUT, :utf8); print(pack(U*, 12371, 12435, 12395, 12385, 12399, 32, 50504, 45397, 54616, 49464, 50836, 63, 32, 20320, 22909));' This should print hello in Japanese, Korean, and Chinese. Nothing but spaces and question marks. However, they can be copied here: こんにちは 안녕하세요? 你好 Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/
Re: xterm-237-2 still has no UTF-8 support
Mark J. Reed wrote: Warning: Cannot convert string -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-* to type FontStruct Warning: Cannot convert string nil2 to type FontStruct And non-ASCII characters become either spaces or question marks. I verified that I can copy the correct characters, but they do not appear. If you can copy them and they appear properly when you paste, that would seem to imply that the xterm is correctly handling the Unicode characters. It's just that the associated glyphs are not present in the font you're using. Good reasoning. I think you are right. Then who is to blame? :-) Another phenomenon I have observed: one cannot change the fonts in the VT Fonts menu. Something is still wrong here, but I am not sure whether it is in xterm or the rest of the XWindow system. 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
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/
