linux-console.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Microcai <microcai@fedoraproject.org>, 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: Wed, 15 Dec 2010 16:04:26 +0100	[thread overview]
Message-ID: <20101215150426.GA26989@const.bordeaux.inria.fr> (raw)
In-Reply-To: <20101215144501.GB10467@ucw.cz>

Pavel Machek, le Wed 15 Dec 2010 15:45:02 +0100, a écrit :
> > 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...
> 
> Well... english has ligatures, too (fi);

English ligatures are extremely far from what arabic needs. People
don't even actually know that there are ligatures in English, while for
arabic, people would even have a hard time reading something that isn't
using ligatures.

> console does not support them nicely and we still use it.

Err, I've very rarely seen the fi/ff ligatures on the console, it was
mostly from copy/pastes from pdf documents.

> Support for eastern european characters by default would be very very
> nice... and yes, that's just breaking the 256 char limit, nothing more
> complex.

The console can do 512 glyphs, not only 256, so eastern europe support
is a matter of combining a latin1 font with parts of the other latin
fonts. That already covers a lot of european languages.

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-12-15 15:04 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
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 [this message]
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=20101215150426.GA26989@const.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --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=pavel@ucw.cz \
    --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).