All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: fonts for gfxmenu, help needed
Date: Wed, 25 Nov 2009 14:17:11 +0100	[thread overview]
Message-ID: <4B0D2E57.9060203@gmail.com> (raw)
In-Reply-To: <a5d587fb0911250429n119d07a7h8fc02f30fc06a447@mail.gmail.com>

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

Michal Suchanek wrote:
> 2009/11/25 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>   
>> Michal Suchanek wrote:
>>     
>>> The difference is that the font is only a bitmap whereas scaling
>>> inside grub can do blending which should give much better results than
>>> scaling bitmap into another bitmap.
>>>
>>>
>>>       
>> What do you mean by blending? Do you mean pixels with alpha channels?
>>     
>
> I mean that you can render the font bitmap in its native size to a
> 32bit surface and use the bilinear scaling feature to resize that, for
> example. 
It's equivalent to have partially transparent pixels
> The advantage of on-the-fly scaling is that you really need
> only a single font, the differently sized glyphs are created as
> needed. The disadvantage over native fonts of different sizes is, of
> course, lower quality.
>   
I still don't think on-the-fly scaling, especially complicated one is a
good solution to a problem.
I think the est way is to find a set of TrueType fonts with adapted
typefaces, render them to different sizes and add unifont as fallback.
We could use on-the-fly cached scaling for unifont fallback and so its
slowness will be less of a problem and may be better alternative than
time required to load multiple versions of unifont. Also quality in this
case is less of an issue too.
> That doesn't really help. There isn't really a canonical reading every
> Chinese speaking person is supposed to understand, and even if you
> choose one as the standard it's not possible to derive the meaning of
> a word from the reading but it is possible from the Chinese character.
>   
Chinese people are usually familiar with either pinyin or
Cantonese-based transliteration since they are widely used in Input Methods
> Hebrew and Arabic use letters that correspond to consonants so anybody
> who knows the language and Latin alphabet should be able to read a
> Latin transcription, though possibly with gritting teeth.
>
>   
Transliterating Arabic isn't good idea. It will make GRUB look like a
big SMS
But we don't speak of same issues either. The only issues is that
Japanese or Chinese may see a similar symbol with similar rendering but
from other language. It may be unnice but is understandable. If we
really care about right symbol I suggest to use glyph variant codes.
>> similar for Arabic.
>> In worst case we can just say Japanese people to install Japanese fonts
>> only and bear with Chinese having a bit wrong rendering and vice-versa.
>>     
>
> Yes, that's certainly a possibility but one has to be aware of this
> limitation and perhaps mention it somewhere.
>
> Thanks
>
> Michal
>
>
> _______________________________________________
> 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: 293 bytes --]

  reply	other threads:[~2009-11-25 13:17 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 12:10 fonts for gfxmenu, help needed 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2009-11-26  4:38 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
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

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=4B0D2E57.9060203@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 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.