From: "Thorsten Glaser Geuer" <eccesys@topmail.de>
To: <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: ISO-8859-1 completeness of kernel fonts?
Date: Tue, 27 Feb 2001 20:05:53 -0000 [thread overview]
Message-ID: <036601c0a0f8$bd0ad070$742c9c3e@tp.net> (raw)
In-Reply-To: <F281raFC8XymNMDdckH00012e6f@hotmail.com> <000001c0a0ed$1ea188d0$742c9c3e@tp.net> <97h0bq$kdc$1@cesium.transmeta.com>
----- Original Message -----
From: "H. Peter Anvin" <hpa@zytor.com>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, February 27, 2001 7:49 PM
Subject: Re: ISO-8859-1 completeness of kernel fonts?
> Followup to: <000001c0a0ed$1ea188d0$742c9c3e@tp.net>
> By author: "Thorsten Glaser Geuer" <eccesys@topmail.de>
> In newsgroup: linux.dev.kernel
> >
> > My second suggestion: code it as .psfu and load it by setfont, including
> > the appropiate console-map. AFAIK all the kernel default fonts are cp437
> > (linux/drivers/char/cp437.uni; consolemap.*)
> >
>
> Something that would be really good is if someone could contribute PSF
> (v1 and v2) support for gfe <http://www.gnu.org/software/gfe/gfe.html>
> or some other free font editor.
>
> -hpa
I always do it by a BASIC programme under DOS (yep I know
this isn't pure but I have a font editor from S-DOS aka
PTS-DOS (the free version)). The SFE.COM allows me to design
8x8 8x12 8x14 8x16 fonts; the unicode table I write in the
MC or VC (NC clone for DOS) editor; my BASIC pgm converts
them together to PSFU. It's very easy once you read the psf
docs.
It's a pity that I've to mkfs the DOS partitions of my HDDs
every handfull of weeks, otherwise I'd put them onto a ftp
server somewhere. But I call you to try it by yourself.
(perl prolly isn't that easy coz it goes to binary values,
but GW-BASIC is fine)
-mirabilos
next prev parent reply other threads:[~2001-02-27 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 6:37 ISO-8859-1 completeness of kernel fonts? Mack Stevenson
2001-02-27 7:34 ` H. Peter Anvin
2001-02-27 16:26 ` Thorsten Glaser Geuer
2001-02-27 19:49 ` H. Peter Anvin
2001-02-27 20:05 ` Thorsten Glaser Geuer [this message]
2001-02-27 21:19 ` H. Peter Anvin
2001-02-28 7:29 ` idalton
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 13:41 Mack Stevenson
2001-02-27 17:37 ` H. Peter Anvin
2001-02-27 19:58 ` Guest section DW
2001-02-27 23:16 ` Kurt Garloff
2001-02-27 21:45 Mack Stevenson
2001-02-27 23:34 Andries.Brouwer
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='036601c0a0f8$bd0ad070$742c9c3e@tp.net' \
--to=eccesys@topmail.de \
--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 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.