From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] move functionality of font_path() directly to util/grub-mkconfig.in and prefer unicode.pf2 over ascii.pf2
Date: Fri, 7 Aug 2009 13:39:28 +0200 [thread overview]
Message-ID: <20090807113928.GM6695@thorin> (raw)
In-Reply-To: <1249551551.3663.7.camel@fz.local>
On Thu, Aug 06, 2009 at 11:39:11AM +0200, Felix Zielcke wrote:
> + for dir in ${pkgdatadir} /boot/grub /usr/share/grub ; do
> + for basename in unicode unifont ascii; do
> + path="${dir}/${basename}.pf2"
> + if is_path_readable_by_grub ${path} > /dev/null ; then
> + GRUB_FONT_PATH=${path}
> + else
> + continue
> + fi
> + if [ "${basename}" = "ascii"] ; then
> + # make sure all our children behave in conformance with ascii..
> + export LANG=C
> + fi
> + break 2
> + done
> + done
> + if [ -z "${GRUB_FONT_PATH}" ] ; then
> + # fallback to the native terminal for this platform
> + unset GRUB_TERMINAL_OUTPUT
> + fi
> fi
> ;;
> -esac
> -
> -# does our terminal support utf-8 ?
> -case ${GRUB_TERMINAL_OUTPUT} in
> - gfxterm) ;;
> *)
> # make sure all our children behave in conformance with ascii..
> export LANG=C
> - ;;
> esac
It seems that "export LANG=C" is issued twice?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-07 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:39 [PATCH] move functionality of font_path() directly to util/grub-mkconfig.in and prefer unicode.pf2 over ascii.pf2 Felix Zielcke
2009-08-07 11:39 ` Robert Millan [this message]
2009-08-07 12:02 ` Felix Zielcke
2009-08-07 12:57 ` Felix Zielcke
2009-08-08 5:12 ` Pavel Roskin
2009-08-08 5:36 ` Felix Zielcke
2009-08-08 5:41 ` Felix Zielcke
2009-08-08 5:49 ` Pavel Roskin
2009-08-08 6:04 ` Felix Zielcke
2009-08-08 6:35 ` Pavel Roskin
2009-08-08 6:41 ` Felix Zielcke
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=20090807113928.GM6695@thorin \
--to=rmh@aybabtu.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 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.