Bug#318923: utf-8 option for xterm does not work anymore
On Tue, Jul 19, 2005 at 08:25:50PM +0200, Jan Willem Stumpel wrote: > Thomas Dickey wrote: > > >Though (I don't see it in my changelog), there was the > >additional complication of ensuring that simply having UTF-8 > >locale set in the environment did not cause the utf8 resource > >in xterm to be set, e.g., > > > >setenv LANG=en_US.UTF-8 > > xterm +u8 > > > >should run xterm without the resource set. > > Couldn't the same effect be achieved (with the old version) just > by calling, e.g., LANG=en_US xterm? On my system this un-utfs the > xterm very well. Not exactly. The complaint was that the command-line option was not overriding the "locale" resource setting, which looked at the environment and simply turned on the UTF-8 mode because it was a UTF-8 locale. > >Generally the old binaries run - I happened to notice last > >night that I had about 75 copies of xterm in my /usr/local/bin > >(and the bug that I was looking at dated back before X11R5 ;-). > > How do you keep them all sorted out? ;-) They all have patch numbers as part of the filename. It makes a quick way to check old versions to see when a bug was introduced. > Extra data point: after purging "new", installing "old", and then > copying only the "new" xterm binary over the "old", the bug > recurred. So it seems the bug really is in the binary, not in any > (possibly changed) config stuff installed by Debian. That's what I'm assuming. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpf2RlvdzKfB.pgp Description: PGP signature
Bug#318923: utf-8 option for xterm does not work anymore
Thomas Dickey wrote: Though (I don't see it in my changelog), there was the additional complication of ensuring that simply having UTF-8 locale set in the environment did not cause the utf8 resource in xterm to be set, e.g., setenv LANG=en_US.UTF-8 > xterm +u8 should run xterm without the resource set. Couldn't the same effect be achieved (with the old version) just by calling, e.g., LANG=en_US xterm? On my system this un-utfs the xterm very well. The new version gives XTerm(220). The new version gives XTerm(202). You are right, of course. Generally the old binaries run - I happened to notice last night that I had about 75 copies of xterm in my /usr/local/bin (and the bug that I was looking at dated back before X11R5 ;-). How do you keep them all sorted out? ;-) Extra data point: after purging "new", installing "old", and then copying only the "new" xterm binary over the "old", the bug recurred. So it seems the bug really is in the binary, not in any (possibly changed) config stuff installed by Debian. Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318923: utf-8 option for xterm does not work anymore
On Tue, Jul 19, 2005 at 06:37:39PM +0200, Jan Willem Stumpel wrote: > Thomas Dickey wrote: > > > > >The locale resource has been there a couple of years (and can > >be set so that you get the original behavior). > > > >What happens if you set the locale resource to false? (And are > >you ensuring that there are no resource conflicts that override > >that). > > No.. changing to false did not help. Nor trying various settings > for utf8. I have no idea how to check for resource conflicts, though. I have some ideas. Knowing that it is a recent change helps (though as in the bold-font bug last week, I can still _look_ in the wrong place). I did read through my changes last night, saw that I went through 2-3 stages as part of this one: * modify interaction between +u8 and locale resource to allow the command-line option to override the resource (requested by Thomas Wolff). Though (I don't see it in my changelog), there was the additional complication of ensuring that simply having UTF-8 locale set in the environment did not cause the utf8 resource in xterm to be set, e.g., setenv LANG=en_US.UTF-8 xterm +u8 should run xterm without the resource set. > >"It used to be" is vague - one of the problems with the Debian > >package is that I don't know offhand what version of xterm it > >corresponds to. > > Ah.. I should have realized before that you are the AUTHOR, not > the Debian package maintainer. It worked with the previous Debian > version called xterm_4.3.0.dfsg.1-14_i386.deb. I could install > this (somewhat to my amazement) on the new x-org system, and it > worked perfectly! It can be started with UTF-8 as default. In this > working version, xterm -version gives > > XTerm(200) > > The new version gives XTerm(220). The new version gives XTerm(202). Generally the old binaries run - I happened to notice last night that I had about 75 copies of xterm in my /usr/local/bin (and the bug that I was looking at dated back before X11R5 ;-). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgp2LgnQCwXdv.pgp Description: PGP signature
Bug#318923: utf-8 option for xterm does not work anymore
Thomas Dickey wrote: The locale resource has been there a couple of years (and can be set so that you get the original behavior). What happens if you set the locale resource to false? (And are you ensuring that there are no resource conflicts that override that). No.. changing to false did not help. Nor trying various settings for utf8. I have no idea how to check for resource conflicts, though. "It used to be" is vague - one of the problems with the Debian package is that I don't know offhand what version of xterm it corresponds to. Ah.. I should have realized before that you are the AUTHOR, not the Debian package maintainer. It worked with the previous Debian version called xterm_4.3.0.dfsg.1-14_i386.deb. I could install this (somewhat to my amazement) on the new x-org system, and it worked perfectly! It can be started with UTF-8 as default. In this working version, xterm -version gives XTerm(200) The new version gives XTerm(220). Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318923: utf-8 option for xterm does not work anymore
On Tue, Jul 19, 2005 at 08:22:10AM +0200, Jan Willem Stumpel wrote: > Thomas Dickey wrote: > > >The only relevant change I recall recently is > > > >Patch #201 - 2005/4/21 - XFree86 4.5.99.2 * modify interaction > >between +u8 and locale resource to allow the command-line > >option to override the resource (requested by Thomas Wolff). > > > >What value are you using to set xterm*VT100*utf8: ? and what > >would be the value for the locale resource? > > It used to be enough to just set xterm*VT100*utf-8 without any > further value. There is (now ?) according to the xterm man page > also a "locale" resource; setting this to "true" makes no > difference, nor calling from the command line "xterm -lc" or > "xterm -u8". It remains necessary to do CTRL-RightClick and select > UTF8. The locale resource has been there a couple of years (and can be set so that you get the original behavior). What happens if you set the locale resource to false? (And are you ensuring that there are no resource conflicts that override that). "It used to be" is vague - one of the problems with the Debian package is that I don't know offhand what version of xterm it corresponds to. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgph4pm9ihBTa.pgp Description: PGP signature
Bug#318923: utf-8 option for xterm does not work anymore
Thomas Dickey wrote: The only relevant change I recall recently is Patch #201 - 2005/4/21 - XFree86 4.5.99.2 * modify interaction between +u8 and locale resource to allow the command-line option to override the resource (requested by Thomas Wolff). What value are you using to set xterm*VT100*utf8: ? and what would be the value for the locale resource? It used to be enough to just set xterm*VT100*utf-8 without any further value. There is (now ?) according to the xterm man page also a "locale" resource; setting this to "true" makes no difference, nor calling from the command line "xterm -lc" or "xterm -u8". It remains necessary to do CTRL-RightClick and select UTF8. Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318923: utf-8 option for xterm does not work anymore
On Mon, Jul 18, 2005 at 10:00:19PM +0200, Jan Willem Stumpel wrote: > Package: xterm > Version: 6.8.2.dfsg.1-2 > Followup-For: Bug #318923 > > > Apparently it is no longer possible to start xterm in UTF-8 mode by default by > setting > >xterm*VT100*utf8: The only relevant change I recall recently is Patch #201 - 2005/4/21 - XFree86 4.5.99.2 * modify interaction between +u8 and locale resource to allow the command-line option to override the resource (requested by Thomas Wolff). What value are you using to set xterm*VT100*utf8: ? and what would be the value for the locale resource? -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpyDrlN8hwve.pgp Description: PGP signature
Bug#318923: utf-8 option for xterm does not work anymore
Package: xterm Version: 6.8.2.dfsg.1-2 Followup-For: Bug #318923 Apparently it is no longer possible to start xterm in UTF-8 mode by default by setting xterm*VT100*utf8: in /etc/X11/app-defaults/XTerm or in ~/.Xresources. Even if a UTF-8 capable font is present, display of non-ASCII chars is mangled (e.g. a "degree" sign, which is hex c2 b0 in UTF-8, is displayed as A-circumflex followed by a degree sign). To get proper UTF-8 display back, you have to do CTRL-RightClick, then select UTF-8 from the pop-up menu. But it should be possible to set this as default by using xterm*VT100*utf8: . As the OP said, this throws us back into "localization hell" (from which I was so glad to have escaped by changing to UTF-8...) Extra data point: I tried to preserve my own /etc/X11/app-defaults XTerm and XTerm-color files during upgrade. There is now an /etc/X11/app-defaults/XTerm-color.dpkg-dist file, but no /etc/X11/app-defaults/XTerm.dpkg-dist. MAybe something went wrong during the processing of /etc/X11/app-defaults/XTerm. But of course I don't know. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.25 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages xterm depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libfontconfig12.3.2-1generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libice6 6.8.2.dfsg.1-2 Inter-Client Exchange library ii libncurses5 5.4-8 Shared libraries for terminal hand ii libsm66.8.2.dfsg.1-2 X Window System Session Management ii libxaw8 6.8.2.dfsg.1-2 X Athena widget set library ii libxext6 6.8.2.dfsg.1-2 X Window System miscellaneous exte ii libxft2 2.1.7-1FreeType-based font drawing librar ii libxmu6 6.8.2.dfsg.1-2 X Window System miscellaneous util ii libxp66.8.2.dfsg.1-2 X Window System printing extension ii libxpm4 6.8.2.dfsg.1-2 X pixmap library ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii libxt66.8.2.dfsg.1-2 X Toolkit Intrinsics ii xlibs 6.8.2.dfsg.1-2 X Window System client libraries m ii xlibs-data6.8.2.dfsg.1-2 X Window System client data Versions of packages xterm recommends: ii xutils 4.3.0.dfsg.1-14 X Window System utility programs -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
