From: Colin D Bennett <colin@gibibit.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: bean123ch@gmail.com
Subject: Re: Problem with fonts in different width
Date: Sat, 3 Jan 2009 10:06:56 -0800 [thread overview]
Message-ID: <20090103100656.1cfa6d3c@gibibit.com> (raw)
In-Reply-To: <ca0f59980901030953p45c5345el2c323a7c9cf3f62f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On Sun, 4 Jan 2009 01:53:16 +0800
Bean <bean123ch@gmail.com> wrote:
> Hi,
>
> Unicode characters are split into two sizes, 16x16 and 16x8, and are
> stored in different files, for example:
>
> f16.pcf.gz
> -efont-fixed-medium-r-normal--16-160-75-75-c-160-iso10646-1
>
> h16.pcf.gz
> -efont-fixed-medium-r-normal--16-160-75-75-c-80-iso10646-1
>
> They can be converted to f16.pf2 and h16.pf2. However, only one font
> can be active at at time. So if we use both full and half width
> characters, some of them is not displayed properly. The pf2 format
> seems to allow different font widths. Perhaps the converter should
> allow multiple input, so that we can merge the two fonts into one pf2
> ?
This would be fairly simple to do. The font would then effectively be
a proportional-width font since the new font engine+gfxterm does not
handle "bi-width" fonts in a character-cell environment.
I try adding the multiple font input feature when I have a chance.
Vesa wants the convert re-implemented in C, though, which will take
some time.
Regards,
Colin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-03 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 17:53 Problem with fonts in different width Bean
2009-01-03 18:06 ` Colin D Bennett [this message]
2009-01-03 19:27 ` Vesa Jääskeläinen
2009-01-03 19:30 ` Vesa Jääskeläinen
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=20090103100656.1cfa6d3c@gibibit.com \
--to=colin@gibibit.com \
--cc=bean123ch@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.