Grub Development Archive on 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: bean123ch@gmail.com
Subject: Re: [PATCH] GSoC #10 new font engine (UTF-8 support+bugfix)
Date: Fri, 2 Jan 2009 23:30:36 -0800	[thread overview]
Message-ID: <20090102233036.35efa846@gibibit.com> (raw)
In-Reply-To: <ca0f59980901022052p76be272dgb21b49f441faa332@mail.gmail.com>

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

On Sat, 3 Jan 2009 12:52:51 +0800
Bean <bean123ch@gmail.com> wrote:

> On Sat, Jan 3, 2009 at 6:57 AM, Vesa Jääskeläinen <chaac@nic.fi>
> wrote:
> > Jerone Young wrote:
> >> I just paid attention to this (sorry). So everything seems fine.
> >> But the dependency on  a proprietary java stack  to generate fonts
> >> isn't good. Does it happen to work with gcc java ?
> >
> > Paying attention is not a bad thing as such :)
> >
> > Never tried it myself but it should work. There isn't anything
> > special on it. As long as Java 1.5 is being supported.
> >
> > Anyway... idea was to get rid of it as soon as possible. I just
> > didn't feel right to hold features because of this.
> 
> Hi,
> 
> I think we can use freetype2 library. It supports both bitmap and
> outline fonts, and we don't need to parse font file ourselves.

That's an idea worth looking into.  I did look into it early on in the
graphical menu design process, and I can't recall why I abandoned the
idea at the time.

> BTW, where can I find document on the new font format ?

See <http://grub.gibibit.com/New_font_format>
or its mirror on the GRUB wiki, <http://grub.enbug.org/FontFormat>.

Regards,
Colin

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

  reply	other threads:[~2009-01-03  7:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 16:27 [PATCH] GSoC #10 new font engine Colin D Bennett
2008-10-05  4:46 ` [PATCH] GSoC #10 new font engine (vs r1885) Colin D Bennett
2008-10-05  8:50   ` Vesa Jääskeläinen
2008-10-30 19:11     ` [PATCH] GSoC #10 new font engine (UTF-8 support) Colin D Bennett
2008-10-31  3:57       ` [PATCH] GSoC #10 new font engine (UTF-8 support+bugfix) Colin D Bennett
2008-10-31 18:31         ` Matt Sturgeon
2008-10-31 19:50           ` Colin D Bennett
2008-11-04 20:19             ` Vesa Jääskeläinen
2008-11-04 20:31               ` Robert Millan
2008-11-04 20:52                 ` Colin D Bennett
2008-12-06 20:18         ` Vesa Jääskeläinen
2008-12-22 17:14           ` Colin D Bennett
2008-12-23 18:39             ` Vesa Jääskeläinen
2008-12-24  1:17               ` Colin D Bennett
2008-12-28  0:34                 ` Vesa Jääskeläinen
2008-12-28  0:35                   ` Vesa Jääskeläinen
2009-01-02 15:26                     ` Vesa Jääskeläinen
2008-12-28  8:44                   ` Arthur Marsh
2009-01-02 22:44                   ` Jerone Young
2009-01-02 22:57                     ` Vesa Jääskeläinen
2009-01-03  4:52                       ` Bean
2009-01-03  7:30                         ` Colin D Bennett [this message]
2009-01-03 16:45                     ` Colin D Bennett
2009-01-03 16:54                       ` Vesa Jääskeläinen
2009-01-05  5:05                       ` Jerone Young
2009-01-05  7:59                         ` Colin D Bennett
2009-01-05 13:29                           ` Jerone Young

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=20090102233036.35efa846@gibibit.com \
    --to=colin@gibibit.com \
    --cc=bean123ch@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox