From: Qianqian Fang <fangqq@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: fonts for gfxmenu, help needed
Date: Sun, 29 Nov 2009 21:15:17 -0500 [thread overview]
Message-ID: <4B132AB5.2030202@gmail.com> (raw)
In-Reply-To: <4B12CD51.9080401@gmail.com>
Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> AFAIK Hanja isn't used a lot and in GRUB2 particularly I see only names
> which could possibly use Hanja. Also quick look into ko.po of glibc
> doesn't reveal any Hanja (even that I can't read either they have
> different appearence). But due to nature of Hangul of being basically
> arranged syllables out of Jamo we need to include whole 111712
> precomposed Hangul. And since even important font rendering engines
> prefered to stay away from Jamo composing except when with historical
> Jamo I feel like it would be inappropriate to make it in GRUB.
> As for Kanji we could stick to Jōyō kanji
> [http://en.wikipedia.org/wiki/J%C5%8Dy%C5%8D_kanji] (I think we can
> reasonably suppose that all kanji needed for grub2 are within the school
> scope)
> However I don't pretend to be expert in either Kanji, Hanja, Hangul or
> Hanzi, so feel free to correct me.
>
I am pretty sure there are a lot of options. But at this point,
I think I need a clear plan on 1) what pixel sizes, 2) what
the number of Hanzi characters and 3) what font styles (song/hei)
does grub project need.
In my previous emails, I summarized the resources that
I know of, including
1) free pan-unifont vector fonts that cover most CJK/nonCJK scripts
2) bitmap fonts that have CJK coverage at smaller font sizes
3) a procedure to produce better quality rasterization from vector
fonts using fontforge
With these, I think you can pretty much do any combination/slicing
you want. I would be glad help to make these bitmap fonts once
you decide the specs on the fonts (listed above)
> Are there any reasons to believe more sinograms came into general usage
> and may be used by grub since then? Will have anyway to have
> computer-specific glyphs too.
>
no, I don't think so. Ideographic characters are
quite stable now. For general usage, the charset is
fixed. What get evolved are their combinations,
which we called "words", for example, "电脑","手机".
All these characters are ancient, but the combinations
represent something new.
> Is the list you provided about Traditional or Simplified Chinese? What
> about the other variant?
>
IICore is a combination of simplified/traditional/japanese/korean.
http://translate.googleusercontent.com/translate_c?hl=en&ie=UTF-8&sl=zh-CN&tl=en&u=http://zh.wikipedia.org/wiki/%25E5%259C%258B%25E9%259A%259B%25E8%25A1%25A8%25E6%2584%258F%25E6%2596%2587%25E5%25AD%2597%25E6%25A0%25B8%25E5%25BF%2583&prev=_t&rurl=translate.google.com&twu=1&usg=ALkJrhiQIu8BQBujT7zze99y_BlwfOCxZQ
> General-usage fonts are good since they are likely to contain all useful
> (for GRUB) glyphs. It just starts to look that we can't significantly
> reduce the size of unifont by removing not-so-useful glyphs. 10000 for
> Simplified Chinese, 10000 for Traditional Chinese and 10000 for Hangul
> and we already have half of BMP/unifont
>
Maybe start with full BMP and see if you have any particular
difficulties coming up. Re-slice a BDF file is quite eazy.
next prev parent reply other threads:[~2009-11-30 2:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 4:38 fonts for gfxmenu, help needed Qianqian Fang
2009-11-26 9:11 ` Felix Zielcke
2009-11-26 15:27 ` Qianqian Fang
2009-11-26 22:14 ` Michal Suchanek
2009-11-27 0:48 ` Qianqian Fang
2009-11-27 0:51 ` Qianqian Fang
2009-11-27 9:42 ` Michal Suchanek
2009-11-28 1:46 ` Qianqian Fang
2009-11-28 21:53 ` Michal Suchanek
2009-11-28 22:33 ` Qianqian Fang
2009-11-28 22:43 ` Qianqian Fang
2009-11-29 11:19 ` Michal Suchanek
2009-11-29 16:14 ` Qianqian Fang
2009-11-29 16:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-29 17:10 ` Qianqian Fang
2009-11-29 19:36 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-30 2:15 ` Qianqian Fang [this message]
2009-11-30 9:44 ` Michal Suchanek
2009-11-30 15:24 ` Qianqian Fang
2009-11-30 16:10 ` Michal Suchanek
2009-12-05 21:50 ` Michal Suchanek
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 12:10 Robert Millan
2009-11-24 15:27 ` Michal Suchanek
2009-11-24 17:35 ` Robert Millan
2009-11-24 19:06 ` Colin D Bennett
2009-11-24 19:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-24 23:20 ` Robert Millan
2009-11-25 9:01 ` Michal Suchanek
2009-11-25 10:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-25 11:12 ` Michal Suchanek
2009-11-25 11:36 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-25 12:29 ` Michal Suchanek
2009-11-25 13:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-25 13:57 ` feng shu
2009-11-25 16:04 ` Michal Suchanek
2009-11-25 17:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-25 21:51 ` Michal Suchanek
2009-11-26 2:58 ` feng shu
2009-11-26 3:11 ` feng shu
2009-11-25 11:15 ` Michal Suchanek
2009-11-25 11:38 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-24 18:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-24 18:29 ` 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=4B132AB5.2030202@gmail.com \
--to=fangqq@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 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.