From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: <9front@9front.org>
Subject: Re: [9front] Truetypefs anti-aliasing
Date: Sun, 19 Jan 2025 20:17:17 -0600 [thread overview]
Message-ID: <D76JFJHV2DAV.2YT3U67K403XM@tcp80.org> (raw)
In-Reply-To: <CA+POUVi=ML1bfSgqp1d6Tuiw=-jytWQcaPYHA55rg=YbTFh22w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
On Sun Jan 19, 2025 at 7:40 PM CST, Paul Lalonde wrote:
> I posted this earlier on 9fans, but I should do it here:
> I've made a modification to truetypefs to do what ttfrender does: render
> the font at higher resolution and filter down to a good looking 8 bit font.
>
> This is a significant improvement in the appearance of the fonts from
> truetypefs, as seen in the image below. Left is the one-bit font, right is
> the filtered font.
> [image: image.png]
> I've attached the change, and I have questions.
> I believe in being opinionated: the 8 bit version is so much better for
> every font I've compared that I don't see any use for the 1 bit versions
> anymore.
> How do other users feel about ditching the 1 bit code path and having only
> the 8 bit code path? This is the cleanest/smallest change.
> The alternatives would be to have a switch to truetypefs so that it always
> returns either 1 bit or 8 bit fonts; a switch in the fs setup to choose
> based on font size; a way to tell the fs what font depth to return
> (probably a hack like the font size now, very ugly).
> The cost of the filtering is low in compute for smaller point sizes, but
> starts to lag a bit at 30 point or so. It probably also blurs out very
> small sizes. I don't know that anyone chooses TrueType fonts for text
> under ~10pt however.
> [image: image.png]
> Thoughts?
> Paul
Paul, Sigrid would like you to take a look at the font renderer she's been
working on at https://git.sr.ht/~ft/fnt . She's currently experiencing e-mail
issues and asked me to relay this. All mistakes in this message are my own.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-20 2:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 1:40 Paul Lalonde
2025-01-20 2:17 ` B. Atticus Grobe [this message]
2025-01-20 4:36 ` [9front] Truetypefs anti-aliasings ori
2025-01-20 6:30 ` [9front] Truetypefs anti-aliasing Blue-Maned_Hawk
2025-01-30 5:32 ` ori
2025-01-20 10:08 qwx
2025-01-20 11:57 ` sirjofri
2025-01-20 13:13 ` Steve Simon
2025-01-20 14:32 ` Paul Lalonde
2025-01-31 16:39 ` qwx
2025-01-20 15:30 ` Sigrid Solveig Haflínudóttir
2025-01-20 17:45 ` ori
2025-01-20 17:55 ` Sigrid Solveig Haflínudóttir
2025-01-20 18:06 ` Paul Lalonde
2025-01-20 19:01 ` Sigrid Solveig Haflínudóttir
2025-01-20 23:20 ` ori
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=D76JFJHV2DAV.2YT3U67K403XM@tcp80.org \
--to=grobe0ba@tcp80.org \
--cc=9front@9front.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).