From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dejavu sans
Date: Wed, 20 Jun 2012 14:37:15 -0400 [thread overview]
Message-ID: <121b985cea0c251ede7c6d8410640ef1@ladd.quanstro.net> (raw)
In-Reply-To: <20120620185228.0807a5d6@vardo.ethans.dre.am>
> I believe I do, and I'm pretty sure the difference lies in gamma or
> color correction which is provided by most graphics chipsets but is
> inaccessible with VESA. It is also likely to be inaccessible with
> native drivers if they are open source, it was a fluff feature when
> CRTs were common and seems to still be treated that way.
>
> You may have noticed that images appear paler on those displays where
> Vera looks blurry. This is because of the lack of gamma correction.
> Black may still be black and white white, but without gamma correction
> a 50% grey may appear far brighter than it should be, especially on a
> LCD. (On a CRT it's more likely to be darker, in my experience.) Vera
> then looks blurry because the pixels that are supposed to be mid-grey
> become far brighter, far more visible than they are meant to be.
>
> The particularly interesting thing about this is it suggests a
> workaround. The font is implemented as a 4-bit greyscale image. Instead
> of treating the font as a true greyscale it could instead be treated as
> a palettized image and the palette adjusted to suit the screen,
> darkening the greys on the displays for which it is necessary.
excellent explainer.
i typically use full rgb fonts. i don't see why one couldn't α
draw through an appropriate shade to change the font image itself.
- erik
next prev parent reply other threads:[~2012-06-20 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK4xykUUVbvHtxyeQYLz3zZPrkOUgMRa=KCxsD2LbiZPww-rsg@mail.gmail.c>
2012-06-11 21:16 ` erik quanstrom
2012-06-11 21:33 ` John Floren
2012-06-11 21:57 ` sl
2012-06-11 21:58 ` erik quanstrom
2012-06-11 22:18 ` Ethan Grammatikidis
2012-06-11 23:31 ` sl
2012-06-11 23:43 ` erik quanstrom
2012-06-11 23:55 ` sl
2012-06-11 23:59 ` erik quanstrom
2012-06-14 18:01 ` Yaroslav
2012-06-14 19:13 ` sl
2012-06-15 4:23 ` Yaroslav
2012-06-20 17:52 ` Ethan Grammatikidis
2012-06-20 18:37 ` erik quanstrom [this message]
2012-06-25 18:13 ` Ethan Grammatikidis
2012-06-25 11:03 ` Richard Miller
2012-06-25 12:09 ` hiro
2012-06-25 13:06 ` Richard Miller
2012-06-11 21:59 ` andrey mirtchovski
[not found] ` <CAK4xykVYFHnOWJCF9ESZ-6+AJ1TpFvAK=Rvee4pQcdkWG7KWnw@mail.gmail.c>
2012-06-11 22:02 ` erik quanstrom
2012-06-11 22:35 ` andrey mirtchovski
2012-06-11 22:37 ` andrey mirtchovski
[not found] ` <CAK4xykVdiOCPmyh=0rHL6djOvkXk4mTXiGzOaAA-eT6g=kqkmw@mail.gmail.c>
2012-06-11 23:47 ` erik quanstrom
2012-06-11 23:54 ` erik quanstrom
[not found] ` <CAK4xykVi13QUxk27riw-P=SY3M60yX94FBChBHOshyXj+PL80g@mail.gmail.c>
2012-06-11 23:41 ` erik quanstrom
2012-06-11 21:36 ` andrey mirtchovski
[not found] ` <CAK4xykU36SW-LwVUoo8Atp2fv6puzYVh614DLy5THy3-9=5Vvg@mail.gmail.c>
2012-06-11 21:40 ` erik quanstrom
[not found] ` <CAL4LZyh6hVGYpMTgO=Q0G8j7NVRCBAYR_HiwhG0nmst+qV3rxg@mail.gmail.c>
2012-06-11 21:45 ` erik quanstrom
2012-06-11 21:06 andrey mirtchovski
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=121b985cea0c251ede7c6d8410640ef1@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).