On Jun 26, 19:54, Thomas Dickey wrote: > On Mon, Jun 26, 2006 at 02:18:08PM -0500, Matthew D. Fuller wrote: > > Well, uxterm is just a shell script, an so amenable to quick tests. > > Running it with sh -x basically yields (trimming uninteresting bits) > > > > + LC_CTYPE=en_US.UTF-8 > > + export LC_CTYPE > > + exec xterm -class UXTerm -title uxterm -u8 > > > > which is what triggers my problem when I do it manually (`env > > LC_CTYPE=... xterm`). > > The -u8 option in combination with the locale setting is needed to make > xterm process UTF-8 (and also the -class option helps it to find the > proper fonts). > > Oddly enough (depending on your perspective of course), > there are people who use xterm in UTF-8 with/without > the initial locale settings. > > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net I believe the problem Matt's seeing is due to an error in the UTF-8.src file that's distributed with FreeBSD. I have a patch to fix this. Unfortunately, documentation of this patch was not previously included in the unicode.html notes, an omission I have now corrected. The error in the UTF-8.src file is that the combining character ranges (there are three) are listed with SWIDTH1; they should have SWIDTH0. Folk who are interested can see details in the updated unicode.html file here: http://opal.com/freebsd/unicode.html#lcctype -jr
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:57 UTC