Date: Wed, 16 Feb 2000 12:41:35 -0500 (EST) Message-Id: <200002161741.MAA05912@indy.delorie.com> From: Eli Zaretskii To: djgpp AT delorie DOT com CC: peuha AT cc DOT helsinki DOT fi In-reply-to: (message from Eli Zaretskii on Wed, 16 Feb 2000 16:01:48 +0200 (IST)) Subject: Re: Problems with Emacs 20.5 References: Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > You cannot currently use `C-x 8' (and any other variants of 8-bit input) > in the DJGPP version of Emacs. Sorry, one should never reply in a haste while one's ride is waiting outside ;-) The *correct* answer to this is that `C-x 8' works for me in Emacs 20.5. You need to set the keyboard coding system to latin-1, like this: C-x C-m k latin-1 RET After that, you should be able to insert Latin-1 characters with "C-x 8", like you'd expect. (But if your codepage doesn't support some of the Latin-1 glyphs, they will be simulated by ASCII strings, like the manual describes.) If this doesn't work for you, please post the details. The reason for the above setting is that `C-x 8' simulates a Latin-1 character by, in effect, feeding Emacs with the Latin-1 8-bit code of the character as if you were typing that 8-bit code from the keyboard. Emacs needs to translate these 8-bit codes into its internal representation of non-ASCII characters, so it needs to know that the keyboard transmits Latin-1 codes. That's what keyboard coding system is for. What I said about limitations of 8-bit input support is true, but only if the 8-bit code is according to the codepage. Since `C-x 8' generates the Latin-1 encoding, not a cp437 encoding, this problem doesn't exist with `C-x 8'. The problems I mentioned will be visible if you try to input non-ASCII characters using the AltGr key. Sorry about any confusion. Btw, why are you using codepage 437? I'd expect the machines in Western Europe to use cp850 by default, not cp437.