On Thu, Jun 09, 2005 at 07:36:58PM -0700, Frederik Eaton wrote:
> On Thu, Jun 09, 2005 at 07:53:05PM -0400, Thomas Dickey wrote:
> Huh. I guess I'd thought that reproducing wouldn't be a problem.
>
> - When I run
>
> perl -le 'print "\x{c2}\x{b7}"'
Offhand, that looks like the UTF-8 encoding for the Latin-1 bullet.
Codes from 0x80 to 0xff are mapped to something like 0xc2 followed
by the original value (a little more complicated than that, but enough
for reading).
> I get a bullet. When I paste an xpdf bullet into hexdump it is the
> same byte sequence.
That much sounds consistent - when setup for a UTF-8 locale, xterm/uxterm
knows how to select/paste data encoded for UTF-8. The original Latin-1
stuff gets passed around in that form.
> - I tried running emacs in uxterm, same results.
>
> - Emacs thinks that the bullet is M-b M-7.
(I don't use emacs): perhaps emacs needs some adjustment to accept UTF-8
input. I'm guessing that 0xb7 gets entered as M-7, and 0cx2 as M-b.
On my home machine (I'm not at home), I do occasionally enter text using
the meta key, for testing, but don't recall what key combinations make
up the keys I see on the keyboard. Just checking now, xfd shows me a ^/A
for 0xc2 (which doesn't seem to be a "b"), and 0xb7 is a bullet character.
So far that sounds like a configuration problem (not an xterm bug).
There are limitations on select/paste - but ASCII and Latin-1 "should"
work as long as the applications know to accept UTF-8 input.
> Thanks,
>
> Frederik
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
Attachment:
pgpVa8cFlMKZE.pgp
Description: PGP signature