From: Lubomir Rintel <lkundrak@v3.sk>
To: nimrud <amanoeladawod@gmail.com>, gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fonts: New Terminus large console font
Date: Tue, 27 Nov 2018 13:24:23 +0000 [thread overview]
Message-ID: <374b76346ab53851632e8d300164022db9ed9a3c.camel@v3.sk> (raw)
In-Reply-To: <20181126034734.9423-1-amanoeladawod@gmail.com>
Hi.
On Sun, 2018-11-25 at 22:47 -0500, nimrud wrote:
> This patch adds an option to compile-in a high resolution and large
> Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
>
> The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
> with the help of psftools and minor hand editing deleting useless characters.
>
> This patch is non-intrusive, no options are enabled by default so most
> users won't notice a thing.
>
> I am placing my changes under the GPL 2.0 just as source Terminus font.
>
> Signed-off-by: Amanoel Dawod <amanoeladawod@gmail.com>
I've wished for a 15x30 font for quite some time, because that would
look good on an OLPC laptop screen that's 19cm (7.5") at 1200x900. A
15x30 would give me 80x30 characters, while a 16x32 would give me
somewhat less practical 75x28 with extra space around.
I'm wondering what resolutions are you targetting? Perhaps a 30x15
would do just as well, and if we need an 32x16, then we could perhaps
just add an ability to scale one of the existing fonts by a factor of
2.
Cheers
Lubo
next prev parent reply other threads:[~2018-11-27 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181126034734.9423-1-amanoeladawod@gmail.com>
2018-11-26 6:56 ` [PATCH] Fonts: New Terminus large console font Greg KH
[not found] ` <CACd_pd8o5vA85ppNp3hzm+awBvwq6VEONij6rHAPExmPfjaWRA@mail.gmail.com>
2018-11-26 8:14 ` Greg KH
2018-11-26 6:57 ` Greg KH
2018-11-27 13:24 ` Lubomir Rintel [this message]
[not found] <20181126092115.754-1-amanoeladawod@gmail.com>
2018-12-05 11:02 ` Greg KH
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=374b76346ab53851632e8d300164022db9ed9a3c.camel@v3.sk \
--to=lkundrak@v3.sk \
--cc=akpm@linux-foundation.org \
--cc=amanoeladawod@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).