Date: Thu, 10 Dec 1998 12:47:17 +0000 (WET)
From: Miroslaw Prywata <Miroslaw DOT Prywata AT fuw DOT edu DOT pl>
X-Sender: mpry AT krak
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, djgpp AT delorie DOT com,
        "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Subject: Re: RHIDE and consolefonts under Linux
In-Reply-To: <Pine.SUN.3.91.981209130934.8064C-100000@is>
Message-ID: <Pine.GSO.3.96.981210123221.25933A-100000@krak>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id HAA05204
Reply-To: djgpp AT delorie DOT com

On Wed, 9 Dec 1998, Eli Zaretskii wrote:

> One possible solution is to have an extra level of indirection between
> the characters written by the display code and the actual bytes that
> are sent to the screen.  Create a 256-element table, where the X-th
> element holds the byte to be sent to the screen when the display code
> wants to display a character whose 8-bit code is X.

That's how it's more less done in Linux. There are two tables G0,G1, which
can be switched. What is more the character does not only mean the number,
but also its meaning and when there's no that one in the table the
substitute is taken (e.g. instead of ó you can display o, instead of
frame you can take - mdash, |,+, and so on).

But that's only theory (it's not exactly that simple - more information
and examples can be found in console-tools, and console-tools-howto). THe
other thing is that application has to use it so that it could work
correctly.


AFAIK one can use no more that 512 characters at one time.

Mirek