All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Video subsystem draft
Date: Tue, 22 Nov 2005 21:06:27 +0200	[thread overview]
Message-ID: <43836C33.5090508@nic.fi> (raw)
In-Reply-To: <200511181206.49374.okuji@enbug.org>

Yoshinori K. Okuji wrote:
> On Friday 18 November 2005 12:19 am, Vesa Jääskeläinen wrote:
>> What is the procedure to generate font file to font manager? Or should I
>>  just add some functionality to import VGA font to font manager.
> 
> First, download unifont.hex from <http://czyborra.com/unifont/HEADER.html>. 
> Then, convert it with util/unifont2pff.rb. If you invoke this script with no 
> argument, you can a short summary of the usage. Let's say, you store the font 
> in unifont.pff, then the command is "ruby util/unifont2pff.rb unifont.hex > 
> unifont.pff". Now you can put this generated file under /boot/grub, and load 
> it by the command "font".
> 
> You can also specify specific code ranges to unifont2pff.rb, if you need only 
> a subset of supported glyphs. This is necessary if you want to use the 
> ancient technology called "floppy".

I think it can be gzipped to fit more nicely :).. (and it seems to work
too).

But even without gzipping it, I am having some problems with it. I don't
think this is a problem in font manager.

> Honestly, I haven't tried the font manager for a long time. So I won't be 
> surprised even if I hear it is not working well. But last time I tried it (it 
> was not GRUB 2, but PUPA), it worked well and I saw a menu with Japanese 
> titles.

After something calls grub_error first read from font file fails, with
grub_file_read() == -1. Now this causes font manager to drop font from
memory. If I disable feature that I can see that first character is
invalid and others come nicely. In case of "error: ..." first 'e' is
corrupt and rest is ok. I am not sure is this really issue in grub_error
 itself but it is in sequence when problem shows up.

I can't find problem in font manager, even the offset that is tries to
seek is within limits of the file (and correct) and there is enough
bytes left in file in order to successfully complete the read.

I can send tarred version of grub2 with video subsystem if someone wants
to help on this one. I will continue to search for possible problems in
case I can pinpoint and fix it.

Is the font file using some standard format or can it's contents be
changed? Bitmap data for fonts could be placed in better order to more
easily to render it (currently I modify byte order before giving it to
glyph renderer). (My guess is that it is [P]upa [F]ont [F]ormat or file)



  reply	other threads:[~2005-11-22 19:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 11:24 Video subsystem draft Vesa Jääskeläinen
2005-10-23 15:03 ` Timothy Baldwin
2005-10-23 15:24   ` Vesa Jääskeläinen
2005-10-28  3:21 ` Yoshinori K. Okuji
2005-10-28 13:59   ` Vesa Jääskeläinen
2005-11-17 23:19     ` Vesa Jääskeläinen
2005-11-18 11:06       ` Yoshinori K. Okuji
2005-11-22 19:06         ` Vesa Jääskeläinen [this message]
2005-11-25 20:25           ` Yoshinori K. Okuji
2005-11-26  0:28             ` Vesa Jääskeläinen
2005-11-26 14:36               ` Vincent Pelletier
2005-11-26 19:54                 ` Yoshinori K. Okuji
2005-11-27  1:48                 ` Vesa Jääskeläinen
2005-12-09 22:44                   ` Marco Gerards
2005-12-10  0:19                     ` Yoshinori K. Okuji
2005-12-10 10:31                     ` Vesa Jääskeläinen
2005-12-10 21:01                       ` Marco Gerards
2005-12-10 21:23                         ` Vesa Jääskeläinen
2005-12-10 20:48                     ` Vesa Jääskeläinen
2005-12-10 21:15                       ` Marco Gerards
2005-12-10 22:14                         ` Vesa Jääskeläinen
2005-12-10 22:32                           ` Marco Gerards
2005-12-10 23:11                             ` Vesa Jääskeläinen
2005-11-27  2:00                 ` Vesa Jääskeläinen
2005-11-26 19:52               ` Yoshinori K. Okuji
2005-11-27  2:09                 ` Vesa Jääskeläinen
2005-12-09 22:33                   ` Marco Gerards
2005-11-28 21:29               ` Vesa Jääskeläinen
2005-12-06 15:18                 ` Vesa Jääskeläinen

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=43836C33.5090508@nic.fi \
    --to=chaac@nic.fi \
    --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.