From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Bugs in GfxMenu
Date: Sun, 16 Jan 2011 12:50:30 +0100 [thread overview]
Message-ID: <4D32DB86.4000908@gmail.com> (raw)
In-Reply-To: <AANLkTinntN25yMQcNWsmR+eksnJV6S7NfR3=mkE-8Hd5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]
On 01/14/2011 02:02 AM, Matt Sturgeon wrote:
> Another major bug is that GRUB does not load fonts used by themes automatically.
>
> update-grub or grub-mkconfig should parse the theme configuration file
> (usually theme.txt) referanced by /etc/default/grub and load fonts in
> the directory (and sub-directories) of the theme file.
> Or, better still, fonts could be installed to /usr/share/grub/fonts,
> /boot/grub/fonts or /boot/grub/fonts (depending on the directory
> choosen by GRUB developers, not theme developers/users) and use that
> as a standard directory to store fonts for autoload if called by the
> choosen theme during the process of running update-grub or
> grub-mkconfig.
>
>
All fonts in theme directory (the directory containing theme.txt file)
are loaded as long as they have pf2 extension.
> Therefore, there is no neccisessity to place scripts into /etc/grub.d/
> just to have GRUB include fonts.
>
> On 14 January 2011 00:54, Matt Sturgeon <mttza1@gmail.com> wrote:
>
>> Hi, as demonstrated by the attatched screenshots, the following key
>> undesireble behaviour is beeing displayed by gfxmenu in GRUB 1.99:
>>
>> * No icons are beeing printed for Ubuntu (probobly all Operating Systems)
>> * The selected pixmap is beeing drawn at a larger scale than the Boot Menu.
>> * The boxes with pixmaps (Selected, Boot Menu and Terminal) should
>> draw all content within the '_c.png' pixmap, as this is the center or
>> "content" area or the pixmap - this is mainly noticed in the terminal,
>> as the contend is printed OVER the north ('_n.png') pixmap.
>> * The Terminal prints a black background, even though the '_c.png' is
>> designed to be used as the content-background.
>>
>> Thanks for the good work.
>>
>>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-01-16 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 0:54 Bugs in GfxMenu Matt Sturgeon
2011-01-14 1:02 ` Matt Sturgeon
2011-01-16 11:50 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-01-16 11:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-02-07 21:23 ` Matt Sturgeon
2011-02-08 0:50 ` Matt Sturgeon
2011-04-18 22:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4D32DB86.4000908@gmail.com \
--to=phcoder@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;
as well as URLs for NNTP newsgroup(s).