Message-Id: <200003141128.GAA23530@delorie.com>
From: "Dieter Buerssner" <buers AT gmx DOT de>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date: Tue, 14 Mar 2000 12:27:47 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Subject: Re: bash 2.03 / german umlauts
CC: djgpp AT delorie DOT com
References: <8aj6e1$3qe1t$1 AT fu-berlin DOT de>
In-reply-to: <Pine.SUN.3.91.1000314094146.4527D-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12b)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-printable to 8bit by delorie.com id GAA23534
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:

> But the interesting aspect is that Bash reacts differently in your
> case. The original poster cannot get German characters by using the
> Alt-numeric method.  Do you have any idea why? 

There must be a misunderstanding. I cannot get German characters
with the Alt-numeric method in bash (but I can get them using the
bioskey(0)). But I do hear a beep in bash when I type the German 
characters either directly or by using the Alt-nnn method in bash. I 
think Sven mentioned, that he does not hear the beep.

BTW, the German keys are not special here. To get the french
accented letter è I have to type ` followed by e. This won't work
with bash, but will work with bioskey(0) (bioskey reports one
key for the two keystrokes, as you would expect it. Printing that
key with printf("%c", key&0xff) displays the correct glyph).

My setup is the almost same, as the setup Sven described, with the 
only difference, that I use codepage 850, and he uses 437. But
that should not matter.