linux-console.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: microcai <microcai@fedoraproject.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-console@vger.kernel.org
Subject: Re: [PATCH 1/2] Kernel fbcon UNICODE font support
Date: Mon, 29 Nov 2010 09:52:19 +0100	[thread overview]
Message-ID: <20101129085219.GL5142@const.bordeaux.inria.fr> (raw)
In-Reply-To: <AANLkTim-S7XcZgKHvGJMG-71B8-73aZ1AX5EFXefcW=w@mail.gmail.com>

microcai, le Mon 29 Nov 2010 09:42:30 +0800, a écrit :
> >> 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.
> 
> think of w3m. which runs on framebuffer, so ,fbterm is useless here.
> But w3m uses framebuffer to draw pictures, not characters.
> So, if you want nice output, enable UNICODE font in kernel will be the
> best way rather than hacking into the w3m code.

Well, fbterm shouldn't prevent applications from being able to draw on
the console.  That's where the fix could go too (and it makes a lot of
sense).

> if you hack one w3m ,there will be another one that need this kinds of hack ....
> implement it in kernel was/is/will be the best choice.

The kernel will never accept good enough support for all kind of unicode
script.  Think of arabic ligatures, tibetan combinations, etc.  You
don't want to put a rendering engine for these in the kernel.  fbterm is
there for that.

Samuel
--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-29  8:52 UTC|newest]

Thread overview: 15+ 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: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
2010-11-29  1:42                         ` microcai
2010-11-29  8:52                           ` Samuel Thibault [this message]
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=20101129085219.GL5142@const.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=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 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).