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: jerone@gmail.com
Subject: Re: [PATCH] GSoC #10 new font engine (UTF-8 support+bugfix)
Date: Sun, 4 Jan 2009 23:59:49 -0800	[thread overview]
Message-ID: <20090104235949.7129e59f@gibibit.com> (raw)
In-Reply-To: <9f50a7a00901042105p1f1b7e8ep83b9c1b36775c033@mail.gmail.com>

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

On Sun, 4 Jan 2009 23:05:40 -0600
"Jerone Young" <jerone@gmail.com> wrote:

> File util/fonttool/src/org/gnu/grub/fonttool/PFF2Loader.java didn't
> make it into the repository.
> 
>               Jerone

Oops!  You're right; my patch is irrelevant since PFF2Loader.java is
used only for the 'Viewer' tools, which Vesa decided not to include.
I had not yet synced with GRUB SVN since Vesa checked in the font
utilities, so I was working with my own feature branch.

Never mind, then.  I can still do a temporary hack to support building
the font converter tool with gcj.  I made this work in my shell script,
and though I think doing it properly would require some autotools
magic, I could add a quick-and-dirty target to a makefile to build
using gcj.  Should I try to do this?

Regards,
Colin


> On Sat, Jan 3, 2009 at 10:45 AM, Colin D Bennett <colin@gibibit.com>
> wrote:
> 
> > On Fri, 2 Jan 2009 16:44:49 -0600
> > "Jerone Young" <jerone@gmail.com> 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 ?
> >
> > The font tool does work with gcj (gcc's Java compiler).  I just had
> > to make a trivial change (see attached) since gcj 4.3.2 does not yet
> > implement the String(byte[], Charset) constructor.
> >
> > Regards,
> > Colin
> >

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

  reply	other threads:[~2009-01-05  9:02 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
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 [this message]
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=20090104235949.7129e59f@gibibit.com \
    --to=colin@gibibit.com \
    --cc=grub-devel@gnu.org \
    --cc=jerone@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox