[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: `set-locale-environment' bug]

From: Eli Zaretskii
Subject: Re: address@hidden: `set-locale-environment' bug]
Date: Mon, 10 Nov 2003 07:31:49 +0200

> Date: Mon, 10 Nov 2003 11:36:00 +0900 (JST)
> From: Kenichi Handa <address@hidden>
> But, in multibyte-mode, it seems that only MS-DOS case (on
> terminal) really requires standard-display-table to be
> setup.  That is because, in that case, characters in the
> current codepage that are not supported by Emacs are decoded
> into eight-bit-control/graphic, and they must be displayed
> by the font of the current codepage as is.
> Eli, is that right?

Yes and no.

No, because unsupported characters are not displayed as the current
codepage's glyphs, they are displayed as a special glyph whose value
is in `dos-unsupported-char-glyph'.

Yes, because term/internal.el, the MS-DOS ``internal terminal''
emulator, sets up standard-display-table to display non-ASCII
characters beyond the current codepage, such as Latin-2 for a cp-850
locale, as strings of ASCII characters, see IT-display-table-setup.

I think in the past standard-display-table was used on multibyte
sessions on Unix as well, to map some characters originating from
Microsoft's codepages to printable ASCII chars, but I'm not sure
whether I remember correctly and if so, why was that removed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]