From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: microcai@fedoraproject.org
Cc: linux-console@vger.kernel.org
Subject: Re: [PATCH 1/2] Kernel fbcon UNICODE font support
Date: Sat, 27 Nov 2010 13:53:30 +0000 [thread overview]
Message-ID: <20101127135330.5e32a45a@pyx> (raw)
In-Reply-To: <1290837149.677.4.camel@cai.gentoo>
> Think about w3m, It must run on framebuffer to display pictures.
> But, I must run on fbterm to display CJK characters .....
So you want a windowing layer - thats a user space problem. You need that
anyway to keep the pictures and the text in the right places relative to
one another and to handle events.
> Well, if you have that time, please find out those softwares that need
> to rewrite, and, send patches to them. I'm sure they will just reply :
> why not handle UNICODE in kernel ?!
Which has been answered, if you want to run multiple graphical apps on a
framebuffer use a windowing system like everyone else does, and I would
imagine "use X" is what most of the software people would tell you.
next prev parent reply other threads:[~2010-11-27 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 10:02 [PATCH 1/2] Kernel fbcon UNICODE font support Microcai
2010-11-26 10:02 ` Microcai
2010-11-26 10:09 ` Alan Cox
2010-11-26 10:19 ` microcai
[not found] ` <1F1E2EC1077B4BA58A16D9D3B458A7FD@avitech.sk>
2010-11-26 10:32 ` microcai
2010-11-26 10:41 ` Alan Cox
[not found] ` <AANLkTi=T7pfTP0xHmGqLCSj_8vq_kRijCp5NF+VeBz_f@mail.gmail.com>
[not found] ` <20101126104818.1e8f6511@lxorguk.ukuu.org.uk>
2010-11-26 10:53 ` microcai
2010-11-26 11:03 ` microcai
2010-11-26 11:42 ` Alan Cox
2010-11-26 11:53 ` Microcai
2010-11-26 23:25 ` Alan Cox
2010-11-27 5:52 ` Microcai
2010-11-27 13:53 ` Alan Cox [this message]
2010-11-29 1:42 ` microcai
2010-11-29 8:52 ` Samuel Thibault
2010-11-27 8:19 ` Microcai
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=20101127135330.5e32a45a@pyx \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-console@vger.kernel.org \
--cc=microcai@fedoraproject.org \
/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.