From: Olivier Galibert <galibert@pobox.com>
To: Alan Cox <alan@linux.intel.com>
Cc: Frank Pan <frankpzh@gmail.com>,
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 15:41:20 +0200 [thread overview]
Message-ID: <20100527134120.GA44150@dspnet.fr> (raw)
In-Reply-To: <20100526151152.28deaa6c@linux.intel.com>
On Wed, May 26, 2010 at 03:11:52PM +0100, Alan Cox wrote:
> On Wed, 26 May 2010 14:55:04 +0800
> Frank Pan <frankpzh@gmail.com> wrote:
>
> > Greetings
> >
> > The motivation is display much more characters on the
> > framebuffer console than 512. If this is done, foreign
> > languages can be easily rendered with currently supported
> > utf-8 encoding.
>
> This has been suggested a couple of times but unfortunately it's not
> enough to use bigger fonts. Rendering many non western languages is far
> far more complex. In addition the text mode vt driver is limited to 512
> symbols by the hardware.
The Unicode book should be required reading for anyone who starts
talking about displaying utf-8/unicode text. It's a *very*
interesting book with way more than code charts in it[1].
OG.
next prev parent reply other threads:[~2010-05-27 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 6:55 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
2010-05-27 13:15 ` Frank Pan
2010-05-27 13:41 ` Olivier Galibert [this message]
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=20100527134120.GA44150@dspnet.fr \
--to=galibert@pobox.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome