From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Microcai <microcai@fedoraproject.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Ted Ts'o <tytso@mit.edu>,
Lisa Milne <lisa@ltmnet.com>,
"jonsmirl@gmail.com" <jonsmirl@gmail.com>,
linux-kernel@vger.kernel.org, linux-console@vger.kernel.org
Subject: Re: VT console need rewrite
Date: Mon, 29 Nov 2010 11:17:02 +0100 [thread overview]
Message-ID: <20101129101702.GS5142@const.bordeaux.inria.fr> (raw)
In-Reply-To: <1291025476.9785.5.camel@cai.gentoo>
Microcai, le Mon 29 Nov 2010 18:11:16 +0800, a écrit :
> 在 2010-11-29一的 10:58 +0100,Samuel Thibault写道:
> > Simple unicode font (i.e. just go beyond the arbitrary historical-vga
> > 512 glyphs limit for fbcon) might go in. Double-width is
> > questionable,
> > but it can probably simple enough to be able to get in (there is
> > already
> > some code for it anyway).
> >
> > But complete unicode support (with arabic ligatures, tibetan
> > combinations, etc.) won't ever be accepted in the kernel as that's far
> > too involved in terms of font rendering. So the userland way needs to
> > be fixed for these anyway, and then things like chinese will go
> > along...
> >
> > Samuel
>
> YES, my patch just include BMP(mostly CJK), not full UNICODE. IF it can
> be included, then I can do more work to make sure it doesn't break old
> stuff. And it's configurable. users don't have to be forced to use.
It seems you didn't get my point: what is the use of including CJK into
kernel when that won't solve the issue for e.g. arabic, while fixing
fbterm will solve the issue for both arabic and CJK?
Samuel
next prev parent reply other threads:[~2010-11-29 10:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 10:57 VT console need rewrite Microcai
2010-11-28 13:24 ` Theodore Tso
2010-11-28 13:42 ` Microcai
2010-11-28 14:05 ` jonsmirl
2010-11-28 14:29 ` Microcai
2010-11-28 14:49 ` jonsmirl
2010-11-28 19:11 ` Samuel Thibault
2010-11-29 1:10 ` Microcai
2010-11-29 2:49 ` Américo Wang
2010-11-29 2:48 ` Microcai
2010-11-29 8:16 ` Samuel Thibault
2010-11-29 8:20 ` microcai
2010-11-29 8:27 ` Samuel Thibault
2010-11-29 8:53 ` Microcai
2010-11-29 8:59 ` Samuel Thibault
2010-11-28 16:06 ` Lisa Milne
2010-11-28 16:20 ` Microcai
2010-11-28 19:46 ` Ted Ts'o
2010-11-29 1:14 ` Microcai
2010-11-29 8:58 ` Samuel Thibault
2010-11-29 9:32 ` Microcai
2010-11-29 9:58 ` Samuel Thibault
2010-11-29 10:11 ` Microcai
2010-11-29 10:17 ` Samuel Thibault [this message]
2010-11-29 10:40 ` Microcai
2010-11-29 10:39 ` Samuel Thibault
2010-12-15 14:45 ` Pavel Machek
2010-12-15 15:04 ` Samuel Thibault
2010-11-29 1:55 ` Alexey Gladkov
2010-11-29 2:14 ` Microcai
2010-11-29 14:02 ` Alan Cox
2010-11-29 17:50 ` Valdis.Kletnieks
2010-11-29 21:23 ` Jerome Glisse
2010-11-28 23:46 ` Alan Cox
2010-11-29 1:28 ` Microcai
2010-11-29 14:07 ` Alan Cox
2010-11-30 5:05 ` microcai
2010-12-20 6:35 ` Pavel Machek
2010-11-29 10:01 ` Andi Kleen
2010-11-29 10:12 ` Microcai
2010-12-07 20:37 ` Jesse Barnes
2010-12-13 7:13 ` Pavel Machek
2010-12-13 10:18 ` Alan Cox
2010-12-15 14:40 ` Pavel Machek
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=20101129101702.GS5142@const.bordeaux.inria.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jonsmirl@gmail.com \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@ltmnet.com \
--cc=microcai@fedoraproject.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).