Date:	Tue, 14 Mar 2000 16:13:30 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Dieter Buerssner <buers AT gmx DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: bash 2.03 / german umlauts
In-Reply-To:	<200003141124.NAA06080@is.elta.co.il>
Message-ID:	<Pine.SUN.3.91.1000314160857.7328A-100000@is>
MIME-Version:	1.0
X-MIME-Autoconverted:	from QUOTED-PRINTABLE to 8bit by delorie.com id JAA01324
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

On Tue, 14 Mar 2000, Dieter Buerssner wrote:

> 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.

Yes, in Sven's case there is no beep.  And that is what puzzles me: why 
the difference?  I can explain the beeps, but not lack thereof.  So 
there's no misunderstanding.

It would be interesting to see what does your program yield on Sven's 
system.

> BTW, the German keys are not special here. To get the french
> accented letter è I have to type ` followed by e.

Yes, the issue is Latin-1 characters with the 8th bit set, not German
characters specifically.

> 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.

I think I explained elsewhere why Bash beeps: it has its own ideas about 
the 8th bit.

But that doesn't explain the lack of any effect on Sven's system, which 
is what I was trying to understand.

> 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.

And yet the two systems do behave differently.  I wonder why.

- Raw text -