Date: Mon, 26 Jun 2006 19:54:39 -0400 From: Thomas Dickey <dickey@radix.net> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: freebsd-current@freebsd.org Subject: Re: Unicode (was Re: Updating ncurses in base) Message-ID: <20060626235439.GA11403@saltmine.radix.net> In-Reply-To: <20060626191808.GC74292@over-yonder.net> References: <6eb82e0606091906j7d9f69aarcf1f9738c7565677@mail.gmail.com> <20060625221640.GI48766@linwhf.opal.com> <20060626014939.GA74292@over-yonder.net> <20060626115840.vrmox3wo0gg08gog@netchild.homeip.net> <20060626124158.GA7801@mail.scottro.net> <20060626191808.GC74292@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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) >=20 > + LC_CTYPE=3Den_US.UTF-8 > + export LC_CTYPE > + exec xterm -class UXTerm -title uxterm -u8 >=20 > which is what triggers my problem when I do it manually (`env > LC_CTYPE=3D... 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. --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFEoHO9tIqByHxlDocRAlEUAKCjN5lA4NtdSTuGVOyZ5lRGdBFzMACfX6Xb WVHmzbAJAyhN6wr+BhQGxyc= =LBvw -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060626235439.GA11403>