[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100527115716.76ce299a@linux.intel.com>
Date: Thu, 27 May 2010 11:57:16 +0100
From: Alan Cox <alan@...ux.intel.com>
To: Frank Pan <frankpzh@...il.com>
Cc: Gerardo Exequiel Pozzi <vmlinuz386@...oo.com.ar>,
Kay Sievers <kay.sievers@...y.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Catalin Marinas <catalin.marinas@....com>,
Daniel Mack <daniel@...aq.de>, Tejun Heo <tj@...nel.org>,
Christoph Lameter <cl@...ux-foundation.org>,
Jiri Slaby <jirislaby@...il.com>,
Jochen Hein <jochen@...hen.org>,
Johannes Weiner <hannes@...xchg.org>,
Dave Airlie <airlied@...hat.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] Enlarge the storage of chars in virtual terminal
> Why is it complex?
You'd have to take that up with the orthographers and historians
> IMHO Rendering non-western languages is nothing
> more than rendering 2 ASCII chars. The current mainline kernel
It is a lot more. Things like arabic vowel handling for example, or
mixed direction text.
> IMHO A user space application doing such thing is just
> re-implementation of virtual terminal support, without the 512
> limitation. Why does we keeping re-inventing the wheel?
Pango does the job. Pango is the wheel.
Kernel code is unpageable, privileged and unable to doing things
trivially like dynamic font management. It's the wrong place for this
kind of stuff because doing fonts right and especially doing language
rendering right is *hard*.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists