9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf + VeraMono rendering
Date: Mon, 13 Aug 2007 07:25:58 -0400	[thread overview]
Message-ID: <efb345fb70418ef2f9d0e04993f9661d@quanstro.net> (raw)
In-Reply-To: <46C03260.80305@ajft.org>

> I can confirm that the problem happens with a plan9 terminal and the
> vera.ttf font running as a guest OS in VMware workstation 5.5, I'd
> thought it was an oddity of my setup.
> 
> > However this doesn't happen in acme window, it happens only to the
> > terminal window.
> 
> > Any hints how to avoid this?

you need an updated rio/libframe/devdraw.  the problem is that libframe
used to do an alpha draw on top of the current screen image.
with a subpixel antialiased font, there are many pixels with 
an alpha channel between 0 and 0xff, so drawing a character
on top of itself will result in these pixels becoming darker.
so when you deselect a window and reselect it (causing the text
to be redrawn grey and then black), the old algorithm would
cause pixels with an alpha channel between 0 and 0xff to become
darker, making the text look pretty blocky.

this was fixed may 15, 2006, i believe.  i use a subpixel antialiased font.
(/n/sources/contrib/quanstro/antialias.tar /lib/font/bit/cyberbit/mod14.font)

by the way, i don't think acme ever had this problem.

- erik


  reply	other threads:[~2007-08-13 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  9:30 prem
2007-08-13 10:28 ` Adrian Tritschler
2007-08-13 11:25   ` erik quanstrom [this message]
2007-08-13 13:12   ` [9fans] " prem
2007-08-13 13:59     ` erik quanstrom
2007-08-15 16:14       ` Uriel
2007-08-16 13:42         ` erik quanstrom
2007-08-16 17:02           ` geoff

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=efb345fb70418ef2f9d0e04993f9661d@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).