All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: font in open firmware
Date: Sun, 28 Aug 2005 15:06:12 +0200	[thread overview]
Message-ID: <200508281506.12774.okuji@enbug.org> (raw)
In-Reply-To: <87u0hfur11.fsf@student.han.nl>

On Wednesday 24 August 2005 20:30, Marco Gerards wrote:
> Can you please explain why this is important and what you mean?  AFAIK
> the console font on the new world apple is fixed width.  On the
> pegasos a text screen just like the PC is used.

Maybe this is the second time, but I talk about it.

It completely depends on the implementation of a terminal how characters are 
displayed. For example, some are capable of displaying wide characters, while 
others do not support them so display merely dummy characters. Or, some want 
to display the border characters used in the menu interface in a single 
width, while others may want to display them as two-column characters.

Even if an underlying system does not support wide characters, you can often 
emulate such support by combining multiple 1-column characters on the 
display. This is feasible only if a target language has a small set of 
characters in comparison with the size of a font area in a firmware.

BTW, the VGA font used in standard PCs is not only ASCII characters but also 
has extra characters. There is a table in the wikipedia:

http://en.wikipedia.org/wiki/CP437

Does pegasos support the same character set?

Okuji



      reply	other threads:[~2005-08-28 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20  5:39 font in open firmware Yoshinori K. Okuji
2005-08-21  7:27 ` Yoshinori K. Okuji
2005-08-24 18:30 ` Marco Gerards
2005-08-28 13:06   ` Yoshinori K. Okuji [this message]

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=200508281506.12774.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.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.