Followup to: <[EMAIL PROTECTED]>
By author: Tomohiro KUBOTA <[EMAIL PROTECTED]>
In newsgroup: linux.utf8
>
> Hi,
>
> At Fri, 29 Jun 2001 15:58:00 +0200 (CEST),
> Bruno Haible <[EMAIL PROTECTED]> wrote:
>
> > > Personally I would suggest making this kind of user-space console
> > > software the default
> >
> > These consoles rely on the framebuffer console.
>
> Though "jfbterm" rely on framebuffer (and require Linux 2.2
> or later), "kon" does not (and works with older Linux kernel).
> [According to the changelog file of "kon", the first test
> release was 1992-10-13, obviously when framebuffer was not
> available.]
>
> However, I don't know whether Unicode can be implemented
> without framebuffer. Just an information.
>
Sure it can. The standard console does, and you could do it on top of
libvga, or whatever. It's just a matter on what level of support.
Building on top of the framebuffer driver is probably a good idea. It
still puts the glyphs and terminal emulation code in user space, which
is probably the Right Thing<TM> to do, especially considering CJK
(extrememly large glyph set), Indic and Arabic scripts (complex
shaping rules), as well as combining characters etc.
Having a single *good* user space console would be a lot better than
different ones for CJK, Arabic, Indic, etc. Getting it used for
Western languages, too, would help speed up development even further.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
