After defining FT_OPTIMIZE_MEMORY, trutype sbits (bit-aligned) stop
to work. I found the glyph size checking in
`tt_sbit_decoder_load_bit_aligned' is not done right. Fixing that
makes glyphs load, but the loaded bitmaps are still not right.
I've seen that you've committed a lot of changes
And will the major .so version be bumpped up?
Nope, because this would create problems as Owen Taylor pointed out,
since through indirect linking, a given program might find itself
dependent on both libfreetype6 and libfreetype7, which could cause
major problems depending on the code paths
Will it be released with FT_OPTIMIZE_MEMORY defined?
Yes, d.e.f.i.n.i.t.e.l.y !!
So maybe it's time to switch that on in the CVS...
More information at:
http://turnerdavid.neuf.fr/freetype/freetype-2.2.0-safe-install.html
http://turnerdavid.neuf.fr/freetype/rogue-patches.html
I'll
Hi David,
After defining FT_OPTIMIZE_MEMORY, trutype sbits (bit-aligned) stop to
work. I found the glyph size checking in
`tt_sbit_decoder_load_bit_aligned' is not done right. Fixing that makes
glyphs load, but the loaded bitmaps are still not right.
--
Regards,
olv
=== src/sfnt/ttsbit0.c
Chia-I Wu a crit:
On Tue, Jan 17, 2006 at 06:22:45PM +0100, Werner LEMBERG wrote:
I want to know when does the next version (ver 2.2.0?)
of freetype release?
Hopefully within a month or so.
Will it be released with FT_OPTIMIZE_MEMORY defined?
I want to know when does the next version (ver 2.2.0?)
of freetype release?
Hopefully within a month or so.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
