From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Improve DejaVuSans detection
Date: Tue, 21 Jan 2014 20:16:19 +0400 [thread overview]
Message-ID: <20140121201619.0b577a81@opensuse.site> (raw)
In-Reply-To: <52DE25E1.3030006@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
В Tue, 21 Jan 2014 08:46:41 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> > Prefer DejaVuSansMono if found, on openSUSE DejaVuSans is proportional font.
> >
> It's fine to use SansMono for terminal (I'd prefer unifont though) but
> this change also changes the way various items in menu are displayed.
> Monospace fonts are less dense so allow less info in menu on small screens.
Yes, I realized that. The problem is, unifont may be missing (user is
free to override it with GRUB_FONT) and theme must be self-consistent
(which is also why my other attempt to set font to Unifont is not quite
correct as well). I tried to build fixed width DejaVuSansMono, but I do
not like results enough. First, it results in extremely large vertical
size using standard parameters; e.g.
bor@opensuse:~/build/grub> ./build-grub-mkfont -o /tmp/foo.pf2 -v -s 12 /usr/share/fonts/truetype/DejaVuSansMono.ttf
Unknown gsub font feature 0x63636d70 (ccmp)
Unknown gsub font feature 0x646c6967 (dlig)
Unsupported substitution flag: 0x9
Unsupported substitution flag: 0x9
Unknown gsub font feature 0x6c6f636c (locl)
Unknown gsub font feature 0x6c6f636c (locl)
Unsupported substitution flag: 0x9
Font name: DejaVu Sans Mono Regular 12
Max width: 11
Max height: 22
Font ascent: 14
Font descent: 4
Number of glyph: 3388
22 height for font size 12! Forcing hinting gives something more close
to reality
bor@opensuse:~/build/grub> ./build-grub-mkfont -o /tmp/foo.pf2 -v -s 12 -a /usr/share/fonts/truetype/DejaVuSansMono.ttf
Unknown gsub font feature 0x63636d70 (ccmp)
Unknown gsub font feature 0x646c6967 (dlig)
Unsupported substitution flag: 0x9
Unsupported substitution flag: 0x9
Unknown gsub font feature 0x6c6f636c (locl)
Unknown gsub font feature 0x6c6f636c (locl)
Unsupported substitution flag: 0x9
Font name: DejaVu Sans Mono Regular 12
Max width: 11
Max height: 16
Font ascent: 13
Font descent: 5
Number of glyph: 3388
But still too high so vertical lines look dashed.
May be the simplest solution would be to follow the same logic as
gfxterm - unless terminal-font is explicitly set, use $gfxterm_font by
default with fallback to first loaded font.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-21 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 12:15 [PATCH] look for DejaVu also in /usr/share/fonts/truetype Andrey Borzenkov
2014-01-18 15:58 ` [PATCH] Improve DejaVuSans detection Andrey Borzenkov
2014-01-18 16:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-18 17:04 ` Andrey Borzenkov
2014-01-21 7:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-21 16:18 ` Andrey Borzenkov
2014-01-21 7:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-21 16:16 ` Andrey Borzenkov [this message]
2014-01-21 23:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-25 20:05 ` Andrey Borzenkov
2014-01-21 7:29 ` [PATCH] look for DejaVu also in /usr/share/fonts/truetype Vladimir 'φ-coder/phcoder' Serbinenko
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=20140121201619.0b577a81@opensuse.site \
--to=arvidjaar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).