QVGA V/s VGA for GTA03 (was something about yummy CPU-GPU combos!)
Carsten Haitzler (The Rasterman)
raster at openmoko.org
Tue Jun 10 03:08:59 CEST 2008
On Mon, 9 Jun 2008 20:11:37 +0200 "Dotan Cohen" <dotancohen at gmail.com> babbled:
> 2008/6/9 Flemming Richter Mikkelsen <quatrox at gmail.com>:
> > On 6/9/08, The Rasterman Carsten Haitzler <raster at openmoko.org> wrote:
> > [...]
> >> an 80x24 terminal is possible to make it readable @ qvga - if we allow
> >> scrolling. (and possible in landscape with an ultra-tiny 4-pixel wide font
> >> - possible (3 pixels for text, 1 for space). not very nice though.
> > How can u separate @, #, $, S, %, æ, ø, o, etc, when only using 3 pixels?
> > 5 pix + 1 pix space is a minimum for good reading, unless some chars
> > take more space than others.
> 5 pix + 1 pix space is a minimum for reading
> There, fixed that for you. Getting by with 3+1 pixels is not reading.
> You may be able to dechipher words, but that is not reading. Reading
> is when the brain skips over large portions of the text and absorbs
> the full meaning, because it is able to recognize familiar shapes and
> derive from them meaning. 3+1 cannot create the different shapes
> necessary for reading.
it can. given a well made font. done it before. see my previous mail with some
examples. when used as an actual font they are readable and recognisable as
their intended character (once you get used to the font).
> 7 pix + 2 pix space is a minimum for _good_ reading
> Dotan Cohen
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> Openmoko community mailing list
> community at lists.openmoko.org
Carsten Haitzler (The Rasterman) <raster at openmoko.org>
More information about the community