From: Alan Cox <alan@linux.intel.com>
To: Frank Pan <frankpzh@gmail.com>
Cc: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>,
Kay Sievers <kay.sievers@vrfy.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Daniel Mack <daniel@caiaq.de>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Jiri Slaby <jirislaby@gmail.com>, Jochen Hein <jochen@jochen.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Dave Airlie <airlied@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Geert Uytterhoeven <geert@linux-m68k.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Enlarge the storage of chars in virtual terminal
Date: Thu, 27 May 2010 11:57:16 +0100 [thread overview]
Message-ID: <20100527115716.76ce299a@linux.intel.com> (raw)
In-Reply-To: <AANLkTikuzGazcBpSvqU73UAAIvcTgxTBsmWTr9bNCSjB@mail.gmail.com>
> 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
next prev parent reply other threads:[~2010-05-27 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 6:55 [PATCH 0/2] Enlarge the storage of chars in virtual terminal Frank Pan
2010-05-26 6:59 ` [PATCH 1/2] " Frank Pan
2010-05-26 7:02 ` [PATCH 2/2] " Frank Pan
2010-05-26 14:11 ` [PATCH 0/2] " Alan Cox
2010-05-27 6:00 ` Frank Pan
2010-05-27 6:52 ` Tejun Heo
2010-05-27 8:59 ` Frank Pan
2010-05-27 9:30 ` Tejun Heo
2010-05-27 12:53 ` Frank Pan
2010-05-27 10:57 ` Alan Cox [this message]
2010-05-27 13:15 ` Frank Pan
2010-05-27 13:41 ` Olivier Galibert
2010-05-27 13:46 ` Frank Pan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100527115716.76ce299a@linux.intel.com \
--to=alan@linux.intel.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux-foundation.org \
--cc=daniel@caiaq.de \
--cc=frankpzh@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=hannes@cmpxchg.org \
--cc=jirislaby@gmail.com \
--cc=jochen@jochen.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=tj@kernel.org \
--cc=vmlinuz386@yahoo.com.ar \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.