Re: Unicode support on VGA console.

Jan Bobrowski (jb@wizard.ae.krakow.pl)
Tue, 5 Oct 1999 18:32:37 +0200 (MET DST)


On 4 Oct 1999, H. Peter Anvin wrote:
> The limit is 512, not 256. Anyhow, it has been agreed that this
> really takes too much kernel memory; [...]

Why? It takes 16KB (it can be slightly compressed), eg. NLS translation
tables waste 768 bytes each (probably more) and they are in the kernel.
Inode structure takes more than 256 bytes (because ext2 private fields
are so big without reason)...

Nobody will use unicode on low-end i386 router because it's usable
only on workstation anyway. Workstations have 16MB at least so it takes
1/1000 unswapable memory at most. Memory cost is not importand.

> [...] and you'd be better off running a
> frame buffer anyway. There really is no reason for the frame buffer
> to have a limit below 2048; the 2048-character limit comes from the
> width of the "direct to font" window (U+F000 to U+F7FF).

Why on framebuffer unicode is ok, but on VGA isn't?
(BTW: Who uses "direct to font"?)

jb

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/