All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qianqian Fang <fangqq@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: fonts for gfxmenu, help needed
Date: Fri, 27 Nov 2009 20:46:59 -0500	[thread overview]
Message-ID: <4B108113.5010407@gmail.com> (raw)
In-Reply-To: <a5d587fb0911270142jb327bf6r2c4e9d1fb0b933e3@mail.gmail.com>

Michal Suchanek wrote:
> Thanks for these tips. I guess wider by one px is acceptable for an
> alternate font, the fonts need not be displayed both at the same time.
> I am not sure if lower quality glyphs of correct shape are preferred
> over higher quality Chinese glyphs, though. I guess it would also
> depend on reader preference but it would be nice to hear the opinion
> of somebody familiar with Japanese.
>   

Using different fonts for different language makes life easier.

> For me the Song/Mincho variant fonts seem more readable at small
> sizes. Although the serifs aren't clearly visible they often add
> weight to the stroke ends and make them easier to recognize. However,
> this may be matter of preference/reader familiarity with the
> language/overall font quality/...
>
> I think that there is not much need for smaller fonts than the default
> 16px/12pt Unifont. It would be nice addition to have a font for
> fine-print but I am personally more interested in larger font sizes
> for captions or simple menus on high resolution screens.
>
> In the larger sizes the difference between different font styles is
> more visible.
>   

I misunderstood the call. You want to have fonts larger than 12pt,
not smaller, as we usually concern. That's fine, actually that is
a lot easier to handle.

I don't know what sizes you prefer, you can find bitmap resources
at typical sizes at 24px/32px/48px. Indeed, using freetype/autohint,
the rasterization of the popular CJK fonts may entirely usable
at these sizes.

In the following links, I experimented to hint/instruct/rasterize
the common CJK fonts, and I think the results are quite usable:

Hei-style:
  WQY Micro Hei@24px: http://wenq.org/upload/microhei_24px.png
  WQY Micro Hei@32px: http://wenq.org/upload/microhei_32px.png

Song-style:
  Japanese Mincho@24px (efont f24): 
http://wenq.org/upload/efont_micho_24px.png
  Chinese Song@32px (uming): http://wenq.org/upload/uming_32px.png

Except the efont 24px, all screenshots were made by rasterizing
vector fonts with freetype2 with autohints. Here are the steps
to reproduce:

1. open a TTF/TTC files in fontconfig, navigate to CJK zone (U4E00-U9FCB)
2. select tens to hundreds of glyphs, select menu Hint\Autohint
3. then, goto menu Element\Font Info...\PS Private, hit Add and add
   multiple PS hints, include StdHW and StdVW, use the guessed values
4. select menu Hint\AutoInstruct
5. select menu Element\Bitmap Strikes Available\, type whatever
   pixel sizes you want in the 3rd box, check freetype, and click ok
6. now from menu View, select the strike you just generated

As I mentioned earlier, if you want to produce Japanese Hei-style
Kanji bitmaps, you can apply the above procedures to
DroidSansJapanese. And of course, the bigger the size, the better the
results.

Let me know if you need any additional information.



  reply	other threads:[~2009-11-28  1:47 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 [this message]
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
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=4B108113.5010407@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.