From: Baybal Ni <nikulinpi@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: My new fancy font for framebuffer
Date: Sun, 22 Mar 2009 18:22:11 +0900 [thread overview]
Message-ID: <ff479ab60903220222w1d10da15xd446fb4eabfde4d1@mail.gmail.com> (raw)
In-Reply-To: <49C5BBE8.6010906@zytor.com>
On Sun, Mar 22, 2009 at 1:17 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> Arjan van de Ven wrote:
>> On Sat, 21 Mar 2009 16:45:19 +0000
>> Baybal Ni <nikulinpi@gmail.com> wrote:
>>
>>> I thought the default font to be boring and there is my linux port of
>>> terminus font.
>>
>> can you give some clarity of the copyrights around the terminus font?
>> It'd nice to have pretty fonts.. but we need to make sure we're clear
>> around the copyrights....
>>
>
> Either way, the terminus font by Dimitar Zhekov is GPL 2. This probably
> means that distributing it without distributing the source format or
> "the preferred form for editing" is illegal in jurisdictions where
> bitmap fonts are copyrightable. The preferred format for editing the
> terminus font appears to be BDF.
BDF is a compilled format itself. Technicaly it is still 100% the same
bitmap (Just a one giant bitmap + markup about character sizes).
So these way we just effectively ... decompiled it to the same it's
source which could be distributed under GPL. Which is totally ok with
GPL.
> That, combined with the sheer number of character subsets one can get
> out of the extremely rich terminus font would again mean that the kbd
> project is a better place for it.
Cut everything below 255
Yes, but we want it to be bundled in kernel, for me it is the only
option for systems with qvga screens or so on. Old fonts were nice
only on CRT displays, but on TFTs they are giving too much load on
eyes and brain. More clean contoured fonts are effectively cutting it.
next prev parent reply other threads:[~2009-03-22 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 16:45 Baybal Ni
2009-03-21 18:15 ` Arjan van de Ven
2009-03-22 4:12 ` H. Peter Anvin
2009-03-22 4:17 ` H. Peter Anvin
2009-03-22 9:22 ` Baybal Ni [this message]
2009-03-22 19:01 ` H. Peter Anvin
2009-03-22 23:35 ` Ken Moffat
2009-03-24 6:43 ` Baybal Ni
2009-03-24 23:15 ` H. Peter Anvin
2009-03-24 23:39 ` Felipe Contreras
2009-03-24 23:43 ` H. Peter Anvin
[not found] <cicyE-3qo-15@gated-at.bofh.it>
[not found] ` <cidXL-5OQ-35@gated-at.bofh.it>
[not found] ` <cinu8-41e-3@gated-at.bofh.it>
[not found] ` <cisas-37w-5@gated-at.bofh.it>
[not found] ` <ciFKp-7QW-17@gated-at.bofh.it>
[not found] ` <cj8CE-3uO-11@gated-at.bofh.it>
[not found] ` <cjo4C-3hh-13@gated-at.bofh.it>
[not found] ` <cjoo1-3FO-13@gated-at.bofh.it>
[not found] ` <cjoxL-3SW-35@gated-at.bofh.it>
2009-03-26 13:55 ` Bodo Eggert
2009-03-30 7:51 ` Baybal Ni
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=ff479ab60903220222w1d10da15xd446fb4eabfde4d1@mail.gmail.com \
--to=nikulinpi@gmail.com \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®