Re: Framebuffer Monochrom Glyphs ( was: Re: Atari MiNT Port )
On Wed, Sep 29, 2010 at 03:12:25PM +0200, m0n0 wrote:
Am Mittwoch, den 29.09.2010, 15:03 +0200 schrieb Rob Kendrick
<rjek(a)netsurf-browser.org>:
>On Wed, Sep 29, 2010 at 02:10:22PM +0200, m0n0 wrote:
>Firstly, don't use monochrome rasterising with FreeType. It's actually
>slower than anti-aliased rendering, because it has to do a second pass
>for drop-out control.
I'm not using monochrom rastering, I know that it is slower ( for
small
glyphs ) :) I just did a quick test because I remembered the topic.
Anyway
maybe it can be usefull when rendering for 256 colors...
I doubt it; I suspect colour-reducing FreeType's 256-shades-of-gray
output to nearest colour in your colour set will still be quicker than
the second pass. I suspect removing this option rather than fixing any
possible problem with it would be a better choice.
>Additionally, when reporting issues, please include information
on what
>versions of everything you are using, and what changes you have made
>from that version. Otherwise we cannot help you.
desktop/netsurf.c netsurf_init 142: version '3.0 (Development)'
desktop/netsurf.c netsurf_init 149: NetSurf on <Linux>, node <armdev>,
release <2.6.27-14-generic>, version <#1 SMP Tue Jun 30 19:57:39 UTC
2009>, machine <i686>
This does not answer the question. Please provide the output of `svn
info` and `svn diff`.
libnsfb revision: Revision 10856
framebuffer frontend revision: 10708
Same goes for these.
B.