All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: rmh@aybabtu.com
Subject: Re: unicode font slowness (Re: gettext patch (beta))
Date: Sun, 8 Feb 2009 00:47:37 -0800	[thread overview]
Message-ID: <20090208004737.2b0aec6d@gibibit.com> (raw)
In-Reply-To: <20090207212636.GB6343@thorin>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

On Sat, 7 Feb 2009 22:26:36 +0100
Robert Millan <rmh@aybabtu.com> wrote:

> On Thu, Jan 22, 2009 at 12:08:28AM +0200, Vesa Jääskeläinen wrote:
> > 
> > Are you using gfxterm ? If yes, then your font is missing í. Try to load
> > unifont.bf2 or unicode.bf2. I think debian defaults to ascii.bf2 which
> > may not include that glyph.
> 
> Actually, it's us who default to ascii:
> 
> 2008-07-23  Robert Millan  <rmh@aybabtu.com>
> 
> 	[...]
> 
>         * util/update-grub_lib.in (font_path): Prefer ascii.pff over complete
>         fonts, because the latter are too slow.
> 
> before this change, using the complete fonts was incredibly slow in things
> like QEMU or VirtualBox.
> 
> Perhaps there's some way in which this can be optimized, so we can go back to
> using the complete set by default?

I'm optimizing the font rendering now for fonts with many characters.
It was using a linear search (gasp!!) for finding the glyph each time
it is requested.  I just never got around to using the proper data
structure, but I will have this done soon.

I made a text rendering benchmark and added it to 'videotest bench' so
I can objectively measure the improvement achieved.  The improvement
could be significant.  I'll report more later.

Regards,
Colin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-08  8:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 21:17 gettext patch (beta) Carles Pina i Estany
2009-01-21 21:38 ` Vesa Jääskeläinen
2009-01-21 21:48   ` Carles Pina i Estany
2009-01-21 22:08     ` Vesa Jääskeläinen
2009-01-21 22:21       ` Carles Pina i Estany
2009-01-24 10:59         ` Niels Böhm
2009-02-07 21:30           ` Robert Millan
2009-02-07 21:26       ` unicode font slowness (Re: gettext patch (beta)) Robert Millan
2009-02-08  8:47         ` Colin D Bennett [this message]
2009-01-24 14:26 ` gettext patch (beta) Carles Pina i Estany
2009-01-24 15:09   ` Carles Pina i Estany
2009-02-09 14:39   ` Robert Millan
2009-02-10  1:58     ` BandiPat
2009-02-21 13:02       ` "single-user mode" string (Re: gettext patch (beta)) Robert Millan
2009-02-21 16:07         ` BandiPat
2009-02-21 19:49           ` Robert Millan
     [not found]             ` <20090221201015.GA4618@piper.oerlikon.madduck.net>
2009-02-21 21:08               ` Robert Millan
2009-02-22  0:40             ` BandiPat
2009-02-27 21:37               ` Robert Millan
2009-04-10 22:47   ` gettext patch (beta) phcoder
2009-04-14  8:54     ` Carles Pina i Estany

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=20090208004737.2b0aec6d@gibibit.com \
    --to=colin@gibibit.com \
    --cc=grub-devel@gnu.org \
    --cc=rmh@aybabtu.com \
    /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.