Re: [ft] FT_Outline_Render makes different bitmaps in 32-bit and 64-bit programs?

2010-10-26 Thread suzuki toshiya
Hi, It seems that this bug appears since a change between 2.3.9 and 2.3.10: The change does not seem to have different effect between 32-bit and 64-bit systems, so I'm afraid there is unknown bug related with overflow or anything like that, and 64-bit system doesn't fall in it occasionally. I

Re: [ft] FT_Outline_Render makes different bitmaps in 32-bit and 64-bit programs?

2010-10-26 Thread Werner LEMBERG
It seems that this bug appears since a change between 2.3.9 and 2.3.10: [...] Thanks in advance for investigating the problem. Since I don't have access to a 64bit system, I unfortunately can't help much. Werner ___ Freetype mailing list

Re: [ft] FT_Outline_Render makes different bitmaps in 32-bit and 64-bit programs?

2010-10-26 Thread Tom Bishop, Wenlin Institute
The bug appears to be here in ftraster.c: /* FMulDiv means `Fast MulDiv'; it is used in case where `b' is */ /* typically a small value and the result of a*b is known to fit into */ /* 32 bits. */ #define FMulDiv( a, b, c ) (

Re: [ft-devel] Re: FT_MAX_CURVE_DEVIATION vs ONE_PIXEL cont'd

2010-10-26 Thread Werner LEMBERG
I also consider conic0.png to be slightly better (I did the blind test *before* reading Werner's response). Yes, conic0 == 2.4.3, conic_0 == HEAD The attached is hinted rendering now. Look for differences between e's and o's. The most notable difference is the rendering of `s' IMHO (e.g.