public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Albert Cahalan <acahalan@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, aeb@cwi.nl, hpa@zytor.com
Subject: Re: console font limits
Date: Tue, 1 May 2007 18:06:20 +0100	[thread overview]
Message-ID: <20070501170620.GA12118@deepthought> (raw)
In-Reply-To: <787b0d920704302109r352e6653wc71a0638cbfbdcce@mail.gmail.com>

On Tue, May 01, 2007 at 12:09:46AM -0400, Albert Cahalan wrote:
> 
> BTW, the PSF font format documentation seems to suggest that
> there is a way to make the kernel handle combining accents:
> http://www.win.tue.nl/~aeb/linux/kbd/font-formats-1.html
> Does anybody know if that really works? I could sure use that.

 My reading of it suggests you need a precomposed version to which
the combining combination can be mapped (the 00c5 for Å in the
example).  Possibly, the fffe and ffff are used as delimiters for
the combination).  Maybe, it could be used for yoruba (yeah, I was
looking at that an hour before I read your mails) _if_ the font
has room to fit in a "private use" character which can hold the
precomposed value.

 For any letter where a precomposed version is in the unicode
standards, the only use for combining characters in a console font
seems to be as a way of displaying text where somebody has already
used them.

 For latin languages which need additional composed letters, the
bigger problem will probably be the input - I've no idea if the
console keymap can use combining keys (direct input of the unicode
hex is available, of course), and I can't manage to get the direct
input of the codes for combining diacriticals to work in combination
in my preferred graphical terminal.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  parent reply	other threads:[~2007-05-01 17:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  4:09 console font limits Albert Cahalan
2007-05-01 11:49 ` Geert Uytterhoeven
2007-05-01 12:11   ` Antonino A. Daplas
2007-05-01 15:05     ` H. Peter Anvin
2007-05-01 15:49       ` Albert Cahalan
2007-05-02 18:02         ` Jan Engelhardt
2007-05-03  6:17           ` Albert Cahalan
2007-05-03  7:12             ` Jan Engelhardt
2007-05-03 14:14               ` Albert Cahalan
2007-05-03 14:26                 ` Jan Engelhardt
2007-05-03 15:56                   ` Geert Uytterhoeven
2007-05-03 18:27                     ` Jan Engelhardt
2007-05-03 20:15                       ` H. Peter Anvin
2007-05-03 20:16                         ` Jan Engelhardt
2007-05-04  0:17                           ` Kyle Moffett
2007-05-04  0:39                             ` H. Peter Anvin
2007-05-04  3:58                               ` Daniel Hazelton
2007-05-04  4:59                                 ` Antonino A. Daplas
2007-05-04 15:34                                   ` Jesse Barnes
2007-05-06 23:35                                     ` Daniel Hazelton
2007-05-03  7:19         ` H. Peter Anvin
2007-05-03  7:45           ` Helge Hafting
2007-05-03 10:20           ` Alan Cox
2007-05-01 17:06 ` Ken Moffat [this message]
2007-05-03 17:11 ` Andries Brouwer

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=20070501170620.GA12118@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=acahalan@gmail.com \
    --cc=aeb@cwi.nl \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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