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: terminal enhancement
Date: Sat, 18 Sep 2004 16:32:21 +0200	[thread overview]
Message-ID: <200409181632.21893.okuji@enbug.org> (raw)

To support Unicode in the menu interface, I think we need to add one 
more function into the terminal system. For now, the menu only thinks 
about ASCII characters. So the number of bytes in a string is identical 
to the number of columns to be used for displaying the string.

This is not true, generally speaking. In UTF-8, most Latin characters 
are 2-bytes but one column is used to show each character. Simply 
speaking, width(string) != length(string).

In POSIX, the function wcwidth is defined to get the width of a string 
of wide characters. We need a similar function in GRUB.

Basically, only terminal drivers know how many columns are used for a 
given string. If a terminal driver uses the font manager completely, we 
can get the information from the font manager, but not all terminals 
use the font manager (such as the PC console).

So I'd like to propose adding a new member 'getwidth' into struct 
grub_term. This function would be like this:

int
getwidth (grub_uint32_t code)
{
  /* CODE is encoded in UCS-4.  */

  /* Do something here.  */

  width = ...;
  return width;
}

Anyway, you need this kind of function to implement a terminal.

What do you think?

Okuji



             reply	other threads:[~2004-09-18 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 14:32 Yoshinori K. Okuji [this message]
2004-09-19 11:07 ` terminal enhancement Marco Gerards
2004-09-19 14:35   ` Yoshinori K. Okuji
2004-09-19 14:51     ` Marco Gerards

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=200409181632.21893.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.