Hi,

I am trying to make debians aptitude work in M-x term. The
problem is that it uses a unicode character, which emacs does not
display properly. It's this one

9618 (#o22622, #x2592)

, which looks like

â–’

In term it is displayed as escape sequences and the tooltip says
'Untranslated unicode'. (describe-coding-system 'utf-8) tells me
that this character is outside it's supported range. But I can insert
it in a buffer with (decode-char 'ucs 9618) .

How do I make emacs display this byte sequence properly ?

-ap

Am 18.09.2008 um 19:25 schrieb Andreas Politz:

Is the *term* buffer set to UTF-8 encoding?

Peter Dyballa wrote:

Yes, it is:

----------%%<----------------
u -- mule-utf-8-unix

UTF-8 encoding for Emacs-supported Unicode characters.
It supports Unicode characters of these ranges:
U+0000..U+33FF, U+E000..U+FFFF.
They correspond to these Emacs character sets:
ascii, latin-iso8859-1, mule-unicode-0100-24ff,
mule-unicode-2500-33ff, mule-unicode-e000-ffff
--------%%<------------------

Am 18.09.2008 um 20:16 schrieb Andreas Politz:

Ahh! So you're with GNU Emacs 22.x? I can reproduce it in 22.2. Once
I check this character in Kermit's utf8.txt file it's described as:

character: â–’ (299218, #o1110322, #x490d2, U+2592)
charset: mule-unicode-2500-33ff
(Unicode characters of the range U+2500..U+33FF.)

In UTF-8 presentation this character is encoded with these three
bytes: E2 96 92. These are in "ASCII" (rather an 8-bit "ASCII"):
‚ ñ í. Using C-q 1 1 1 0 3 2 2 I can insert
HALF SHADE. Could be this non-Unicode Emacs has to use some extras to
handle this ...

If no-one on this list has an explanation I'd write a bug report (see
Help menu), also mentioning the 'Invalid character' message. Although
it looks as if GNU Emacs 22.x seems to recommend to use 1110322
instead of 22622 ...

Peter Dyballa wrote:

Yes emacs 22.2.1 .