Re: [Tuxpaint-devel] [Tuxpaint-users] TuxPaint text area default font

[Albert C. <aca...@gm...>]

On Wed, Jun 3, 2009 at 2:12 PM, Bill Kendrick <nb...@so...> wrote:
> On Wed, Jun 03, 2009 at 01:37:18PM -0400, Albert Cahalan wrote:

> Uh, what I mean is:  The FreeSans/FreeMono/etc. fonts that we include
> by default appear as:
>
>  A {block}

You can easily cause these to be thrown away or scored
lower, as long as "block" doesn't have tiny hex numbers.
If you really just get a plain block, put a pair of Chinese
characters in a string and it'll work.

One does need a **pair** of characters to go bad. There is
no specific recognition of the missing character symbol.
You need to cause more than one to occur; the resulting
match (identical rendering) is what affects the results.

The code also considers a character bad if it simply won't
render, but you can't count on this to happen. Some fonts
will cause such failures, while others map all missing characters
to a blank space or to a rectangular box.